It looks like the software version of the Mageia package is newer (0.5) than the MDV package (0.1), but because of the weird version string, RPM sees the Mageia 1 package as version 0, while the MDV one is 0.1 (0.1-1.0.2mdv2010.0). It looks like this happened because the package was imported from Fedora instead of MDV, and the version was not normalized. No epoch was used in the Mageia 1 package, so this package will not be upgraded when upgrading from MDV.
pushed on 1, 2 and cauldron
Assignee: dmorganec => bugsquad
Thanks D Morgan. No functional changes were made, so it should be sufficient to verify that they install. Advisory ======== This update fixes the jsr-305 package so that it will install properly when upgrading from Mandriva 2010.2. Packages in core/updates_testing: jsr-305-1-0.5.20090319svn.1.mga1.noarch.rpm jsr-305-javadoc-1-0.5.20090319svn.1.mga1.noarch.rpm jsr-305-1-0.7.20090319svn.2.mga2.noarch.rpm jsr-305-javadoc-1-0.7.20090319svn.2.mga2.noarch.rpm from SRPMS: jsr-305-1-0.5.20090319svn.1.mga1.src.rpm jsr-305-1-0.7.20090319svn.2.mga2.src.rpm
CC: (none) => dmorganecVersion: 1 => 2Assignee: bugsquad => qa-bugsWhiteboard: (none) => MGA1TOO
"No functional changes were made" = Only the epoch tag was changed in the packages. No patch added, no version change, etc. Packages install cleanly on Mageia 1 64.
CC: (none) => stormiWhiteboard: MGA1TOO => MGA1TOO MGA1-64-OK
Installation goes fine on Mageia 1 32. I haven't tested upgrade from Mandriva 2010.2 version numbers from the RPMs themselves guarantee that it will work better with this update : Mandriva: jsr-305-0.1-1.0.2mdv2010.0.noarch.rpm Mageia 1 release: jsr-305-0-0.5.20090319svn.1.mga1.src.rpm Mageia 1 updates: jsr-305-1-0.5.20090319svn.1.mga1.noarch.rpm Mageia 2 release: jsr-305-0-0.7.20090319svn.2.mga2.noarch.rpm Mageia 2 updates: jsr-305-1-0.7.20090319svn.2.mga2.noarch.rpm Just one question: what does the version 1 mean for this package, as compared to 0 previously or 0.1 in mdv? Is it an arbitrary version number?
Whiteboard: MGA1TOO MGA1-64-OK => MGA1TOO MGA1-64-OK? MGA1-32-OK?
(In reply to comment #4) > Just one question: what does the version 1 mean for this package, as compared > to 0 previously or 0.1 in mdv? Is it an arbitrary version number? It's as meaningless as it was before and is still "wrong," as the real versions are 0.5 and 0.7, but the weird meaningless 0 in the version field is because that's how it is in Fedora and this package was imported into Mageia from Fedora instead of being imported from Mandriva. It probably doesn't matter though.
updates well on Mageia 2 x86_64 too
Whiteboard: MGA1TOO MGA1-64-OK? MGA1-32-OK? => MGA1TOO MGA1-64-OK? MGA1-32-OK MGA2-64-OK
tested update path Mageia 1 64
Whiteboard: MGA1TOO MGA1-64-OK? MGA1-32-OK MGA2-64-OK => MGA1TOO MGA1-64-OK MGA1-32-OK MGA2-64-OK
Tested update mga2 64 Validating See comment 2 for advisory and srpms for mga1 and 2 Could sysadmin please push from core/updates_testing to core/updates Thanks!
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugsHardware: i586 => AllWhiteboard: MGA1TOO MGA1-64-OK MGA1-32-OK MGA2-64-OK => MGA1TOO MGA1-64-OK MGA1-32-OK MGA2-64-OK mga2-64-OK
mga2-32 in previous comment, oops.
Whiteboard: MGA1TOO MGA1-64-OK MGA1-32-OK MGA2-64-OK mga2-64-OK => MGA1TOO MGA1-64-OK MGA1-32-OK MGA2-64-OK mga2-32-OK
Update pushed: https://wiki.mageia.org/en/Support/Advisories/MGAA-2012-0101
Status: NEW => RESOLVEDCC: (none) => tmbResolution: (none) => FIXED