I think I've had this bug since at least Mageia 4, maybe earlier (could be a fallback of the GTK+3 port).
When sorting packages by version in drakrpm-update / MageiaUpdate, cherry-picking does not work reliably. If you click on a specific package that has dependencies to install, it will notify you about it, but clicking OK won't select the mentioned dependencies.
If you manage in the end to select all packages that you want to cherry-pick, clicking install will propose only a subset of what you actually selected (and maybe even random other updates that you did not select IIRC).
Maybe the backend does not know that the list is sorted by version, and tries to match positions in the list with the list sorted by name or something like that?
To reproduce, in current mga5:
1. Activate and update testing repos, and mark them as update media (drakrpm-editmedia)
2. Start MageiaUpdate
3. Unselect everything
4. Click on "Version" to sort by versions
5. Try to select all packages of a given version and install them (e.g. systemd 217 in current mga5).
Steps to Reproduce:
I'm assuming that the issue is also valid in Cauldron as there haven't been many changes to rpmdrake in git since version 6.20.
Setting as a release_blocker for now to make sure we try to fix it for Mageia 6.
Really there is a fundamental flaw in the design of MageiaUpdate, as it should not allow you to cherry pick some subpackages but not others that are built from the same SRPM. The checkboxes it should show you should only be for the *SRPM* names of the updateable packages, allowing you to select or deselect those, and for the selected ones, it'll upgrade all subpackages built from that selected package that are installed. If deemed desirable, when you click on one of the SRPM rows, it could in the interface display a list of the actual RPM names it will be updating if chosen.
Yes, it is valid in Cauldron also.
When you for example unselect some package for updating a message is displayed that it's dependencies are unselected too, but this is not reflected by removing their tickmarks - they remain displayed as selected for update.
Moving to a mga7 tracker (it is still allowed to fix this bug now, though ;-) )
Not a release blocker since it can be fixed afterwards, although would be nice to get finally fixed.