Bug 135022 - up2date no longer works with rpm-libs-4.3.2-10 installed
up2date no longer works with rpm-libs-4.3.2-10 installed
Status: CLOSED DUPLICATE of bug 135008
Product: Fedora
Classification: Fedora
Component: up2date (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Adrian Likins
Fanny Augustin
Depends On:
Blocks: FC3Blocker
  Show dependency treegraph
Reported: 2004-10-07 23:37 EDT by Jef Spaleta
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 14:06:13 EST
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 Jef Spaleta 2004-10-07 23:37:33 EDT
Description of problem:
seems there as been an internal change to rpm-libs as of todays
rawhide updates affecting both yum and up2date dependancy resolution.  

up2date gnumeric   
will get stuck in dep resolution with rpm-libs-4.3.2-10.

Yum Bug Reference: 

How reproducible:
When using up2date to install a package that needs an addition
dependancy to be installed as well, up2date will get stuck at the
dependancy resolution stage.

So up2date gnumeric fails for me because i do not have libgda or
libgnomedb installed

but if i do  up2date gnumeric libgda libgnomedb  that will succeed
because up2date doesnt have to look up additional packages to fullfil

Comment 1 Jeremy Katz 2004-10-12 14:48:15 EDT

*** This bug has been marked as a duplicate of 135008 ***
Comment 2 Red Hat Bugzilla 2006-02-21 14:06:13 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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