Bug 457095 - installation stops when attempting to install package
Summary: installation stops when attempting to install package
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: rpm
Version: 9
Hardware: i586
OS: Linux
low
medium
Target Milestone: ---
Assignee: Panu Matilainen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 457251
TreeView+ depends on / blocked
 
Reported: 2008-07-29 15:50 UTC by Doug
Modified: 2008-07-30 15:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-07-30 15:23:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Doug 2008-07-29 15:50:09 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.1) Gecko/2008071615 Fedora/3.0.1-1.fc9 Firefox/3.0.1

Description of problem:
On attempting to install viking-0.9.4-2.5.i586.rpm got message 
ERROR with rpm_check_debug vs depsolve : rpmlib(PayloadIsLzma) is needed by viking...please report this error in bugzilla

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


How reproducible:
Always


Steps to Reproduce:
1.Double-click package file
2.Enter root password
3.wait

Actual Results:


Expected Results:


Additional info:

Comment 1 Florian Festi 2008-07-29 19:27:21 UTC
Looks like you are trying to install a package that was created by a more recent
version of rpm that does support Lzma compression while your own rpm version
doesn't. Can you please add a link to the package you are trying to install and
state what distribution you are using.

Comment 3 Florian Festi 2008-07-30 15:23:02 UTC
Fedora does not support rpm packages with Lzma compresion yet. Rpm upstream
already has Lzma support but it is not yet released and therefore may not get
into Fedora 9. As a work around you can try to rebuild the source package on
your system.

I am closing this as it is more or less a missing feature and installing random
packages from other distributions is neither supported nor encouraged.
Nevertheless this problem is already targeted by upstream and expected to go
away in the future (releases of the involved distributions).


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