from urpmi rpm:


search_packages: found rpm-4.12.0.1-20.mga5.x86_64 matching rpm
search_packages: found rpm-4.12.0.1-20.2.mga5.x86_64 matching rpm
found package(s): rpm-4.12.0.1-20.mga5.x86_64 rpm-4.12.0.1-20.2.mga5.x86_64
opening rpmdb (root=, write=)
chosen rpm-4.12.0.1-20.2.mga5.x86_64 for rpm|rpm
selecting rpm-4.12.0.1-20.2.mga5.x86_64
set_rejected: rpm-4.12.0.1-20.mga5.x86_64
requiring lib64rpm3[== 1:4.12.0.1-20.2.mga5],librpm.so.3()(64bit),librpmio.so.3()(64bit) for rpm-4.12.0.1-20.2.mga5.x86_64
installed package lib64rpm3-4.12.0.1-20.mga5.x86_64 is conflicting with rpm-4.12.0.1-20.2.mga5.x86_64 (Conflicts: lib64rpm3[<= 1:4.12.0.1-22.mga6])
set_rejected: lib64rpm3-4.12.0.1-20.mga5.x86_64
no packages match lib64rpm3[== 1:4.12.0.1-20.2.mga5] (it is either in skip.list or already rejected)
unselecting rpm-4.12.0.1-20.2.mga5.x86_64
adding a reason to already rejected package rpm-4.12.0.1-20.2.mga5.x86_64: unsatisfied lib64rpm3[== 1:4.12.0.1-20.2.mga5]
Le paquetage demandé ne peut pas être installé :
rpm-4.12.0.1-20.2.mga5.x86_64 (car lib64rpm3[== 1:4.12.0.1-20.2.mga5] est non satisfait)
Désirez-vous tout de même continuer ? (O/n) ^C
[root@localhost manu]# urpmi --debug rpm^C
[root@localhost manu]# cat /etc/urpmi/skip.list 
# Here you can specify the packages that won't be upgraded automatically
# for example, to exclude all apache packages :
# /^apache/

[root@localhost manu]#

I fixed the conflicts on lib(64)rpm3, so the packages are now:

SRPMS:
rpm-4.12.0.1-20.3.mga5.src.rpm

i586:
librpm3-4.12.0.1-20.3.mga5.i586.rpm
librpmbuild3-4.12.0.1-20.3.mga5.i586.rpm
librpm-devel-4.12.0.1-20.3.mga5.i586.rpm
librpmsign3-4.12.0.1-20.3.mga5.i586.rpm
python3-rpm-4.12.0.1-20.3.mga5.i586.rpm
python-rpm-4.12.0.1-20.3.mga5.i586.rpm
rpm-4.12.0.1-20.3.mga5.i586.rpm
rpm-build-4.12.0.1-20.3.mga5.i586.rpm
rpm-sign-4.12.0.1-20.3.mga5.i586.rpm

x86_64:
lib64rpm3-4.12.0.1-20.3.mga5.x86_64.rpm
lib64rpmbuild3-4.12.0.1-20.3.mga5.x86_64.rpm
lib64rpm-devel-4.12.0.1-20.3.mga5.x86_64.rpm
lib64rpmsign3-4.12.0.1-20.3.mga5.x86_64.rpm
python3-rpm-4.12.0.1-20.3.mga5.x86_64.rpm
python-rpm-4.12.0.1-20.3.mga5.x86_64.rpm
rpm-4.12.0.1-20.3.mga5.x86_64.rpm
rpm-build-4.12.0.1-20.3.mga5.x86_64.rpm
rpm-sign-4.12.0.1-20.3.mga5.x86_64.rpm

CC: (none) => tmb

Testing Mageia 5 x64; OK

Using MCC to 'update system' from Updates Testing repos has been giving me hell. I think the update helped.
BEFORE
First, with the earlier rpm update in the list, the whole thing was unuseable. Too long to tell; but the rpm update was *not* automatically offered up front as is usual for it; nor could it be selected.
Second, following IRC advice, I added
 /^rpm/
 /^lib64rpm/
 /^python-rpm/
 /^python3-rpm/
to /etc/urpmi/skip.list and tried again. Then after warnings about taking out fglrx kernel due to conflict with the desktop one, the entire list *was* displayed, all ticked except the rpm update.
Third, I commented out the /etc/urpmi/skip.list above, & tried again. This time, the rpm update (Comment 2) *was* offered up front; and seemed to work. I accepted rpmnew since the previous file contained a long string of irrelevant language codes, which were probably responsible for some of the previous angst.

AFTER
lib64rpm3-4.12.0.1-20.3.mga5
rpm-4.12.0.1-20.3.mga5
lib64rpmbuild3-4.12.0.1-20.3.mga5
Seems to work OK (kernel conflicts apart); updated a couple of independant things from the Updates Testing list - one a lib64 rpm pkg not included by its update. Curious, correct?
Reluctant to OK this until somebody else confirms it.

CC: (none) => lewyssmith

As a matter I've had this update installed on Mageia 5 64bit for a while already since it's a mandatory one to be able to install other update candidates; it works just fine to install update, new packages, or do packaging work.

As for the specific bug fixes:
 --excludedocs seems to work fine
 --whatrecommends works too, e.g.:

# rpm -q --whatrecommends 7kaa-music
7kaa-2.14.5-1.mga5

Whiteboard: (none) => MGA5-64-OK

s/matter/matter of fact/

Theese exact rpms have also been running in cauldron / bs since I restored them to get bs back online on 2015-08-16 so I'd say both i586 and x86_64 has seen a lot of testing...

Validating then. The advisory has been uploaded.

Keywords: (none) => validated_update
Whiteboard: MGA5-64-OK => MGA5-64-OK advisory
CC: (none) => sysadmin-bugs

An update for this issue has been pushed to Mageia Updates repository.

http://advisories.mageia.org/MGAA-2015-0098.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED