preupgrade is aborting

[Kevin J. Cummings]

The time has come for me to upgrade my F10 server to something more
recent.  Right now, I don't care if its to F11 or F12.  Neither is
working for me.

OK, so, I invoke "preupgrade" to do the work.

After some initial chugging, it dies with the message:

> requested datatype primary not available

This is strange.  I *just* finished preupgrading my F12 test system to
F13 Beta.  That went fine (compared to this, OK, I had to find a valid
install.img file and type the new URL in by hand, but that's minor
compared to this problem).

Seems I can't even get started.

Things I've tried:

1)  I edited my /etc/yum.repos.d/fedora*.repo files so that the baseurls
point to fedoraproject.org instead of redhat.com

	no difference

2)  yum clean all

	no difference

3)  (cd /var/cache; mv yum yum.f10)

	no difference

4)  preupgrade --clean

	no difference

The GUI error box seems to indicate that "This could be caused by a
missing network connection or a bad mirror."

Has anyone else seen this?  I'd like to be able to upgrade my server....

The error message gives *me* no indication of *which* repo it is having
problems with.  Is it the last one listed in the xterm I invoked it
from?  Or maybe the "next" one (which I can't tell because it hasn't
printed anything yet)?

If I click on the RETRY button, I get a different error:

> Repository preupgrade-main is listed more than once in the configuration

Any ideas on how to work around this?

-- 
Kevin J. Cummings
kjchome at rcn.com
cummings at kjchome.homeip.net
cummings at kjc386.framingham.ma.us
Registered Linux User #1232 (http://counter.li.org)