ROSA Linux Bugzilla – Bug 6031
Latest Network Manager Commit will install dnsmasq and uninstall bind
Last modified: 2015-12-06 19:12:18 MSK
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.
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.
I think I like the second option.
This bug also seems to remove resolveconf.
This was never published.
Why did this fail QA?
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.