Bug 673452

I'm still seeing this myself:


Transaction Check Error:
  file /usr/share/systemtap/tapset/glib.stp from install of glib2-devel-2.28.5-2.fc15.i686 conflicts with file from package glib2-devel-2.28.5-2.fc15.x86_64
  file /usr/share/systemtap/tapset/gobject.stp from install of glib2-devel-2.28.5-2.fc15.i686 conflicts with file from package glib2-devel-2.28.5-2.fc15.x86_64

Created attachment 491402 [details]
specfile fix

fix for tip of f15/master glib2 git branch

The above patch allows me to install both i686 and x86_64 devel packages, tested locally with a mock build.

-devel packages are not supposed to be parallel installable. multilib only means that library packages are parallel installable.

Matthias:

this is absolutely a bug.  -devel packages install symlinks required for linking, like:
/usr/lib/libglib-2.0.so

Without this you must specify the exact library path when linking 32-bit libraries (meaning you can't use pkgconfig).

Also, this is a regression.  glib2-devel was parallel installable on f14.

Please either repon or apply my patch.  I am glad to rework it if you have specific comments on it.

yours,
Bobby

> -devel packages are not supposed to be parallel installable. multilib only
> means that library packages are parallel installable.

Do you have any packaging recommendations or similar statement to motivate that claim?

It was the first time I have heard it, and I was very surprised.  It is also the first time I see a bug report about multilib conflict closed without a fix.

Furthermore, if it was true, there would not be much point of providing multilib devel packages in the first place.  It is a rare 64 bit system that will have the 32 bit devel packages but not the corresponding 64 bit devel package.

*** Bug 697138 has been marked as a duplicate of this bug. ***

This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 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 this bug is closed as described in the policy above.

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.

Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.