Bug 70871 - up2date fails (resolving dependencies?)
Summary: up2date fails (resolving dependencies?)
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: up2date
Version: limbo
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Adrian Likins
QA Contact: Jay Turner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-08-06 11:27 UTC by Michael Young
Modified: 2015-01-07 23:58 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2002-08-09 02:36:36 UTC
Embargoed:


Attachments (Terms of Use)

Description Michael Young 2002-08-06 11:27:42 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (X11; U; SunOS 5.9 sun4u)

Description of problem:
up2date -l exits silently at the Testing RPM inter-dependencies stage
without outputing any hashes, or listing any packages. It doesn't upgrade a
named package either, probably failing at the same point. This is version
up2date-2.9.33 - it works again if I downgrade to up2date-2.9.30

How reproducible:
Always

Steps to Reproduce:
1. up2date -l

Comment 1 Lamar Owen 2002-08-06 23:52:34 UTC
 Additional information: when started from the command line, called simply as 
up2date with no options, then selecting to override configuration (to update 
the kernel), I get the same behavior.  However, I also see the following 
message: 
 ** (up2date:2446): WARNING **: could not find handler `onRegPackagePageBack' 
Segmentation Fault

Comment 2 Lamar Owen 2002-08-06 23:54:45 UTC
 Disregared my previous message -- it's a different bug. Sorry.

Comment 3 Lamar Owen 2002-08-06 23:59:36 UTC
 After thinking a minute, it is the same bug, just in the GUI instead of the 
batch mode.  The GUI gets to the same point -- resolving RPM interdependencies 
and then I get the Segmentation Fault (the WARNING is from much earlier in the 
program execution).

Comment 4 Michael Young 2002-08-09 09:33:34 UTC
It is working again in up2date-2.9.38 from rawhide (though only after upgrading
the rpm packages to 4.1-0.75). I am closing this bug.


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