On Wed, 01 Mar 2017 08:40:05 +0000
Russel Winder <russel(a)winder.org.uk> wrote:
Advice required…
I have four installations of Rawhide. Three of them seem fine,
consistent, and as expected: all packages except the kernel installed
once and up to date – I keep multiple kernels for fairly obvious
reasons.
However one machine has a large number of not fully upgraded packages.
The older package is emboldened by dnf and marked @rawhide. The newer
package is not emboldened and is marked @System. dnf seems entirely
happy that this is a consistent situation with no further action
required. Personally I would suggest that dnf is, well, wrong. As an
example:
ImageMagick.x86_64 6.9.3.0-
4.fc26 @rawhide
ImageMagick.x86_64 6.9.3.0-
5.fc26 @System
Even on the consistent systems some installed only once from the
rawhide repository are marked @System, I am not sure why, I would have
thought it should be marked @rawhide.
I could manually remove all the old @rawhide packages leaving the up-
to-date @System packages, but this seems wrong on so many fronts.
Sufficiently many that I thought I would become a supplicant here
seeking advice.
I am hoping that someone will show up my ignorance of the
sophistication of dnf and tell me the one liner that allows dnf to fix
everything. My fear is that dnf has just ###### things up and is
incapable of sorting it out.
It sounds very much like there was a transaction in the past that
didn't complete for whatever reason ( power lost, reboot, etc).
You can try looking for that transaction in 'dnf history list' (it will
have a big E next to it for error) and then doing a 'dnf history redo
N' where N is the number of the transaction.
I've had mixed luck with that. sometimes it works, other times packages
have changed too much and it refuses.
If that doesn't work, then yes, you will need to remove all the older
packages with: 'dnf remove --duplicates'
Hope that helps,
kevin