Description of problem: updating to mga6 failed for jsr-305, as version was set to 0 in mga6, while it was 1 in mga5 jsr-305-0-0.18.20130910svn.1.mga6.src.rpm Name : jsr-305 Version : 0 Release : 0.18.20130910svn.1.mga6 vs in mga5: Name : jsr-305 Version : 1 Release : 0.7.20090319svn.6.mga5
Assignee: bugsquad => mageia
I'll push an update.
CC: (none) => mageiaKeywords: (none) => Junior_jobAssignee: mageia => rverschelde
src.rpm: jsr-305-1-0.18.20130910svn.1.mga6 this is the same package, just with a fix in the version field to help upgrade
Keywords: Junior_job => (none)Assignee: rverschelde => qa-bugs
Advisory: ========= Updated jsr-305 package fixes upgrade conflict The version number for jsr-305 in Mageia 6 had been mistakenly decreased to a value lower than Mageia 5's. This update fixes it, resolving an upgrade conflict. RPMs: ===== jsr-305-1-0.18.20130910svn.1.mga6.noarch jsr-305-javadoc-1-0.18.20130910svn.1.mga6.noarch SRPM: ===== jsr-305-1-0.18.20130910svn.1.mga6
I did an unconvention test locally, but I think it's good enough for such an update. On Mageia 6, downloaded the Mageia 5 RPM and tried to install it: # LC_ALL=C urpmi Téléchargements/jsr-305-1-0.7.20090319svn.6.mga5.noarch.rpm A requested package cannot be installed: jsr-305-1-0.7.20090319svn.6.mga5.noarch (in order to keep jsr-305-1-0.18.20130910svn.1.mga6.noarch) So the versions are now correct.
Whiteboard: (none) => MGA6-64-OK
Whiteboard: MGA6-64-OK => advisory MGA6-64-OKKeywords: (none) => validated_updateCC: (none) => sysadmin-bugs
An update for this issue has been pushed to the Mageia Updates repository. http://advisories.mageia.org/MGAA-2017-0029.html
Resolution: (none) => FIXEDStatus: NEW => RESOLVED
Blocks: (none) => 21340