This page is about fixing bug 2317.
Planned changes
An update for rpmdrake / urpmi in Mageia 2 will be prepared with the following changes :
- The option to add only update media will be removed, one can only add full media lists (patch exists)
- MageiaUpdate and urpmi --update will pull dependencies from all active medias, instead of only update medias currently (patch exists)
- In the Media Manager gui, the option to enable a backport media should display a warning, or maybe be removed
- the disabled backport medias will be listed in the "update media" menu in rpmdrake, so it's easy to update hdlists for disabled backport medias
- a README.update.urpmi file will be added to notify users of the change
For Mageia 3, the support for backport medias will be improved. Backports media will be flagged as backport in urpmi.cfg and media.cfg, and their hdlists updated automatically. A feature page list the planned changes : Feature:BackportsSupport.
Testing procedure
MageiaUpdate and mgaapplet will have to be tested thoroughly.
For mgaapplet, creating a test case is fairly simple.
Take any update from Core Updates, that has a dependency that only exists in Core Release (which would be the case if Core Release also requires the dependency.
Install the Core Release version.
Uninstall the dependency using "rpm -e --nodeps dependencypackagename". Then use mgaapplet to install the update. Ensure that it does install the dependency from Core Rlease
Ensuring dependencies do not get installed from non-enabled repositories can be done by installing the Core Release version of a package such as audacious, using rpm -e --nodeps audacious-plugins, then installing the update for audacious using mgaapplet without, and then with the tainted repositories enabled, ensuring the correct version of the plugins is selected.
Similar tests should be done for MageiaUpdate, while using it to test an upgrade from Mageia 1 to 2.
