Hide Forgot
Created attachment 813951 [details] fedup debug log Description of problem: I tried to upgrade F19->F20 using fedup. I first ran # fedup --network 20 --debuglog fedupdebug.log and after some errors because of a missing repository (jamielinux-tor not available on F20 as of now) I tried # fedup --network 20 --debuglog fedupdebug.log --disablerepo jamielinux-tor without cleaning fedup inbetween. This is my output: ~~~~~ setting up repos... getting boot images... .treeinfo | 1.1 kB 00:00:00 setting up update... Your system is already upgraded! Finished. Nothing to do. ~~~~~ fedup didn't download any packages at all so it really didn't upgrade my system. Version-Release number of selected component (if applicable): fedup 0.7.4-4.fc19 How reproducible: always
I am seeing a similar problem on Fedora 20, when trying to upgrade to rawhide. In my case, in addition I also am failing to find any usable debugging output. Output I do get from the fedup.log is that it looks like it is successful but what is displaying on the screen itself as it streams by very quickly duringi the upgrade is another story. I see no progress bar as it never gets to that point in the console at reboot. Multiple errors for every single file occur, including input/output errors involving cp commands, 'unable to extend' errors, 'access denied' massages, insufficient disk space on the device (even though there are over 50 GiB of free space on the device), failure to write any files to the system-upgrade-root folder, and more. There also is nothing wrong with the device. SMART and other diagnostics confirm that as to the hard disk everything is OK. Running fsck utilities shows the drive's filesystem as clean and undamaged. Not sure what is going on. fedup-0.8.0-3.fc20.noarch I am going to attempt a downgrade and see what happens next.
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.