Hide Forgot
This bug file is just in case it already isn't fixed. there is a likelihood that a trouble of this order would have already been caught and fixed by the time of filing of this bug. Description of problem: * After resolving other dependency problems, upgrade fedora 19 to fedora 20 with the following command does not succeed # fedup-cli --network 20 --disablerepo bitcoin --instrepo "http://alt.fedoraproject.org/pub/fedora/linux/updates/testing/20/x86_64/x86_64/os" --verbose * Error is shown and Fedup halts during the downloaded package verify stage "package does not match intended download" error is thrown ilmbase pyliblzma gtkglext-devel gtkglext-lib * An unrelated but exactly same problem, caught by someone else has also encountered this under spurious circumstance [1] so it might may have affected more users. Version-Release number of selected component (if applicable): NA fedup-cli fedora-19 -> fedora-20 How reproducible: possibly not reproducible, and even possible that the issue might get fixed during next build cycle. Steps to Reproduce: 1. give the above command Actual results: a lot of packages are downloaded to /var/tmp/fedora-upgrade fedup-cli does not succeed Troubleshooting * ls/var/tmp/fedora-client/*.drpm The above command reveals that the delta rpms have been downloaded for the previously mentioned four packages instead of the main ".rpm" packages A glance at http://alt.fedoraproject.org/pub/fedora/linux/updates/testing/20/x86_64/ reveals that that only the rpm is not available. Workaround Search the internet and download the following rpm packages directly to /var/tmp/fedora-upgrade folder cd /var/tmp/fedora-upgrade wget "http://alt.fedoraproject.org/pub/fedora/linux/development/20/x86_64/os/Packages/p/pyliblzma-0.5.3-10.fc20.x86_64.rpm" wget "http://alt.fedoraproject.org/pub/fedora/linux/development/20/x86_64/os/Packages/g/gtkglext-devel-1.2.0-21.fc20.x86_64.rpm" wget "http://alt.fedoraproject.org/pub/fedora/linux/development/20/x86_64/os/Packages/g/gtkglext-libs-1.2.0-21.fc20.x86_64.rpm" wget "http://alt.fedoraproject.org/pub/fedora/linux/development/20/x86_64/os/Packages/i/ilmbase-1.0.3-7.fc20.x86_64.rpm" Expected results: fedup-cli should have downloaded the right packages, start installing, end asking to reboot. Additional info: [1] http://www.spinics.net/lists/fedora-testing/msg118717.html
just adding greshko's email-id (as found in redhat-bugzilla) as it was his id on the spinics post.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.