Description of problem: During fedup test day (https://fedoraproject.org/wiki/Test_Day:2015-04-21_FedUp) I tried upgrading from Fedora 20 to 22, and got a weird warning message about a potential yum conflict, even though both versions mentioned in the message were identical. Version-Release number of selected component (if applicable): fedup-0.9.2-1.fc20.noarch.rpm How reproducible: 100% Steps to Reproduce: 1. fedup --network 22 --product workstation --instrepo https://dl.fedoraproject.org/pub/alt/stage/22_Beta_RC3/Server/(arch)/os --nogpgcheck 2. 3. Actual results: After downloading everything, but prior to rebooting, fedup complains: ... setting up update... Warning: Group base-x does not have any packages to install. finding updates 100% [========================================================] WARNING: potential problems with upgrade yum-3.4.3-152.fc20.noarch (replaced by yum-3.4.3-505.fc22.noarch) requires yum-3.4.3-152.fc20.noarch (replaced by yum-3.4.3-505.fc22.noarch) verify local files 100% [=====================================================] ... Expected results: How can it be a problem if the versions are identical? Either there really IS a version clash that may cause upgrade grief (in which case, there's a bug in the error message for not printing correct version numbers in at least one of the two strings), or there is NO problem and the warning should not be issued. Since fedup followed by reboot succeeded at upgrading me (modulo other bugs, like bug 1209941), and a subsequent 'dnf update' ran without errors in the upgraded system, I think this is a case of the latter (we should not be warning). Additional info:
I am facing a similar issue when trying to use fedup for f21->f22 upgrading: On fc21: # fedup --network 22 ... WARNING: potential problems with upgrade sqlitebrowser-3.5.1-1.fc21.x86_64 (replaced by sqlitebrowser-3.6.0-1.fc22.x86_64) requires sqlitebrowser-3.5.1-1.fc21.x86_64 (replaced by sqlitebrowser-3.6.0-1.fc22.x86_64) ... WARNING: problems were encountered during transaction test: broken dependencies sqlitebrowser-3.6.0-1.fc22.x86_64 requires sqlitebrowser-3.6.0-1.fc22.x86_64 ... A probably related observation on fc22: # dnf install sqlitebrowser Error: nothing provides libqhexedit-qt5.so.1()(64bit) needed by sqlitebrowser-3.6.0-1.fc22.x86_64
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.
bumping to F21 given comment 1
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.