Bug 142241 - libxslt-devel: remove .la files or fix Requires
libxslt-devel: remove .la files or fix Requires
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: libxslt (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Veillard
: Reopened
Depends On:
  Show dependency treegraph
Reported: 2004-12-08 09:43 EST by Rex Dieter
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version: 1.1.13-2
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-06-08 09:32:06 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Rex Dieter 2004-12-08 09:43:27 EST
/usr/lib/libexslt.la contains:
dependency_libs=' -lgcrypt -lgpg-error ...

So, either
1.  Remove all /usr/lib/lib*.la files from the package (preferred)
2.  Add to -devel subpkg:
Requires: libgcrypt-devel
Requires: libgpg-error-devel
Comment 1 Daniel Veillard 2005-03-14 11:49:18 EST
Both fixed on rawhide,


Comment 2 Rex Dieter 2005-12-01 11:06:17 EST
FYI, the brokenness described here is also present in libxslt from FC4/RHEL4
(and I think FC3, but I don't have a box to check) -> Reopening, retargetting FC4.

For these, the best fix is option 2 so as not to introduce any binary
Comment 3 Daniel Veillard 2006-06-08 08:33:30 EDT
Won't fix for FC4, sorry, fixed in FC5

Comment 4 Rex Dieter 2006-06-08 08:50:08 EDT
> Won't fix for FC-4

The dependancies at least do appear to be fixed... at least in cvs,
libxslt/FC-4/libxslt.spec includes for -devel subpkg:
Requires: libgcrypt-devel

However, the latest RHEL4 release (libxslt-1.1.11-1 that I can see) is still
broken wrt this.  (Geesh, do I really have to file a separate bug for *every*
release?).  Reopening, targeting -> RHEL4 this time.
Comment 5 Daniel Veillard 2006-06-08 09:32:06 EDT
I won't change a RHEL4 package and go though the work of going though a
RHEL4 update process without an existing breakage on an app which can
be identified clearly and reported as a customer serious problem. 
So, to be honnest I don't expect to push an update for RHEL4 due to this, 


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