Hide Forgot
Created attachment 828589 [details] packed logs Description of problem: with FC19.x86_64 and Fedora-19-a10-armhfp-r2.img when using yum distro-sync an error is produced : --> Finished Dependency Resolution Dependency Process ending Traceback (most recent call last): File "/bin/yum", line 29, in <module> yummain.user_main(sys.argv[1:], exit_code=True) File "/usr/share/yum-cli/yummain.py", line 355, in user_main errcode = main(args) File "/usr/share/yum-cli/yummain.py", line 217, in main (result, resultmsgs) = base.buildTransaction() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1329, in buildTransaction if txmbr.pkgtup in bad_togo[ipkg.name]: KeyError: 'yum' Version-Release number of selected component (if applicable): Yum version: 3.4.3 How reproducible: yum --releasever=20 distro-sync --debuglevel=9 --rpmverbosity=9 Actual results: error Expected results: upgrade to FC20 Additional info: on FC19.x86_64 an upgrade was finally successfull after partial updates. Please see attached files.
I am sorry for misinformation, the problem was seen on i686 (not x64). I tested the update again on cubieboard 2 - and this seems to help ( I would guess rpm update to fc20 helped): yum -y --nogpg --releasever=20 update webrtc* grep* vlgothic* xz* polkit* SDL* phonon* abrt* cyrus* easymock* heisenbug* perl* lua* telepathy* system* redha t* 2>&1 | tee 1upd.log ; yum -y --releasever=20 distro-sync 2>&1 | tee 2sync.log please see attached logs for more info
Created attachment 828655 [details] update logs 1
I am encountering exactly the same problem on the i686 with yum-4.11.0.1-2 (I also tried yum-4.11.1-3, but the problem persists). I workarounded it and successfully upgraded the machine by using the yum-3.4.3-99.
Tested on Lenovo T500 with installed fedora core 19 x86_64 and this worked : yum -y update yum rpm yum -y --nogpg --releasever=20 update rpm system* redhat* yum -y --nogpg --releasever=20 distro-sync please see attached logs for more info
Created attachment 832807 [details] upgrade logs 2
Another working iteration ;) yum -y install screen mc ### ssh over wifi, telinit 5, forgot to run under screen rpm -qa > 011.fc19packages.txt yum -y update yum rpm yum -y --nogpg --releasever=20 update system* 2>&1 | tee 012.up.txt yum -y --releasever=20 distro-sync 2>&1 | tee 013.yum.distro.sync.txt yum -y --nogpg --releasever=20 distro-sync 2>&1 | tee 014.yum.distro.sync.txt see attachment for more info
Created attachment 833906 [details] upgrade logs 3
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.