Bug 104170 - up2date fails to start after upgrading itself from RHN
up2date fails to start after upgrading itself from RHN
Status: CLOSED RAWHIDE
Product: Red Hat Linux Beta
Classification: Retired
Component: up2date (Show other bugs)
beta1
All Linux
medium Severity medium
: ---
: ---
Assigned To: Adrian Likins
Fanny Augustin
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-09-10 14:14 EDT by Michael K. Johnson
Modified: 2007-04-18 12:57 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-09-16 19:06:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Michael K. Johnson 2003-09-10 14:14:06 EDT
Description of problem:
I ran with up2date --nosig from a recent version of up2date
it told me there was a new version in the channel and offered to just update
that version of up2date, and I said yes
when it tried to restart up2date, I got the help message
$ up2date --nosig
New Up2date available
Restarting up2date
$ Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
                                                                                
No interactive mode available
Please specify either -l, -u, --nox, or package names as command line
arguments.usage: up2date [OPTIONS] [<packages>]
(blah blah blah)
...
yes, I am going through userhelper


Version-Release number of selected component (if applicable):
updating from up2date-3.9.24-1 -> up2date-3.9.25-2

How reproducible: reliably


Steps to Reproduce:
1. install up2date-3.9.24-1
2. run up2date --nosig as a normal user (--nosig may not be required)
3. accept updating to new version of up2date from RHN
4. profit!
Comment 1 Adrian Likins 2003-09-10 16:00:10 EDT
fixed in cvs, should land in 3.1.26 or so
Comment 2 Michael Young 2003-09-10 18:52:45 EDT
Presumably ^3.1.26^3.9.26^. Also this bug is a duplicate of Bug 103185.
Comment 3 Michael K. Johnson 2003-09-11 10:39:10 EDT
Happened again this morning up2dateing (again, with --nosig) to up2date-3.9.26-2
Comment 4 Chris Ricker 2003-09-11 13:49:04 EDT
<aol>Me too, though I didn't use --nosig</aol>
Comment 5 Adrian Likins 2003-09-11 17:03:39 EDT
up2dating to 3.9.26 will still break (bug is in <= 3.9.25).
Should go away updating 3.9.26 to anything newer. 
Comment 6 Chris Ricker 2003-09-16 19:06:31 EDT
This appears fixed -- worked for me going to up2date-3.9.28-2


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