Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 662732 - UPX bundles lzma library -- and incorrectly does so in a form that reaches into ../../SOURCES/lzma465.tar.bz2
Summary: UPX bundles lzma library -- and incorrectly does so in a form that reaches in...
Keywords:
Status: CLOSED DUPLICATE of bug 564522
Alias: None
Product: Fedora
Classification: Fedora
Component: upx
Version: rawhide
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 564522 596461
Blocks: DuplicSysLibsTracker
TreeView+ depends on / blocked
 
Reported: 2010-12-13 18:15 UTC by R P Herrold
Modified: 2011-04-05 18:00 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 564522
Environment:
Last Closed: 2011-04-05 18:00:55 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description R P Herrold 2010-12-13 18:15:48 UTC 
UPX bundles lzma library -- and incorrectly does so in a form that reaches into ../../SOURCES/lzma465.tar.bz2

+++ This bug was initially created as a clone of Bug #564522 +++

Description of problem:
the lzma sdk is bundled in our upx package.  This is not allowed and must be stopped.  From the looks of https://bugzilla.redhat.com/show_bug.cgi?id=501636 this change is only to enable lzma compression so if worse comes to worse we can remove the support and still have a usable package.  It would be better to find a solution that lets us unbundle liblzma and still retain the functionality, though.
========================

new content:

but ALSO, it is using buildsystem relative paths to reach up into ../../SOURCES, rather than carrying a clean reference to SOURCE1

I don't quite understand how this can work except for strange co-incidences in a particular build system as to path names

This can be fixed directly, pending a resolution on #564522's issue

-- Russ herrold
Comment 1 Gwyn Ciesla 2011-04-05 18:00:55 UTC 

*** This bug has been marked as a duplicate of bug 564522 ***
Note You need to log in before you can comment on or make changes to this bug.