+++ This bug was initially created as a clone of Bug #507982 +++ Description of problem: Cannot install new popt-devel due to biarch conflict. A similar popt Bug 701891 points to the graphviz Bug 507982. Version-Release number of selected component (if applicable): popt-devel-1.13-9.fc16 How reproducible: Always. Steps to Reproduce: Install popt-devel.{i686,x86_64} yum update to latest Rawhide Actual results: 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-9.fc16.x86_64 and popt-devel-1.13-9.fc16.i686 file /usr/share/doc/popt-devel-1.13/html/findme_8h__dep__incl.png conflicts between attempted installs of popt-devel-1.13-9.fc16.x86_64 and popt-devel-1.13-9.fc16.i686 file /usr/share/doc/popt-devel-1.13/html/poptint_8h.html conflicts between attempted installs of popt-devel-1.13-9.fc16.x86_64 and popt-devel-1.13-9.fc16.i686 file /usr/share/doc/popt-devel-1.13/html/poptint_8h__dep__incl.map conflicts between attempted installs of popt-devel-1.13-9.fc16.x86_64 and popt-devel-1.13-9.fc16.i686 file /usr/share/doc/popt-devel-1.13/html/poptint_8h__dep__incl.png conflicts between attempted installs of popt-devel-1.13-9.fc16.x86_64 and popt-devel-1.13-9.fc16.i686 file /usr/share/doc/popt-devel-1.13/html/poptparse_8c__incl.png conflicts between attempted installs of popt-devel-1.13-9.fc16.x86_64 and popt-devel-1.13-9.fc16.i686 file /usr/share/doc/popt-devel-1.13/html/system_8h__incl.png conflicts between attempted installs of popt-devel-1.13-9.fc16.x86_64 and popt-devel-1.13-9.fc16.i686 Expected results: No conflicts Additional info:
See also Bug #432683 which claims the problem was fixed at one point. Better fix would be to build the Doxygen documentation on a single architecture. Best fix, IMO, would be to leave it on a web site.
There can be also popt-doc.noarch Required by popt-devel.
Version-Release number of selected component (if applicable): popt-1.13-9.fc17
Can someone please reassign this to popt? As a graphviz upstream developer I don't accept this as a graphviz issue. We try to make images visually identical across all formats and architectures, but we cannot assure that the generated PNG, JPEG, GIF, etc. files are bit-for-bit identical, or that they contain the same meta-information - such as timestamps.
The graphviz problem with ongoing fixes is Bug 827927. For popt I proposed Comment 2 independent of Bug 827927.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. 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 Fedora version prior to Fedora 16'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 Fedora 16 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 Fedora, you are encouraged to click on "Clone This Bug" 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
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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 Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.