Re: Strange dnf behavior or UFU (user foul up)?
On 6/3/20 1:41 PM, George R Goffe via users wrote:
Description of problem:
Attempting to upgrade this system. First try revealed errors with "nut" and
"gnutls" so I reran the command adding --exclude='nut-*' and
--exclude='gnutls*'. This retry listed several other packages with problems.
Second try, adding --exclude='kdevelop*' and --exclude='python*'. This
resulted in the "protected packages" message.
It's clear that there's a bug here or (probably) I don't understand dnf as
well as I thought.
Version-Release number of selected component (if applicable):
dnf-4.2.21-1.fc33.noarch
This is a rawhide system, so someone is certainly going to tell you that
you should post this on the test list instead. So there, I just did it. :-)
It is not unusual for rawhide to have periods of time where upgrades of
certain packages have issues because that's where development is
happening. I know there are two very large updates in progress, so
you're likely hitting an issue with one or both of those. I see a
reference to python3.9 in there, so very likely. Give it a few days to
settle down and try again. That's quite the combination of dnf options
you've put together, I'm not sure how well they all work together.
Maybe just try "--skip-broken" for now and if that doesn't work, try later.