Fedora 12 -- unable to access repositories

[maverick280857]

Hi,

I just did a clean install of Fedora 12 on a system running Fedora 11. I'm behind a proxy, and I followed the steps outlined at http://digitizor.com/2009/06/17/how-...in-fedora-11/u to fix the initial repository error. This is what I get now:

[root@farpoint vivek]# yum update yum
Loaded plugins: presto, refresh-packagekit
fedora                                                   | 4.2 kB     00:00     
fedora/primary_db                                        |  12 MB     01:55     
rpmfusion-free                                           | 3.8 kB     00:00     
rpmfusion-free/primary_db                                | 344 kB     00:03     
rpmfusion-free-updates                                   | 3.3 kB     00:00     
rpmfusion-free-updates/primary_db                        | 176 kB     00:01     
rpmfusion-nonfree                                        | 3.3 kB     00:00     
rpmfusion-nonfree/primary_db                             |  91 kB     00:01     
rpmfusion-nonfree-updates                                | 3.3 kB     00:00     
rpmfusion-nonfree-updates/primary_db                     |  43 kB     00:01     
http://download.fedoraproject.org/pub/fedora/linux/updates/12/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 302 : http://download.fedoraproject.org/pub/fedora/linux/updates/12/x86_64/repodata/repomd.xml 
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: updates. Please verify its path and try again
[root@farpoint vivek]#

My /etc/hosts.conf looks like this

[root@farpoint vivek]# more /etc/hosts
# hostname farpoint added to /etc/hosts by anaconda
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4 farpoint
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6 farpoint
80.239.156.215 mirrors.fedoraproject.org
213.129.242.84 mirrors.rpmfusion.org
[root@farpoint vivek]#

Also,

[root@farpoint ~]# yum clean all
Loaded plugins: presto, refresh-packagekit
Cleaning up Everything
r[root@farpoint ~]# rm -f /var/lib/rpm/__db*
[root@farpoint ~]# rpm --rebuilddb

did not help at all.

I'd appreciate suggestions and advice to fix this problem.

Thanks in advance,
Vivek

[glennzo]

The link you provided doesn't appear to send me to the correct page. Anyhow, have you configured yum to work behind a proxy?

Have you made any changes to the .repo files?

[maverick280857]

Originally Posted by glennzo

The link you provided doesn't appear to send me to the correct page. Anyhow, have you configured yum to work behind a proxy?

Have you made any changes to the .repo files?

Sorry, here's the link: http://digitizor.com/2009/06/17/how-...-in-fedora-11/.

Yes, I configured the system proxy. And I uncommented baseurl and commented mirrors in the .repo files.

[glennzo]

I would change the repository back to the way it was. Do that and see if it makes any difference.

[maverick280857]

Restored .repo files...this is what happens:

[root@farpoint ~]# yum clean all
Loaded plugins: presto, refresh-packagekit
Cleaning up Everything
[root@farpoint ~]# yum update
Loaded plugins: presto, refresh-packagekit
Error: Cannot retrieve repository metadata (repomd.xml) for repository: fedora. Please verify its path and try again
[root@farpoint ~]#

[glennzo]

Originally Posted by maverick280857

Yes, I configured the system proxy.

But did you configure yum proxy?

[maverick280857]

Originally Posted by glennzo

But did you configure yum proxy?

How do I do that?

[glennzo]

Try this thread, post #10, http://forums.fedoraforum.org/showthread.php?t=238619

[maverick280857]

I still get the same error. I did yum clean all after editing yum.conf.

Is there anything else that has to be done with Fedora 12 too, because I never had to change the yum.conf file in Fedora 11.

[maverick280857]

I still haven't been able to resolve this. Any ideas?

EDIT: February 16, 2010....still no success. I would really appreciate if someone could help me out here. Fedora 11 seemed to work just fine.

EDIT: February 17, 2010...works all by itself now. Thanks!