Op zondag 26-08-2007 om 16:19 uur [tijdzone +0200], schreef Michael
Schwendt:
On Sun, 26 Aug 2007 15:30:13 +0200, Mark wrote:
> The update progress seems to have a few issues now:
>
> Error: Unresolveable requirement libexpat.so.0 for elinks
> Error: Unresolveable requirement libexpat.so.0 for gdb
> Error: Unresolveable requirement libexpat.so.0 for dbus
> Error: Unresolveable requirement libexpat.so.0 for exempi
> Error: Unresolveable requirement libexpat.so.0 for PolicyKit
> Error: Unresolveable requirement libexpat.so.0 for dbus-glib
> Error: Unresolveable requirement libexpat.so.0 for libtunepimp
> Error: Unresolveable requirement libexpat.so.0 for hal
> Error: Unresolveable requirement libexpat.so.0 for python
> Error: Unresolveable requirement libexpat.so.0 for mesa-libGL
> Error: Unresolveable requirement libexpat.so.0 for avahi
>
> resulting in not updating at all.
Yes, that's why I wondered, too. "yum install compat-expat1" does see
the compat-expat1 package, so I did a "yum -y update yum ; yum -y
update" and now it works.
[...]
---> Package compat-expat1.i386 0:1.95.8-3 set to be updated
[...]
Yeah, there still is a bug in yum. About 2 weeks ago I also stumbled
on this bug (but then with the rarian package) and Jesse Keating told
me a fix for it was already applied in yum's cvs. Unfortunately, no
new yum package has been pushed into rawhide yet containing the fix.