On 16/10/17 21:58 -0400, Dan Book wrote:
On Mon, Oct 16, 2017 at 9:51 PM, Matthew Miller <mat...@fedoraproject.org>
wrote:
On Tue, Oct 17, 2017 at 03:20:09AM +0200, Radka Janekova wrote:
> so recently I managed to destroy[1] two production servers by removing
what
> I saw as useless web-config utility. Apparently Cockpit depends on
> NetworkManager, which nobody would expect and is easily overlooked.
> PLEASE FIX
I think the bug here is that DNF is being over-zealous. NetworkManager
does not require Cockpit, but Cockpit requires NetworkManager. For some
reason, DNF thinks that Cockpit is the *only* reason NetworkManager is
installed, and "helpfully" decides to remove it.
This is clean_requirements_on_remove being helpful as usual. Never should
have been a default setting as I've argued before, and the first thing I
disable in /etc/dnf/dnf.conf.
http://dnf.readthedocs.io/en/latest/conf_ref.html#clean-requirements-on-remove-label
It would be a nice feature if it hadn't been for PackageKit not
marking packages correctly in older Fedora versions. Anybody who has
done in-place upgrades has totally wrong mark-installed metadata in
their local DB, with no good way to fix that.
Occasional bugs like NetworkManager not being marked as needed by
anything don't entirely negate the feature's usefulness.
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
