Bug#1101532: marked as done (systemd: unable to migrate to Testing because of removed packages)

Marc Haber mh+debian-packages at zugschlus.de
Wed Apr 2 05:51:10 BST 2025


On Wed, Apr 02, 2025 at 12:24:02AM +0000, Debian Bug Tracking System wrote:
>   * reintroduce systemd-resolved, with conflict on avahi-daemon. It turns
>     out the cloud images have a hard dependency on resolved. In order to
>     avoid having to change them, reintroduce the package, with a hard
>     conflict on avahi-daemon to avoid reintroducing #1098914 (Closes:
>     #1101532)

How would I configure my system when I want resolved to handle unicast 
DNS resolving (its features are rather nice, for example it handles 
gracefully when the first of the full service resolvers is down), but 
need avahi-daemon for service announcements?

I might be stupid, but in my understanding the hard conflict forces me 
to have a local full service resolver running since I can't have 
systemd-resolved sans mDNS AND avahi-daemon. If my assumption is 
correct, the current solution breaks existing systems in a worse way 
than the solution proposed by the TC breaks other systems.

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany    |  lose things."    Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421



More information about the Pkg-systemd-maintainers mailing list