Yum Update error message

creative525 · #1 16th December 2007, 07:18 AM

I was trying to finish my install and I need to update, but everytime I run Yum Upate, I get this error message: Could not retrieve mirror list. Cannot retrieve repository metadata (repomd.xml) for repository: fedora. Please verify its path and try again.

Any help would be appreciated.

creative525 · #2 16th December 2007, 07:21 AM

By the way, I am using Fedora 8.

stunter · #3 17th December 2007, 07:11 AM

I had that problem and it was decided that I had accidentally upgraded to a development kernel (along with other stuff) and it wasn't going to work. So I did a fresh install of Fedora 8. I can't get a video driver to work so I was going to install kmod-nvidia. I tried this:

yum install kmod-nvidia

It wants to install 5 packages including an update to the kernel. I say go ahead and get this error message:

[Errno9] Requested Range Not Satisfiable

What does that mean?

Seve · #4 17th December 2007, 07:27 AM

Hello:
I don't know what the error means, sorry

Assuming that you have the livna repo installed.

Try updating using yum with
su -

yum --disablerepo=livna update

once everything is updated, reboot to the newest kernel then try
yum install kmod-nvidia

Seve

leigh123linux · #5 17th December 2007, 12:00 PM

Quote:

Originally Posted by creative525

I was trying to finish my install and I need to update, but everytime I run Yum Upate, I get this error message: Could not retrieve mirror list. Cannot retrieve repository metadata (repomd.xml) for repository: fedora. Please verify its path and try again.

Any help would be appreciated.

Post the output for this command

Code:

yum repolist

stunter · #6 17th December 2007, 03:05 PM

Seve,

OK, I'll try that tonight. This has been an interesting process. I'm learning a lot about what not to do when updating a system, that's certain.

edit

Doing a bit of googling, I found that I'm not the first to have this problem. It seems that it is probably cause by either 1) the repodata not yet being updated across mirrors or 2) Incomplete or garbled data in the cache. It was suggested that: yum clean all or yum clean packages may take care of it. It was also suggested that gpgcheck be disabled, though that doesn't seem like a good idea.

It was also suggested that just waiting it out will work. Hmmm...

creative525 · #7 18th December 2007, 04:27 AM

Thank you for the response. I will try your suggestions. Thank you