Hide Forgot
Description of problem: preupgrade skips RPMs Version-Release number of selected component (if applicable): preupgrade-1.1.9-1.fc14.noarch How reproducible: use it to upgarde, see some rpms not downloaded Steps to Reproduce: 1. 2. 3. Actual results: skipped rpms Expected results: Additional info: See attached log. See two rpms skipped, one other rpm is not even an rpm, I see these not being re-tried.
Created attachment 504125 [details] log
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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" (top right of this page) 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
NOBODY looked into this and added anything to the bug report. This ensures the quality and justification to simply close the bug report. This is just one of many cases where more or less similar situations happen. No solution if provided, no new information is asked nor gets available so the bugzapper emails (there's another bugreport about the loads of nonsens emails they cause) need to `solve` the issues...