Description of problem: Transaction Check Error: file /usr/share/doc/popt-devel-1.13/html/structpoptContext__s__coll__graph.png from install of popt-devel-1.13-5.fc11.i586 conflicts with file from package popt-devel-1.13-5.fc11.x86_64 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Ask the doxygen folks to fix their broken software, please. *** This bug has been marked as a duplicate of bug 507982 ***
This problem I had to workaround already for 20+ times by rpm -U --force, while graphviz may have some bugs documentation should be in popt-doc.noarch package anyway and this problem will no longer appear. Transaction Check Error: file /usr/share/doc/popt-devel-1.13/html/findme_8c__incl.png conflicts between attempted installs of popt-devel-1.13-10.fc17.i686 and popt-devel-1.13-10.fc17.x86_64 ...
Created attachment 575997 [details] Fix - introduce -devel-doc subpackage. There are many -devel-doc subpackages in Fedora. It makes sense as in 99% of installation cases of -devel one needs it for some other package rebuild or even development, not for one own's development using popt. The size savings are very significant: 24K popt-devel-1.13-11.fc17.x86_64 12K popt-devel-1.13-11.fc17.x86_64.rpm 1.6M popt-devel-doc-1.13-11.fc17.x86_64 332K popt-devel-doc-1.13-11.fc17.x86_64.rpm Please push it for F-15, F-16, F-17 and master, it is still breaking all the mock buildroots.
ping Transaction Check Error: file /usr/share/doc/popt-devel-1.13/html/findme_8c__incl.png conflicts between attempted installs of popt-devel-1.13-10.fc17.i686 and popt-devel-1.13-10.fc17.x86_64
ping, should I therefore start the non-responsive maintainer process?
I still see the root cause in doxygen/graphviz.
Issue reported against graphviz in bug #827927.
While I agree with graphviz I still find the -doc split as another improvement, coincidentally also fixing the problem.
This is hijacking of this Bug for an unrelated fix.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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 Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Still a problem even in Rawhide, last time I was forcing it yesterday: popt-devel-1.13-12.fc18 rpm --force -U --nodeps http://kojipkgs.fedoraproject.org//packages/popt/1.13/12.fc18/i686/popt-devel-1.13-12.fc18.i686.rpm http://kojipkgs.fedoraproject.org//packages/popt/1.13/12.fc18/x86_64/popt-devel-1.13-12.fc18.x86_64.rpm
This has gone on long enough... The normal route would of course be creating a noarch -devel-docs or similar sub-package, but in this case the doxygen generated documentation isn't helpful to somebody wanting to *use* popt, its only of any use for somebody hacking internals of popt itself. And anybody hacking popt itself will obviously need to get the full source etc, at which point pre-generated docs are of no real use anyway. So I actually went ahead and just axed the useless doxygen generated documentation. Poof, wholly unnecessary problem gone.