Re: Cockpit depends on NetworkManager.
> 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-r... > -Dan If users survived half the system being removed and rendered useless because of PackageKit bugs, I think they will survive one NetworkManager removal. What I am trying to say, that should have been done earlier, now is too late. IMHO. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Cockpit depends on NetworkManager.
Hi, You should always check the list before confirming the action. As Mathew said, it is probably an issue with package not being marked as user installed for some reason. There was an issue in the past with using PackageKit and dnf together, see: https://fedoraproject.org/wiki/Common_F24_bugs#DNF_might_remove_essential_system_packages_if_you_used_PackageKit_.28GNOME_Software.2C_KDE_Apper.29_in_the_past Such package might have been still marked wrongly, thus this issue. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Cockpit depends on NetworkManager.
On Tue, Oct 17, 2017 at 7:29 AM, Jonathan Wakely wrote: > > >> 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-requ >> irements-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. They don't, but they do add to the list of reasons why it should not be enabled by default. The other major reason is that there is (still) no feedback to the user why the extra packages are being removed. This could be fixed, but it hasn't been. Other package managers, and indeed yum before, had a specific command to enable this sort of behavior called autoremove. I would be perfectly fine with having such a command, and having the ability to enable clean_requirements_on_remove, but I disagree with its default setting. -Dan ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Cockpit depends on NetworkManager.
On 16/10/17 21:58 -0400, Dan Book wrote: On Mon, Oct 16, 2017 at 9:51 PM, Matthew Miller 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
Re: Cockpit depends on NetworkManager.
On 10/17/2017 12:58 PM, jkone...@redhat.com wrote: On Tue, 2017-10-17 at 09:30 +0200, Miroslav Suchý wrote: Dne 17.10.2017 v 03:51 Matthew Miller napsal(a): 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. Can this be fixed by running: dnf mark '*' by Anaconda after installation? Or even better dnf mark SOME PRECISELY CRAFTED LIST ? I really don't think Anaconda should or can do that. You can't just mark everything as installed on purpose because it is not (there are dependencies for packages you choose) and you can't create the list of packages which user wants. Only user knows what are these packages and then he should specify them in a %packages group in a kickstart file. If we are talking about installation groups then we need to change comps to have NetworkManager explicitly named there. Do we install NetworkManager as if it were a leaf package? I think we did that in the past. No matter how we do that, this should cause the dnf mark step above. There shouldn't be any separate list to maintain here, it's just about preserving the information in the installed system. Thanks, Florian ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Cockpit depends on NetworkManager.
On Tue, 2017-10-17 at 09:30 +0200, Miroslav Suchý wrote: > Dne 17.10.2017 v 03:51 Matthew Miller napsal(a): > > 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. > > Can this be fixed by running: > dnf mark '*' > by Anaconda after installation? Or even better > dnf mark SOME PRECISELY CRAFTED LIST > ? I really don't think Anaconda should or can do that. You can't just mark everything as installed on purpose because it is not (there are dependencies for packages you choose) and you can't create the list of packages which user wants. Only user knows what are these packages and then he should specify them in a %packages group in a kickstart file. If we are talking about installation groups then we need to change comps to have NetworkManager explicitly named there. Jirka ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Cockpit depends on NetworkManager.
Dne 17.10.2017 v 03:51 Matthew Miller napsal(a): > 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. Can this be fixed by running: dnf mark '*' by Anaconda after installation? Or even better dnf mark SOME PRECISELY CRAFTED LIST ? Mirek ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Cockpit depends on NetworkManager.
On 10/16/17, Dan Book wrote: > On Mon, Oct 16, 2017 at 9:51 PM, Matthew Miller > 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 +1. -- Yours sincerely, Christopher Meng http://awk.io ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Cockpit depends on NetworkManager.
Dan Book wrote: > 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 +1 Kevin Kofler ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Cockpit depends on NetworkManager.
On Mon, Oct 16, 2017 at 9:51 PM, Matthew Miller 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 -Dan ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Cockpit depends on NetworkManager.
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. -- Matthew Miller Fedora Project Leader ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Cockpit depends on NetworkManager.
Hi, 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 [1] https://cloud.rhea-ayase.eu/s/eH6JX43kYErHJ3s Cheers, Radka -- *Radka Janeková* .NET & OpenShift Engineer, Red Hat *radka.ja...@redhat.com * IRC: radka | Freenode: Rhea ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
