Hide Forgot
Created attachment 833146 [details] Part of the update output I was doing update from f19 to f20 and accidentally hit CTRL+C during the transaction and I'm not able to finish the transaction anymore. `dnf update` after the interrupted transaction just updated couple of packages but did not completed the transaction. I have now a lot of packages twice in the system. Attached is part of output (especially dnf update after the interruption).
Generally, DNF always finishes updating/installing the second time around what it was interrupted to finish the first time, that's how the solving mechanism is designed. It runs into a problem when interrupted while there are packages to be deleted. The expected reaction to ^C (that is immediate termination) was one of our goals. Not providing transaction stopping and resuming was something we thought we could get away with. All solutions to this problem have some drawbacks: 1) Blocking ^C during on ongoing RPM transaction. But what if the user really means it? 2) Storing and resuming transaction the yum-style using transaction logs. This has the drawback of leaving confusing files lying around. In the end it also brings a lot of little inconsistencies to the table: what if rpmdb changes after the transaction was stopped. Then resuming means we need to re-resolve anyway. That's hard technically (as we'd also need to store what we resolved from originally), with little benefit. 3) Using history to dig out the same information as the transaction log provides. Probably not possible. 4) Just going with the current situation. I'd very much prefer 4) --- after all it's just doing what the user wanted, then perhaps 1). If we end up with 2) it should be isolated to a plugin. Giving this a low prio now.
Discussed this with Panu who thinks RPM should block ^C when it's in the middle of transaction.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.