rpmdrake reports firefox-beta and firefox-aurora as available and also: " urpmq firefox-beta firefox-beta" but: "urpmi --test --no-suggests firefox-beta unable to access medium "Core Release (private1)". Installation failed, some files are missing: /mirror/Mageia/distrib/3/x86_64/media/core/release/firefox-beta-21.0-0.b1.mga3.x86_64.rpm You may need to update your urpmi database." It seems that the hdlists were not updated when these packages were removed. I've confirmed on x86_64, but the dates of the hdlist files are the same on i586 and so it probably also affects i586. Reproducible: Steps to Reproduce:
seems the generation was missed after fixing https://bugs.mageia.org/show_bug.cgi?id=8833
CC: (none) => boklmAssignee: bugsquad => sysadmin-bugs
Yeah, the "fixing" of 8833 should not have happend :( It would have been better to leave a few "obsolete" rpms on the mirrors than breaking the tree... As soon as a release tree is forked, it's supposed to stay _frozen_, no-one should touch it after that. drakx tools also assumes /release is frozen, only updates change....
CC: (none) => tmb
In general it should stay frozen, but this was fixed very soon after the release, and was done for a good reason, and unfortunately fixing the hdlists was missed, but that could still be fixed, although not all mirrors would pick it up. These packages should *not* have made it into the final release, and leaving them available would have left people expecting us to support these packages, and cause even more headaches and harassment from users that don't understand why we don't package the beta releases for stable and instead only package the stable (aka ESR) releases. The reason it was missed to delete them before the release is because of all of teh last-minute rushing that happened for the final release. We need to be more careful next time and make sure all the boxes are checked off on the pre-release TODO list before doing the final branching and release. We already had that this needed to be deleted listed in pre-release TODO list bug, so it shouldn't have been forgotten.
CC: (none) => luigiwalser
It does not matter if it "was fixed very soon after the release", it was still done too late. as for "leaving them available would have left people expecting us to support these packages" a simple obsoletes in firefox packages would fix that part. Anyway, tree stays frozen.
Status: NEW => RESOLVEDResolution: (none) => WONTFIX
CC: boklm => (none)