Description of problem: if you enable the core backport testing media, go in rpmdrake, type libreoffice, the version 4.2.0 is proposed as an update, it looks bad to propose this. Reproducible: Steps to Reproduce:
Created attachment 5001 [details] screenshot
Assignee: bugsquad => thierry.vignaud
I think that this may be one of the un-fixed Mandriva bugs that I referred to in: https://bugs.mageia.org/show_bug.cgi?id=12766#c5 I suspect that there may be more, that have not yet become apparent.
On second thought, is this not normal behaviour? If you enable a repo, rpmdrake will find updates in that repo. Try with, for example core/updates_testing. (You'll need to update the media after enabling it.) (I missed originally that you had enabled the backports repo.)
backport are not updates, if the tag update (only set for core/nonfree/tainted updates as default) is not set, it should not be shown imho.
Keywords: (none) => PATCH
Keywords: PATCH => (none)
My understanding is that rpmdrake does not use the "update" tag. It determines which packages can be updated by comparing the versions of the installed packages with the versions of the available packages. It uses all active sources. FWIW, this behaviour is long-established and IMHO useful. It makes it possible, for example, to use rpmdrake to selectively update a package with one from an updates_testing or third party source without tagging that source as an "update" source. The "update" tag is relevant for MageiaUpdate, which reports updates only if they are in active sources tagged as "update" sources. You can thus keep an updates_testing source enabled and continue to update normally using MageiaUpdate, which will ignore the updates_testing source so long as it is not tagged as an "update" source. This difference between rpmdrake and MageiaUpdate is a bit like the difference between: urpmq --auto-select and urpmq --update --auto-select
Indeed.
Status: NEW => RESOLVEDResolution: (none) => INVALID