-----Original Message-----
From: fedora-test-list-bounces(a)redhat.com
[mailto:fedora-test-list-bounces@redhat.com] On Behalf Of
Fulko.Hew(a)sita.aero
Sent: Friday, April 30, 2004 8:22 AM
To: fedora-test-list(a)redhat.com
Subject: header/RPM mismatch
Yesterday I was complaining about missing RPMs and the fact
that the update icon, and up2date were out of sync., so today
I thought I'd look at it some more.
Today, my icon still says there are 2 RPMs to upgrade, but
up2date says that only one is available. But up2date hangs
while trying to resolve dependencies.
So I went back to using yum.
Yum told me that there are two other RPMs (gaim and
rpmdb-fedora) that needed updating, and that there were
problems with perl-XML-Twig that needs XML::Path, which is not found.
So again I told it to ignore perl-XML-Twig, and yum installed
gaim and rpmdb-fedora. But alas the icon and up2date are
still as confused as ever.
Looking at the alert notification tool I see that it says:
Package Version Installed Version Available
perl-Net-DNS perl-Net-DNS-0.31.3.2 perl-Net-DNS-0.45-2
perl-XML-Twig perl-XML-Twig-3.09-3 perl-XML-Twig-3.13-4
OK, I need perl-XML-Twig-3.13-4. So I manually look at the mirror
site:
http://mirrors.kernel.org/fedora/core/development/i386/Fedora/RPMS
and the only version of perl-XML-Twig it has is 3.09-3 and
the same goes for perl-Net-DNS (only the old version).
Now i look in the mirrors header directory, and they don't
have the new version either. But at some time, my system did
fetch that header and now it thinks that's what it needs.
Did someone release new versions of the headers, without the
RPMs, (that my machine sucked)... and then pulled back the
new headers, (causing my machine to get into a mode)?
1/ If so, why?
2/ And how do I get my machine to forget about the headers
that point to
non-existant RPMs?
--
fedora-test-list mailing list
fedora-test-list(a)redhat.com
To unsubscribe:
http://www.redhat.com/mailman/listinfo/fedora-test-list
I didn't see your post from yersterday, so sorry if this was stated before
but,
Is your up2date using the same repository as yum? Both tools can be pointed
at completely different repos. Up2date has its configuration file in
/etc/sysconfig/rhn/sources, and yum has its in /etc/yum.conf.
If they are not using the same repository, you will get results like you are
explaining. Also, updates that come out from
fedora.redhat.com arent picked
up by mirrors immediately. There is varying time periods before each mirror
will sync with the main repo.