[network-manager maintainer speaking here] Am 14.06.25 um 06:52 schrieb Martin-Éric Racine:
[ Reason ] As someone found out during the soft freeze, a daemonized dhcpcd competes with network-manager and other network configuration tools for control over the network interfaces and resolver. Back when I took over maintenance of the package, I ended up spliting the init.d script and systemd unit into a separate bin:dhcpcd package precisely to avoid this. Apparently, that wasn't enough. I therefore just added a "Conflicts: network-manager" to bin:dhcpcd to further drive the point that having two networking daemons on the same host is a bad idea. This is the only change. Meanwhile, bin:dhcpcd-base remains perfectly harmless on hosts running systemd-networkd or network-manager, since it doesn't come with startup scripts and is instead executed via ifupdown or some other network configuration framework as per administrator configuration. [ Impact ] Without this fix, bug reports similar to #1107683 are likely to be filed after Trixie is released. [ Tests ] None needed. It's only a dependency change (Conflicts: network-manager).
In the past, network management systems did not declare conflicts against each other.
If what you say is true, and dhcpcd interferes with networkd, NetworkManager, ifupdown and its variants, why was only a Conflicts against the network-manager added?
This feels like a very ad-hoc workaround.
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature