(In reply to comment #0)
>   file /usr/share/systemtap/tapset/glib.stp conflicts between attempted
> installs of glib2-devel-2.28.6-2.fc15.x86_64 and glib2-devel-2.28.6-2.fc15.i686
>   file /usr/share/systemtap/tapset/gobject.stp conflicts between attempted
> installs of glib2-devel-2.28.6-2.fc15.x86_64 and glib2-devel-2.28.6-2.fc15.i686

For the .stp files, you might take a lead from python-libs, which names those -32/-64 to allow multilib.  SystemTap is able to handle the same aliases defined in separate files.

Also happens with latest update to 2.28.8-1.fc15:

file /usr/share/glib-2.0/gdb/glib.pyc conflicts between attempted installs of glib2-devel-2.28.8-1.fc15.x86_64 and glib2-devel-2.28.8-1.fc15.i686
  file /usr/share/glib-2.0/gdb/glib.pyo conflicts between attempted installs of glib2-devel-2.28.8-1.fc15.x86_64 and glib2-devel-2.28.8-1.fc15.i686
  file /usr/share/glib-2.0/gdb/gobject.pyc conflicts between attempted installs of glib2-devel-2.28.8-1.fc15.x86_64 and glib2-devel-2.28.8-1.fc15.i686
  file /usr/share/glib-2.0/gdb/gobject.pyo conflicts between attempted installs of glib2-devel-2.28.8-1.fc15.x86_64 and glib2-devel-2.28.8-1.fc15.i686
  file /usr/share/systemtap/tapset/glib.stp conflicts between attempted installs of glib2-devel-2.28.8-1.fc15.x86_64 and glib2-devel-2.28.8-1.fc15.i686
  file /usr/share/systemtap/tapset/gobject.stp conflicts between attempted installs of glib2-devel-2.28.8-1.fc15.x86_64 and glib2-devel-2.28.8-1.fc15.i686

Any workaround?  I have projects that require 32-bit.

I'd like to see some progress here too.  The same happens on F16.

I believe it can be solved with a simple rename in glib2.spec %install, like:

  # rename systemtap files to allow multilib
  rename -- .stp -%{__isa_bits}.stp \
    $RPM_BUILD_ROOT%{_datadir}/systemtap/tapset/*.stp


Also, please consider adding to "%files devel":
  %dir %{_datadir}/systemtap/
  %dir %{_datadir}/systemtap/tapset/
since there's no "Requires: systemtap" to make sure that those paths are owned.
(see also bug #744907)

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 occurs in F17 as of glib2-devel-2.32.4-1.fc17.x86_64/i686

Still happens in glib2-devel-2.32.4-1.fc17

*** This bug has been marked as a duplicate of bug 718404 ***