how do i recover from an up2date failure?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Up2date screwed up on my RH ES 3.0 system, and I'd
like to know how to get out of this gracefully.

I usually update the packages with -nox soon after
advisories come in, but I got an error last night, so
I tried the gui. I got through the installing and
removal of old packages, according to the log, and
then began 'updating transaction list'

At that point, the python scripts broke, specifically
rpcServer.py -- I've seen this in Bugzilla -- line
104, IndexError -- and the up2date process itself is
in some kind of deadlock now, and has been for an hour
and a half. I'll leave it for now just in case though
I have no evidence that anything is being retried.

So what do I need to do now to keep my rpm db correct?
I don't know up2date well, but old logs show it still
needs to add the packages to the profile, and then
remove the .hdr and .rpm files.

Thanks,




__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

[Index of Archives]     [CentOS]     [Kernel Development]     [PAM]     [Fedora Users]     [Red Hat Development]     [Big List of Linux Books]     [Linux Admin]     [Gimp]     [Asterisk PBX]     [Yosemite News]     [Red Hat Crash Utility]


  Powered by Linux