Error: Cannot retrieve repository metadata (repomd.xml) for repository: virtualmin-bleed

9 posts / 0 new
Topic locked
Last post
#1 Fri, 09/07/2012 - 01:42
decay

Error: Cannot retrieve repository metadata (repomd.xml) for repository: virtualmin-bleed

Not sure if this is virtualmin related, would be awesome if someone can help me with it though :)

Keep in mind that im a linux noob, so you might need to give me command to execute if you want me to post anything back :P

So i have a Centos VPS, and i tried to install java, and get:

[root@server1 ~]# yum install java
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: yum.singlehop.com
* extras: mirror.sanctuaryhost.com
* updates: mirror.steadfast.net
http://software.virtualmin.com/bleed/rhel/6/x86_64/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404"
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: virtualmin-bleed. Please verify its path and try again

and yum update:

[root@server1 ~]# yum update
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: yum.singlehop.com
* extras: mirror.sanctuaryhost.com
* updates: mirror.steadfast.net
http://software.virtualmin.com/bleed/rhel/6/x86_64/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404"
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: virtualmin-bleed. Please verify its path and try again

did yum clean all few times and retried too, but no luck, same issue.

[root@server1 ~]# yum clean all
Loaded plugins: fastestmirror
Cleaning repos: base extras updates virtualmin virtualmin-bleed
              : virtualmin-universal vz-base vz-updates
Cleaning up Everything
Cleaning up list of fastest mirrors
Fri, 09/07/2012 - 08:58
andreychek

Hmm, well, it does appear that the URL it's using for repo metadata doesn't exist.

If you look in /etc/yum.repos.d, do you see a file there for the Virtualmin bleed repo? If so, can you paste in it's contents?

Thanks!

-Eric

Fri, 09/07/2012 - 15:28 (Reply to #2)
decay
[virtualmin-bleed]name=Red Hat Enterprise $releasever - $basearch - Virtualmin Bleeding Edge
baseurl=http://software.virtualmin.com/bleed/rhel/$releasever/$basearch/
enabled=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-virtualmin
gpgcheck=1
Fri, 09/07/2012 - 08:59
andreychek

Oh, actually, I see what the issue is... the Virtualmin Bleed repo is, at this point, designed for CentOS 5.

CentOS 6 has newer software available than what's currently in the Bleed repo.

Which isn't to say that it won't at some point have software in it for CentOS 6, but with that being such a new distro, there hasn't currently been a need to provide that.

-Eric

Fri, 09/07/2012 - 15:30 (Reply to #4)
decay

Yeah I think I'm using centos 6. I see.

I'm not entirely sure what that means, but is there anything I can do to fix it? :(

Fri, 09/07/2012 - 17:58 (Reply to #5)
andreychek

Well, I guess I'm saying there's no reason to use the bleed repository on CentOS 6... there's no packages in it available to your distro. Your distro has newer packages available within it than are in the bleed repo.

My recommendation would simply be to disable the bleed repository.

-Eric

Fri, 09/07/2012 - 19:10 (Reply to #6)
decay

Oh i see. That makes sense.

emm, small question... emm how would i go about doing that? :S

Fri, 09/07/2012 - 22:06
andreychek

Well, one way would be to edit the .repo file for the bleed repo... and set "enabled=0".

You could also just delete the .repo file, or rename it so that it doesn't end with .repo... for example, you could rename it so that the filename ends with .old or .disabled.

-Eric

Sat, 09/08/2012 - 09:18 (Reply to #8)
decay

yey, it worked!

Thanks Eric. :)

Topic locked