PDA

View Full Version : My issues with yum/Fedora update/repos



m_raguraman
9th August 2008, 05:24 AM
Hi,
I am really having a rough time with the yum/update issues in FC9. When I try using the GUI to add software, I get the following error:

Cannot retrieve repository metadata (repomd.xml) for repository: fedora. Please verify its path and try again

When I try to use yum to update, I get the following error:

yum install xemacs
Loaded plugins: refresh-packagekit
http://download.fedoraproject.org/pub/fedora/linux/releases/9.90.1/Everything/i386/os/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: fedora. Please verify its path and try again
You have new mail in /var/spool/mail/root

Why is that my FC9 is not able to see the update server or the repos for adding new software ? I tried yum cleanup and all those command for db in google but still not able to resolve it.

I would greatly appreciate if somebody who understands the issues can help me out.

Thanks,
Ragu

marcrblevins
9th August 2008, 08:22 AM
Check yum every hour.

First one you want to load would be:


su -
yum install yum-fastestmirror

m_raguraman
9th August 2008, 02:30 PM
Still having the same problem after trying this out:

yum install yum-fastestmirror
Loaded plugins: refresh-packagekit
Could not retrieve mirrorlist http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-9.90.1&arch=i386 error was
[Errno 4] IOError: <urlopen error (-2, 'Name or service not known')>
http://download.fedoraproject.org/pub/fedora/linux/releases/9.90.1/Everything/i386/os/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: fedora. Please verify its path and try again

marko
9th August 2008, 05:57 PM
No, load doesn't cause his problems, his repository links point to repo directories that don't exist


http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-9.90.1&arch=i386


that should be this:


http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-$releasever&arch=$basearch

(assuming the releasever resolves to "9" on your installation which it should
unless you're really running some development version of Fedora 10 )
Were you modifying your Fedora 9 to experiment with Fedora 10 development for a while and now want to switch back?

Either edit your /etc/yum.repos.dir/* files to get those "9.90.1" out and replace them with "$releasever" or you might want to just get a fresh "fedora-release" rpm file for Fedora 9 and do:

rpm -i --force fedora-release.rpm

by getting it by ftp (avoiding yum since it's busted) at:


http://download.fedoraproject.org/pub/fedora/linux/releases/9/Everything/i386/os/Packages/fedora-release-9-2.noarch.rpm

and use that with rpm as shown to replace the fedora-release package files, some of those are the /etc/yum.repos.d files so you'll get a correct set

m_raguraman
9th August 2008, 08:22 PM
Hi Marko & marcrblevins,
Yes you are perfectly right. I wanted to try some devel stuff. But all I did was turn on the repos in GUI and after that I never got time to try those devel s/w. Now even if I turn them off, I am running into trouble. I followed your instructions, but still the same result. I cleared /var/cache/yum and no improvement. Will it work if I try to obtain the *.repo from another F9 user and delete everything in my /etc/yum.repo.d dir use those repos.

Thanks,
Ragu

yum install xemacs
Loaded plugins: refresh-packagekit
fedora | 83 B 00:00
http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-9.90.1&arch=i386/repodata/repomd.xml: [Errno -1] Error importing repomd.xml for fedora: Damaged repomd.xml file
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: fedora. Please verify its path and try again
[root@malar yum.repos.d]# yum install xemacs
Loaded plugins: refresh-packagekit
Could not retrieve mirrorlist http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-9.90.1&arch=i386 error was
[Errno 4] IOError: <urlopen error (-2, 'Name or service not known')>
fedora | 83 B 00:00
http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-9.90.1&arch=i386/repodata/repomd.xml: [Errno -1] Error importing repomd.xml for fedora: Damaged repomd.xml file
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: fedora. Please verify its path and try again

marko
9th August 2008, 08:39 PM
Why don't you just edit them and remove the number and replace it
with $releasever, save those changes and
run:

yum repolist all

this will show if the releasever value is '9' as it should be because for example the
"fedora" statement should look something like:


fedora Fedora 9 - i386 enabled: 12,444


What GUI, it is yumex or package kit?

Orioner
9th August 2008, 08:54 PM
Was running Fedora 9 and decided to dl 10 and installed it. But it wiped out Fed 9 from loading sequence and I can only boot Fed 10 now and it's giving me lots of pain. Repos are out of course and I can't boot into my old Fed 9 as it doesn't appear in the load sequence. Formerly I had the most recent Fed and the prior one to choose, now only Fed 10 and can't update!! Beware installing the Fed 10 release!!!

marko
9th August 2008, 08:59 PM
Was running Fedora 9 and decided to dl 10 and installed it. But it wiped out Fed 9 from loading sequence and I can only boot Fed 10 now and it's giving me lots of pain. Repos are out of course and I can't boot into my old Fed 9 as it doesn't appear in the load sequence. Formerly I had the most recent Fed and the prior one to choose, now only Fed 10 and can't update!! Beware installing the Fed 10 release!!!


So boot F10, fix the grub.conf file to put your Fedora 9 entry back in and set the default flag in grub.conf to point to the Fedora 9 so it's the default at boot time.

Fedora 10 is an alpha now, it's not a release

Orioner
9th August 2008, 09:09 PM
Thanks for the almost instant reply!! I'll do it and thanks again. Installing the release was a mistake.

marcrblevins
9th August 2008, 09:57 PM
He is using that lousy Packagekit thingy. Others prefers Yumex and othes old fashion yum.



yum install xemacs
Loaded plugins: refresh-packagekit
fedora | 83 B 00:00
http://mirrors.fedoraproject.org/mi...ata/repomd.xml: [Errno -1] Error importing repomd.xml for fedora: Damaged repomd.xml file
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: fedora. Please verify its path and try again
[root@malar yum.repos.d]# yum install xemacs
Loaded plugins: refresh-packagekit
Could not retrieve mirrorlist http://mirrors.fedoraproject.org/mi....90.1&arch=i386 error was
[Errno 4] IOError: <urlopen error (-2, 'Name or service not known')>
fedora | 83 B 00:00
http://mirrors.fedoraproject.org/mi...ata/repomd.xml: [Errno -1] Error importing repomd.xml for fedora: Damaged repomd.xml file
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: fedora. Please verify its path and try again

Orioner
9th August 2008, 11:22 PM
Marco, I need the F9 title in full to change grub. I've looked around but can't find what I need, the kernel description.

Orioner
9th August 2008, 11:40 PM
Maybe someone could post their grub.conf with Fed9 so I can see what details I need to input? Tnx

Mariano Suárez-
9th August 2008, 11:56 PM
He is using that lousy Packagekit thingy. Others prefers Yumex and othes old fashion yum.


The problem is quite unrelated to what program he is using.
Any program that uses his repository lists will result
in the same problem.

Of course, why would that stop anyone from bashing $HATED_APP_DU_JOUR?

Orioner
10th August 2008, 12:02 AM
Sorry, that's for an i386

marko
10th August 2008, 01:10 AM
This is mine, make the proper corrections so that the i386 suffix is used in the right places:

=======================
#boot=/dev/sda
default=0
timeout=15
splashimage=(hd0,0)/grub/splash.xpm.gz
#hiddenmenu
title Fedora (2.6.25.14-108.fc9.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.25.14-108.fc9.x86_64 ro root=UUID=d5ff60d9-9abc-404c-bb08-86cc0ebff427
initrd /initrd-2.6.25.14-108.fc9.x86_64.img
==============================

So try to use
ls /boot/vm*

to see the F9 kernel name in /boot where Fedora 9 is so you can replace the Title name and the kernel filename (orange), and then recover the UUID string with the blkid tool so you can replace mine (red) with the right one for yours.

blkid /dev/sda2

where the argument to blkid is the partition name where "/" is ,
that is my / is in /dev/sda2, yours might be elsewhere so use whatever
yours is and use that to replace my UUID (red)

Orioner
10th August 2008, 04:31 AM
[root@localhost ~]# blkid /dev/sdb
[root@localhost ~]# blkid /dev/sdb1
/dev/sdb1: LABEL="/boot1" UUID="ff2e7d24-99b6-48a3-98a6-39e18c96c715" SEC_TYPE="ext2" TYPE="ext3"
[root@localhost ~]# blkid /dev/sdb2
/dev/sdb2: UUID="VdRW3v-3Xax-mRfV-mBDb-VHhR-MdXT-3WzR5n" TYPE="lvm2pv"
[root@localhost ~]# ls /boot/vm*
/boot/vmlinuz-2.6.27-0.166.rc0.git8.fc10.i686

Looks like Fed 9 has disappeared altogether as above. I use a dual boot system with linux on one hard drive and usually when upgrading, the earlier kernel and its successor or Windows XP on different hard drive can be booted with Grub, but installing Fed 10 has removed Fed 9 altogether, it seems. It doesn't appear in the boot sequence or in Grub.conf. But thanks anyway.

w5set
10th August 2008, 05:19 AM
Actually if you enabled the devel (F10) repos and installed much of anything or did an update...you are at a F10 (mostly) install that wrote over/deleted the F9 stuff.
F9 isn't there to boot into.
Even if the last F9 kernel was there still, some of the new F10 stuff would probably make a flakey running install.

If you want to return to F9...it's reinstall time (at least for a "clean" running version without many problems).