On Fri, 21 Feb 2003, Harry Putnam wrote:
> I've gotten myself into quite a pickle with todays attempt to update.
>
> up2date -u showed these:
>
> lynx-2.8.5-7.1.i386.rpm pam-devel-0.75-46.8.0.i386.rpm
> pam-0.75-46.8.0.i386.rpm shadow-utils-20000902-12.8.i386.rpm
>
> I downloaded them since I have up2date set to only download. Had a
> look, then ran up2date -u -i -k /var/spool/up2date which in my case
> would just rescan for needed packages then install them from where I
> downloaded them. Its how I've been doing it for a while now.
>
> The installation started ok, with lynx. Ran through the hash siqns
> lynx ################################## 100 percent
>
> And then just stopped, but never returned the prompt. I thought
> maybe a network drop might cause that, if up2date was still talking
> to rhn. But no, its something worse.
Stuff snipped.
> Wondered if anyone else had seen anything weird like this?
sounds like the classic RHL-8.0 rpm db corruption.
Suggest the following:
rm /var/lib/__db*
rpm --rebuilddb -vv
The -vv is only so you can see that it is working. It will scroll a bunch
of garbage across the screen periodically pausing while it does it's thing.
If you do not want to see the output just leave off the -vv.
Once done try your up2date again and see what happens. FWIW I have on more
than one occasion had to run the --rebuilddb more than once to get things
working again.
I sure hope this is fixed in RHL-TNV!! It is the biggest pita I have with the
8.0 machines.
HTH,
--
.............Tom "Nothing would please me more than being able to
[EMAIL PROTECTED] hire ten programmers and deluge the hobby market
with good software." -- Bill Gates 1976
We are still waiting ....
--
Psyche-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/psyche-list
