Bug Report: Error E: Unable to locate package systemd-resolved

[hd00842]

OS Version

Debian 11, Debian 12

System Information

Debian 11, Debian 12

What happened?

Error E: Unable to locate package systemd-resolved

Machine Type

generic-x86-64

Installer output

No response

Relevant log output

No response

ADR

• I have read through the ADR and have confirmed that my system is compliant with the requirements
• I understand that if my system is found to not be compliant, my issue will be closed immediately without further investigation

Code of Conduct

• I have read and agree to the Home Assistant Code of Conduct

[waney]

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package systemd-resolve

[Aliskin-Papa]

Same here

[Lockszmith-GH]

I'm no maintainer, but I encountered something similar before, turned out I didn't upgrade debian 12 peroperly, after that the issue was resolved.

systemd-resolved is a native debian package (I think it was introduced in debian 12, split away from a larger monolith repo).
Please run the following

If you run the following, check to see if you get anything different in the output from mine (expand the Details section at the bottom).

Hope this helps.

cat /etc/debian_version
cat /etc/os-release
cat /etc/apt/sources.list
ls -la /etc/apt/sources.list.d
sudo apt update && sudo apt install systemd-resolved

Output from my debian 12 system

$ cat /etc/debian_version
 12.1
$ cat /etc/os-release
 PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
 NAME="Debian GNU/Linux"
 VERSION_ID="12"
 VERSION="12 (bookworm)"
 VERSION_CODENAME=bookworm
 ID=debian
 HOME_URL="https://www.debian.org/"
 SUPPORT_URL="https://www.debian.org/support"
 BUG_REPORT_URL="https://bugs.debian.org/"
$ cat /etc/apt/sources.list
 # deb cdrom:[Debian GNU/Linux 11.1.0 _Bullseye_ - Official amd64 NETINST 20211009-10:07]/ bookworm main
 
 #deb cdrom:[Debian GNU/Linux 11.1.0 _Bullseye_ - Official amd64 NETINST 20211009-10:07]/ bookworm main
 
 deb http://deb.debian.org/debian/ bookworm main
 deb-src http://deb.debian.org/debian/ bookworm main
 
 deb http://security.debian.org/debian-security bookworm-security main
 deb-src http://security.debian.org/debian-security bookworm-security main
 
 # bookworm-updates, to get updates before a point release is made;
 # see https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_updates_and_backports
 deb http://deb.debian.org/debian/ bookworm-updates main
 deb-src http://deb.debian.org/debian/ bookworm-updates main
 
 # This system was installed using small removable media
 # (e.g. netinst, live or single CD). The matching "deb cdrom"
 # entries were disabled at the end of the installation process.
 # For information about how to configure apt package sources,
 # see the sources.list(5) manual.
$ ls -la /etc/apt/sources.list.d
$ sudo apt update && sudo apt install systemd-resolved
 Hit:1 http://deb.debian.org/debian bookworm InRelease
 Hit:2 http://security.debian.org/debian-security bookworm-security InRelease                                       
 Hit:3 http://deb.debian.org/debian bookworm-updates InRelease                                                                   
 Hit:4 https://packages.microsoft.com/debian/10/prod buster InRelease                                                            
 Hit:5 https://download.docker.com/linux/debian bullseye InRelease                                        
 Reading package lists... Done
 Building dependency tree... Done
 Reading state information... Done
 3 packages can be upgraded. Run 'apt list --upgradable' to see them.
 Reading package lists... Done
 Building dependency tree... Done
 Reading state information... Done
 systemd-resolved is already the newest version (252.12-1~deb12u1).
 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.

[hd00842]

I'm no maintainer, but I encountered something similar before, turned out I didn't upgrade debian 12 peroperly, after that the issue was resolved.

systemd-resolved is a native debian package (I think it was introduced in debian 12, split away from a larger monolith repo). Please run the following

If you run the following, check to see if you get anything different in the output from mine (expand the Details section at the bottom).

Hope this helps.

cat /etc/debian_version
cat /etc/os-release
cat /etc/apt/sources.list
ls -la /etc/apt/sources.list.d
sudo apt update && sudo apt install systemd-resolved

Output from my debian 12 system

[Lockszmith-GH]

You didn't include the cat output of the 3 files I asked, but from the apt output I can see you are runing bullseye, that's Debian 11.

You have 2 options:

• recommended You'll need to upgrade to Debian 12 aka bookwork, that where systemd-resolved package was introduced.

• Alternativley (very short lived, as Debian 11 support is marked for deprecation), if you can't upgrade immedietly, you might have luck installing it from bullseye backports.

This is Debian's guide to upgrade to a new release.
This is Debian's instructions on how to add backports.

Just an FYI about Debian packages: Searching for a package name, if you use the exact name, you'll see in the results the releases the package is available for.

As you can see below, bullseye is missing.

Screenshot of search (click to expand)

If you open the package info for stable (currently bookworm), you can see at the top right, the list of releases the package belongs to.
Also, if you follow the side-bar link to release notes (in this case it's release notes for systemd - the source meta-package), and search for systemd-resolved, you should be able to find the following text, which shows that systemd-resolved was split into it's own package recently:

systemd (251.3-2~exp1) experimental; urgency=medium

 * Split systemd-resolved into its own package which takes over
   /etc/resolv.conf (Closes: #939904)

Hope all of this helps.

[github-actions]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.