On Wed, 2017-03-01 at 10:12 -0700, Kevin Fenzi wrote: > […] > > It sounds very much like there was a transaction in the past that > didn't complete for whatever reason ( power lost, reboot, etc). Aha. Of course. I was doing an upgrade a couple of weeks ago or so, and something associated with terminal terminated the session, logging me out. > 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 have a very large number of transactions looking similar to: 1395 | upgrade | 2017-02-25 18:39 | I, O, U | 585 EE in fact every upgrade has the trailing EE on the two machines I checked on. > 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' Maybe I just go this route this time since it has been a while it seems sine the problematic transaction. -- Russel. ============================================================================= Dr Russel Winder t:+44 20 7585 2200 voip:sip: russel.winder@xxxxxxxxx 41 Buckmaster Road m:+44 7770 465 077 xmpp:russel@xxxxxxxxxxxxx London SW11 1EN, UK w: www.russel.org.uk skype:russel_winder
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
