Bug 911597

Summary: systemd-devel.x86_64 and systemd-devel.i686 not co-installable
Product: [Fedora] Fedora Reporter: Fabio Valentini <decathorpe>
Component: systemdAssignee: systemd-maint
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: contact, harald, johannbg, lnykryn, metherid, msekleta, nmiell, notting, plautrba, systemd-maint, vpavlin, william, zboszor, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 23:15:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 910830, 1018023    
Bug Blocks:    

Description Fabio Valentini 2013-02-15 12:36:32 UTC
The packages

systemd-devel-197-1.fc18.1.x86_64 and
systemd-devel-197-1.fc18.1.i686

are not co-installable by yum, following file seems to be in both packages, as per the error output of the yum transaction test:

"file /usr/share/gtk-doc/html/libudev/ch01.html from install of systemd-devel-197-1.fc18.1.i686 conflicts with file from package systemd-devel-197-1.fc18.1.x86_64"

Reproduce the error (on a 64bit machine):
yum install systemd-devel.i686 systemd-devel.x86_64



This (packaging?) error makes it difficult to build 32bit libraries that link against (32bit) libudev (without forcing rpm to install the package anyway).

Comment 1 Lennart Poettering 2013-05-13 21:15:05 UTC
*** Bug 961464 has been marked as a duplicate of this bug. ***

Comment 2 Zoltan Boszormenyi 2013-05-24 15:37:16 UTC
The same error happens on F19 beta:

Transaction check error:
  file /usr/share/gtk-doc/html/libudev/ch01.html from install of systemd-devel-204-3.fc19.i686 conflicts with file from package systemd-devel-204-3.fc19.x86_64

Comment 3 Harald Hoyer 2013-06-03 12:56:04 UTC
Will be fixed automatically, if bug 910830 is fixed and systemd was rebuilt with it.

Comment 4 Lennart Poettering 2013-06-19 13:49:44 UTC
*** Bug 974915 has been marked as a duplicate of this bug. ***

Comment 5 Zbigniew Jędrzejewski-Szmek 2013-10-06 21:53:17 UTC
F19 seems to be OK:
# rpm -q systemd-devel
systemd-devel-204-16.fc19.i686
systemd-devel-204-16.fc19.x86_64

F18 still has gtk-doc-1.18-3, so I'm assuming that it's not fixed.

Comment 6 Fedora End Of Life 2013-12-21 11:25:47 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

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.

Comment 7 Fedora End Of Life 2014-02-05 23:15:53 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.