Bug 194303 - Error: Missing Dependency: libXaw.so.7
Summary: Error: Missing Dependency: libXaw.so.7
Alias: None
Product: Fedora
Classification: Fedora
Component: libXaw   
(Show other bugs)
Version: rawhide
Hardware: All Linux
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2006-06-07 02:18 UTC by sangu
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-06-07 07:05:52 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description sangu 2006-06-07 02:18:42 UTC
Description of problem:
Installing libXaw-1.0.2-2.i386.rpm with yum,
Error: Missing Dependency: libXaw.so.7 is needed by package xorg-x11-xkb-utils
Error: Missing Dependency: libXaw.so.7 is needed by package xorg-x11-server-utils
Error: Missing Dependency: libXaw.so.7 is needed by package xterm
Error: Missing Dependency: libXaw.so.7 is needed by package xorg-x11-utils
Error: Missing Dependency: libXaw.so.7 is needed by package xorg-x11-apps

$ rpm -qp --provides  libXaw-1.0.2-2.i386.rpm
libXaw = 1.0.2-2

$ rpm -qpl libXaw-1.0.2-2.i386.rpm | grep libXaw.so.7

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

How reproducible:

Steps to Reproduce:
1. $yum update libXaw
Actual results:

Expected results:

Additional info:
$ rpm -q --provides libXaw-1.0.2-1
libXaw = 1.0.2-1

Comment 1 Mike A. Harris 2006-06-07 07:05:52 UTC
Numerous rpm packages have recently started failing to build, claiming that
XAW could not be found, even though the packages were installed correctly.
This was first reported to us in an xorg-x11-resutils bug, which ./configure
was unable to detect XAW being present.

Additionally, many people have experienced the error you are reporting
above, which is caused by the same problem.  Yesterday we investigated this,
and oddly enough, the problem was not reproduceable on rpmbuild builds,
nor in beehive.  It only occured when building using mock.

The library would build, and get packaged seemingly ok, but nothing could
find it after that.  The problem was tracked down by Bill Nottingham, who
determined that the libXaw sonames were being incorrectly generated.  He
further tracked the problem down to being a missing build dependency.

A new libXaw package has been built with:

BuildRequires: ed

This allows it to build correctly and get the right soname.  Assuming there
are no other hidden issues, all packages that require libXaw should be
buildable now, and the reported error above should vanish as well.

It is possible that all software which links to libXaw may need to be
recompiled, so if you encounter any problems, please attempt to recompile
the given application's src.rpm to see if that fixes it before reporting
a bug against that component.


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