Hide Forgot
Description of problem: gpk-update-viewer (the gui updates part of gnome-packagekit) does not seem to fail to the next mirror site when a malfunctioning mirror is selected. Version-Release number of selected component (if applicable): gnome-packagekit-3.2.1-1.fc16.x86_64 How reproducible: Every time Steps to Reproduce: 1. Ensure that the mirror is defective. E.g. the defective nexicom.net sites. 2. Ensure that there is at least one update required. 3. Run the graphical update tool (gpk-update-viewer). 4. Note that no updates are found, and that the tool finishes more quickly than expected. 5. Open a terminal and run sudo yum update 6. Note that yum falls back to a new mirror (twice, because nexicom has two mirrors, both defective), and finds updates that gpk-update-viewer did not. Actual results: As above. Expected results: gpk-update-viewer should find the same updates as yum does. Additional info:
The infrastructure fixes made in the last day have not had any effect upon this bug. This morning, the gui updater reported no changes, and using cli running yum only 10 seconds later reported 7 updates required.
Problem still exists, unchanged. Easily reproduced on two independently staged and updated machines - one fresh install, and one upgrade from F14. How can I turn on some packagekit debugging logs to show the incorrect behaviour in the presence of a broken mirror in at least some detail? Cut/paste of yum updater showing failing mirror site and failure reason that apparently causes the problem: $ sudo yum update Loaded plugins: presto, refresh-packagekit adobe-linux-i386 | 951 B 00:00 rpmfusion-free-updates | 3.3 kB 00:00 rpmfusion-nonfree-updates | 3.3 kB 00:00 updates/metalink | 9.8 kB 00:00 updates | 4.5 kB 00:00 http://fedora.mirror.nexicom.net/linux/updates/16/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates Trying other mirror. updates | 4.5 kB 00:00 ftp://mirror.nexicom.net/pub/fedora/linux/updates/16/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates Trying other mirror. updates | 4.5 kB 00:00 updates/primary_db | 5.6 MB 00:34 Setting up Update Process Resolving Dependencies --> Running transaction check . . .
Happened again this morning: the gui updater found no changes, and an immediate yum update found 21 updates. The gui updater tool is just BROKEN!!! Recommend altering priority to critical, as no action is apparently occurring, and security updates are routinely missed because of this bug.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 'version' of '16'. 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 prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. Thank you for reporting this bug and we are sorry it could not be fixed.