This may be trivially closable, but if I have the diagnosis right it may
(regrettably) be a reason to delay FC6 release. Or possibly I'm just not on the
appropriate mailing lists to have gotten the notice about this.

On my machine, *many* packages are not listed by yum list, and yum-3.0-3 was not
been pulled by the update process (I noticed this because attempts to update
fedora-kmod to 3.0-3 using the previous version of yum failed because the older
version of yum was unable to locate yum-3.0-3 in the repository). Example: try
"yum list|grep tetex" and you will see nothing (this is with fc6test3, yum
preceding 3.0-3. Sorry -- didn't think to jot down the yum version before
upgrading it by hand).

The faulty version of yum also appears to infinite loop when it is pointed
directly at the development repository, and also on some (but curiously not all)
mirrors. It seems possible that some of the mirrors (e.g. ibiblio) are not updating.

After hand-updating YUM to the version currently in the development/ tree (which
is 3.0-3), using yum update suddenly lists a vast number of packages to be updated.

So: the proximate bug appears to be fixed in yum-3.0-3. Hopefully, this is just
something where I didn't see the email, and everybody else knows that they
should hand update, and all is well. My concern is that if many people running
FC6test3 are running the faulty version of yum, then it is likely that many bug
fixes are not propagating and therefore may not be getting tested. This is why I
rated this "urgent".

Best guess on how to reproduce (which I have not tried):

Do a clean install of FC6test3 and run yum update. Check if yum >= 3.0-3 ends up
on your machine.

Note that my original install on this particular machine was from the 5.92 ISOs,
*not* from the ISOs in the development/ tree.  I have no way to know if the
issue is resolved in the later ISO images.