Here is an update candidate to fix the problem mentioned in summary. Someone managed somehow to provide an update that has the exact same version and release than the one in core/release. So I bumped the subrel and submitted a new build to updates_testing. *** Advisory *** The complete package name (including version and release) of libcroco0.6_3-0.6.5-1.mga2 was exactly the same in the Core Release and Core Updates media. It must always be different, with a higher release or version in Core Updates. This update fixes this issue by providing libcroco0.6_3-0.6.5-1.1.mga2 in Core Updates. *** SRPM *** libcroco0.6-0.6.5-1.1.mga2.src.rpm *** RPMS *** libcroco0.6_3-0.6.5-1.1.mga2.i586.rpm libcroco-devel-0.6.5-1.1.mga2.i586.rpm libcroco0.6-utils-0.6.5-1.1.mga2.i586.rpm libcroco0.6-debug-0.6.5-1.1.mga2.i586.rpm lib64croco0.6_3-0.6.5-1.1.mga2.x86_64.rpm lib64croco-devel-0.6.5-1.1.mga2.x86_64.rpm libcroco0.6-utils-0.6.5-1.1.mga2.x86_64.rpm libcroco0.6-debug-0.6.5-1.1.mga2.x86_64.rpm Reproducible: Steps to Reproduce:
Hardware: i586 => All
This is INVALID. This package was *hard linked* into core/updates because of Bug 2317 during the update for Bug 7369. Sysadmins, please remove libcroco0.6 from Mageia 2 core updates_testing.
CC: (none) => luigiwalser, qa-bugsAssignee: qa-bugs => sysadmin-bugs
Nooo TBWNWDNM strikes again :(
lol, my bad, sorry for that, TBWNWDNM got me :(
Summary: There is the exact same version of libcroco0.6 in core/release and core/updates => Remove update candidate for libcroco0.6 (was: There is the exact same version of libcroco0.6 in core/release and core/updates)
Samuel, make sure you revert your SVN changes too if you haven't yet.
Done. Benefit of my work: now in SVN spec and sources match the version in core/updates, which was not the case before (aborted big gnome update left SVN with lots of unsubmitted changes)
Just removed by tmb.
Status: NEW => RESOLVEDResolution: (none) => INVALID