| Summary: | rpm-1:4.9.1.3-2.1.mga2.x86_64 conflicts | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Stefano Negro <stblack> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | mageia, stormi-mageia, tmb |
| Version: | 2 | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | rpm | CVE: | |
| Status comment: | |||
|
Description
Stefano Negro
2012-12-05 16:35:46 CET
Manuel Hiebel
2012-12-06 09:50:07 CET
CC:
(none) =>
mageia, tmb Hmm, This would appear to be unrelated specifically to the latest update, in that the rpmsign binary has been listed twice in the spec (once in the main package and once in the rpm-sign package) for some time. The update only included this single change: http://svnweb.mageia.org/packages?view=revision&revision=273416 The problem was introduced in: http://svnweb.mageia.org/packages?view=revision&revision=185007 which was before mga2 shipped and thus would have been a problem in your existing install also (likely it allowed a silent install at the time due to them being the same file and thus "not conflicting" and it's only coming to light now that they have different validation hashes) I guess we should remove it from the main package and keep it in the separate sub-package... That said I know nothing about this, and it might in some small way break signing on the infrastructure... I guess it works OK for cauldron now that the binary was removed from the main package. Thomas WDYT? (strangely /usr/share/man/man8/rpmsign.8.xz is in the "rpm" package on cauldron... so it looks like it's still affecting rpm there, even if the binary itself is in the rpm-sign package). Is that problem still present in Mageia 2? CC:
(none) =>
stormi
Samuel Verschelde
2013-08-29 16:48:21 CEST
Keywords:
(none) =>
NEEDINFO This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad Status:
NEW =>
RESOLVED |