Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 223876 - Packaging error: libXmu-devel missing dependencies
Summary: Packaging error: libXmu-devel missing dependencies
Alias: None
Product: Fedora
Classification: Fedora
Component: libXmu
Version: 5
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Søren Sandmann Pedersen
QA Contact:
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2007-01-22 21:21 UTC by Michel Alexandre Salim
Modified: 2018-04-11 16:33 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-05-06 17:48:10 UTC

Attachments (Terms of Use)

Description Michel Alexandre Salim 2007-01-22 21:21:15 UTC
Description of problem:
libXmu-devel as shipped in FC-5 is missing dependencies on several other X
development packages. This causes, among others, the gai RPM in extras to fail
to build for FC-5, due to this dependency chain:

gai -> gtkglext -> libXmu -> libXt

(libXmu-devel does not require libXt-devel in FC-5; it does in FC-6 and upwards). 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. rpm -q --requires libXt
2. rpm -q --requires libXt-devel

Actual results:
A lot of libraries required by libXt are missing -devel counterparts in
libXt-devel's required packages

Expected results:
libXt-devel and probably libX11-devel should be required by libXmu-devel

Additional info:

Comment 1 Espen Stefansen 2007-04-26 17:47:53 UTC
In Rawhide, both libXt-devel and libX11-devel are required by libXmu-devel now.

Comment 2 Matěj Cepl 2007-04-27 07:50:54 UTC
Sorry, my mistake. Espen, it doesn't matter that this was fixed in Rawhide, we
still support FC-5 and the bug should be fixed there to be resolved.

Comment 3 Bug Zapper 2008-04-04 05:41:06 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here: to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out

Comment 4 Bug Zapper 2008-05-06 17:48:08 UTC
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

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

Note You need to log in before you can comment on or make changes to this bug.