> 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 th
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#DN
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
rently 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 *
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
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 Cock
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" d
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
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
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
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.
> P
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
12 matches
Mail list logo
