A DIFFERENT yum/up2date problem...

[Allan Metts]

Hi Alexander,

Thanks for the suggestion.  Unfortunately, rebuilding the rpm database 
doesn't solve the problem.  Yum still hits the "base", then the "Released 
Updates" repositories, and reports that there's nothing new.

Anything else I can try?

(BTW -- I wasn't aware that I was hijacking a thread.  Please email me 
off-list if I'm misunderstanding something).

A-----


At 01:48 PM 1/18/2004, you wrote:
>Am So, den 18.01.2004 schrieb Allan Metts um 19:19:
> >
> > I have a server that I've recently switched to a mirror for package
> > updates.  Both up2date and yum are reliably connecting to the package
> > repository -- yet no new packages are listed as available  (tried running
> > both "up2date -l" and "yum list updates").
> >
> > I KNOW this isn't true -- the whole reason I switched to the mirror 
> site is
> > because I couldn't successfully update from the redhat fedora site.  There
> > are about 30 new packages I haven't gotten yet.  I've tried several
> > different mirrors -- and oddly enough, the original redhat fedora site
> > gives me this same report now.
> >
> > I've tried the "yum clean" commands, and I've blown away everything in
> > /var/spool that looks relevant.  I'm obviously overlooking something.
> >
> > Please help!  I'm attaching yum.conf below.
> >
> > Thanks in advance,
> > Allan
>
>[ snipped yum.conf ]
>
>FIRST: Do not hijack foreign threads, please!
>
>Does your rpm package db run ok? Do you get a valid response to "rpm -qa
>| wc -l"? Maybe you face the rpm bug, which sometimes occur. You can fix
>it running as root:
>
>rm -f /var/lib/rpm/__db.00? && rpm --rebuilddb