On 31/05/2022 22.25, Eyal Lebedinsky wrote:
I am on f36 for a few weeks now, upgraded from f34.
This is the second time this happened. A 'dnf update' runs fine but hangs at
the very end, after the list of 'Veritying'.
dnf (the python3 process) is in state D+ (though I could kill it).
dnf.log
Tom Horsley writes:
On Tue, 31 May 2022 18:38:54 -0400
Sam Varshavchik wrote:
> It keeps finding its way back on my systems, even after I uninstalled it
Uninstalling is probably hopeless. I don't bother with uninstalling
things like that, but disabling and masking them seems to work well,
and
On Tue, 31 May 2022 18:38:54 -0400
Sam Varshavchik wrote:
> It keeps finding its way back on my systems, even after I uninstalled it
Uninstalling is probably hopeless. I don't bother with uninstalling
things like that, but disabling and masking them seems to work well,
and that leaves all the fil
Roger Heflin writes:
« HTML content follows »
once you update the file to be a good one, then do this:
chattr +i /etc/resolv.conf (that sets the immutable bit that disallows
rename, write, delete).
That should prevent anything from overwriting the file. If you need to
change the fi
once you update the file to be a good one, then do this:
chattr +i /etc/resolv.conf (that sets the immutable bit that disallows
rename, write, delete).
That should prevent anything from overwriting the file. If you need to
change the file you will have to -i the file first.
It is kind of crude
> Am 31.05.2022 um 14:25 schrieb Eyal Lebedinsky :
>
> ...
> dnf.rpm.log ends with this interesting line
> 2022-05-31T21:37:06+1000 INFO '/etc/resolv.conf' ->
> '../run/systemd/resolve/stub-resolv.conf'
This is expected behaviour. systemd-resolved with resolv.conf linked to that
stub is
I am on f36 for a few weeks now, upgraded from f34.
This is the second time this happened. A 'dnf update' runs fine but hangs at
the very end, after the list of 'Veritying'.
dnf (the python3 process) is in state D+ (though I could kill it).
dnf.log ends with
2022-05-31T21:32:33+1000 DDE
