As reported in https://bugs.mageia.org/show_bug.cgi?id=10869#c6 installing an updated version of bind fails, if bind-doc is also installed, as they both have /usr/share/doc/CHANGES. Reproducible: Steps to Reproduce:
Whiteboard: (none) => mga2too
Both packages will actually have whatever the main bind package puts in /usr/share/doc/bind, which is currently (from the %doc line under %files): CHANGES README README.mga FAQ COPYRIGHT Those files should only be in bind or bind-doc, not both.
CC: (none) => guillomovitch, oe
Or as Dave suggested on IRC, if bind-doc is packaging things the upstream Makefiles install in /usr/share/doc/bind, that directory could be renamed /usr/share/doc/bind-doc at the end of %install, which would make the doc directory owned by bind-doc consistent with every other package, and only bind would own the stuff in /usr/share/doc/bind (which would only be things it placed there itself in its own %doc tag). To ensure clean upgrades, bind would conflict with bind-doc <= the current version we have now.
CC: (none) => eeeemail
> that directory could be renamed /usr/share/doc/bind-doc at the end of %install, which would make the doc directory owned by bind-doc consistent with every other package Consistent but wrong: doc for package foo should be in /usr/share/doc/foo, whatever the exact subpackage it is shipped in.
(In reply to Guillaume Rousse from comment #3) > > that directory could be renamed /usr/share/doc/bind-doc at the end of %install, which would make the doc directory owned by bind-doc consistent with every other package > Consistent but wrong: doc for package foo should be in /usr/share/doc/foo, > whatever the exact subpackage it is shipped in. Not wrong, packages ship in /usr/share/doc/foo based on their package name, not SRPM name. Anyway, if you feel strongly about keeping them in /usr/share/doc/bind for some reason, then they should be removed from either bind or bind-doc.
CC: (none) => luigiwalser
Packages ship documentation under a /usr/share/doc subdirectory named after the binary package name by accident, just because %doc macro use the current package name. That doesn't make much sense than a file location, even if just documentation, change just because its distribution granularity changes too.
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 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
Resolution: (none) => OLDStatus: NEW => RESOLVED
Still valid.
Status: RESOLVED => REOPENEDVersion: 3 => CauldronResolution: OLD => (none)Whiteboard: mga2too => MGA4TOO
*** Bug 18997 has been marked as a duplicate of this bug. ***
CC: (none) => bittwister2
Keywords: (none) => Junior_jobAssignee: bugsquad => pkg-bugsWhiteboard: MGA4TOO => MGA5TOO
Fixed in 9.10.4.P2-2.mga6
Resolution: (none) => FIXEDStatus: REOPENED => RESOLVED
(In reply to Guillaume Rousse from comment #9) > Fixed in 9.10.4.P2-2.mga6 Thanks a lot :-) Do you mind fixing it in Mageia 5, too?
Status: RESOLVED => REOPENEDCC: (none) => marja11Version: Cauldron => 5Resolution: FIXED => (none)Whiteboard: MGA5TOO => (none)
We can include the fix with the security update that's currently pending. You can still close this bug.
Depends on: (none) => 18983
Fixed in: http://advisories.mageia.org/MGASA-2016-0332.html
Status: REOPENED => RESOLVEDResolution: (none) => FIXED