| Summary: | jsr-305 is older in Mageia 1 than in MDV 2010.1 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | David Walser <luigiwalser> |
| Component: | RPM Packages | Assignee: | QA Team <qa-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | dmorganec, stormi-mageia, sysadmin-bugs, tmb |
| Version: | 2 | Keywords: | validated_update |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | MGA1TOO MGA1-64-OK MGA1-32-OK MGA2-64-OK mga2-32-OK | ||
| Source RPM: | jsr-305-0-0.5.20090319svn.1.mga1.src.rpm | CVE: | |
| Status comment: | |||
|
Description
David Walser
2012-02-15 02:46:33 CET
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) =>
dmorganec "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) =>
stormi 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?
Samuel Verschelde
2012-07-08 20:14:01 CEST
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_update 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 =>
RESOLVED |