Description of problem: After installing and configuring either a specific mirror or MIRRORLIST, and enabling Tainted Release and Tainted Update repositories, Mageia Update does not find any packages for the "list of Updates." A search for "vlc" in "Software Management" shows the tainted versions marked as updates, but not checked. Prior behavior has been to automatically list the tainted versions of several packages as updates, if the tainted repositories were enabled. I was able to install software from the tainted repositories in "Software Management," so the connection is good. Also, "updating" the repositories made no difference. I do not know if non-tainted packages are not being flagged too, as I do not know if any are currently waiting in the other update repositories. Version-Release number of selected component (if applicable): Seen on the June 7 Mageia 5 i586 KDE LiveDVD and the June 9 Classical x86-64 DVD, both installed from usb media. I have not tried the Classical i586 DVD yet, but I have no doubt that the same condition exists. How reproducible: Every time I try Mageia Update Steps to Reproduce: 1. Install 2. Configure and enable tainted repositories 3. Attempt to update packages Reproducible: Steps to Reproduce:
Priority: Normal => release_blocker
Thanks for the report. I can't judge if it's a bug or a wanted behaviour, so I'm assigning it to the maintainer. It looks like wanted behaviour since tainted/release is not an updates medium (unless you mark is as such). This bug report does not qualify for being a release blocker, since it can be fixed with a later update, and the update applet will remain red with an exclamation mark until users install the available updates (so an update to MageiaUpdate would get installed in the end).
Priority: release_blocker => HighAssignee: bugsquad => thierry.vignaud
Well, perhaps what I've been seeing in the many Cauldron installs is wanted behavior for Cauldron, but not for an Official release. It's been over a year since I did a non-cauldron install, so I could easily have forgotten what happened with Mageia 4. I do remember that this was the behavior in Mandriva and Mageia 1, but somehow I got the idea that it had changed somewhere along the line since then.
Its by design. Mageia update only tracks medias tagged as updates
CC: (none) => tmbStatus: NEW => RESOLVEDResolution: (none) => INVALID