| Summary: | Package not upgraded (bigger EVR in mga4 than in mga5) | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Marc Krämer <mageia> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | ennael1, luigiwalser, makowski.mageia, pterjan, thierry.vignaud |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | python-pillow-2.6.2-1.mga5.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Marc Krämer
2015-03-01 23:01:05 CET
Marc Krämer
2015-03-01 23:04:43 CET
Summary:
Package not updagraded =>
Package not upgraded Well 2.6.2-1.mga5 is lower than 2.6.2-1.1.mga4... It seems an update to Mageia 4 was made with a higher release number than the Cauldron one. CC:
(none) =>
pterjan Thanks. Freeze push requested for a rebuild in Cauldron. CC:
(none) =>
luigiwalser (In reply to Pascal Terjan from comment #1) We should script a check against all packages... CC:
(none) =>
thierry.vignaud
Thierry Vignaud
2015-03-02 10:58:09 CET
Summary:
Package not upgraded =>
Package not upgraded (bigger EVR in mga4 than in mga5) $ ruby oldver.rb python-django14 (4=0:1.4.18-1.1.mga4, 5=0:1.4.18-1.mga5) python-pillow (4=0:2.6.2-1.1.mga4, 5=0:2.6.2-1.mga5) Freeze push requested for python-django14 too. Philippe, please be careful to remove subrels when updating packages for stable updates. CC:
(none) =>
makowski.mageia Sorry, and thanks for the correction sorry for the late reply - I didn't recognize the different versions, but for release urpmi should update the package by the new version. python-pillow-2.6.2-2.mga5 is pushed in Cauldron. Still waiting on python-django14. CC:
(none) =>
ennael1 python-django14-1.4.18-2.mga5 pushed in Cauldron. Thanks again for the report(s). Status:
NEW =>
RESOLVED (In reply to M K from comment #7) > sorry for the late reply - I didn't recognize the different versions, but > for release urpmi should update the package by the new version. No. urpmi uses rpmlib for comparisons so both compare EVR (Epoch:Version-Release). That has always been like this. |