Bug 6031 - Latest Network Manager Commit will install dnsmasq and uninstall bind
: Latest Network Manager Commit will install dnsmasq and uninstall bind
Product: Desktop Bugs
Classification: ROSA Desktop
Component: Main Packages
: Fresh
: All Linux
: Normal normal
: ---
Assigned To: ROSA Linux Bugs
: ROSA Linux Bugs
Depends on: 6075
  Show dependency treegraph
Reported: 2015-08-11 06:03 MSD by Zombie Ryushu
Modified: 2015-12-06 19:12 MSK (History)
5 users (show)

See Also:
RPM Package: networkmanager
Bad POT generating:


Note You need to log in before you can comment on or make changes to this bug.
Description Zombie Ryushu 2015-08-11 06:03:35 MSD
Latest Network Manager Commit will install dnsmasq and uninstall bind and dnssec-tools. I barely had time to stop it, but the latest round of updates triedto uninstall bind server and install dnsmasq in it's place.
Comment 1 Eugene Shatokhin 2015-08-11 11:48:02 MSD
Yes, dnsmasq is now in "Suggests:" for NetworkManager. Curiously enough, this is needed for AP support to work properly, and that functionality is useful quite often.

For some reason, there is "Conflicts: bind" in the spec for dnsmasq, that is why bind gets removed in your case.

You can install this particular update with '--no-suggests'. 

Then there are at least 2 options.

1. If 'bind' and 'dnsmasq' can actually coexist (does anyone know if they can?), we can just remove that "Conflicts: " line from dnsmasq.

2. Or we could reshuffle dnsmasq and dnsmasq-base packages carefully, so that everything needed for AP support is in the latter. dnsmasq-base can coexist with bind it seems. Then, just remove that "Suggests: dnsmasq".

Suggestions and, better, patches are welcome.
Comment 2 Zombie Ryushu 2015-08-11 11:58:37 MSD
I think I like the second option.
Comment 3 Zombie Ryushu 2015-08-11 17:45:07 MSD
This bug also seems to remove resolveconf.
Comment 4 Zombie Ryushu 2015-08-16 19:40:21 MSD
This was never published.
Comment 5 Zombie Ryushu 2015-08-28 10:39:32 MSD
Why did this fail QA?
Comment 6 Denis Silakov 2015-12-06 19:12:18 MSK
networkmanager currently suggests dnsmasq-base only, so let's close this bug. NetworkManager can easily coexist with bind.

As for co-existence of dnsmasq and bind - they will definitely fail to run simultaneously with default configuration, since their DNS services will try to occupy port 53. One can configure them to bind different ports, but I wonder if smb really needs this in practice.