Virtualmin Package Updates looking at wrong repo

4 posts / 0 new
Last post
#1 Sat, 03/07/2009 - 09:25
mdtiberi

Virtualmin Package Updates looking at wrong repo

I saw a couple of packages I wanted to install which failed. It appears that it is looking at my ART repo rather than where it is supposed to. The error message is as follow:

Installing package(s) with command yum -y install wbm-virtualmin-google-analytics .. Loading "fastestmirror" plugin Loading mirror speeds from cached hostfile * virtualmin: software.virtualmin.com * virtualmin-universal: software.virtualmin.com * extras: mirrors.usc.edu * atomic: www2.atomicorp.com * base: yum.singlehop.com * asl-2.0: atomicorp.com * addons: mirror.fdcservers.net * updates: mirrors.usc.edu Excluding Packages in global exclude list Finished Setting up Install Process Parsing package install arguments Resolving Dependencies --> Running transaction check ---> Package wbm-virtualmin-google-analytics.noarch 2:2.1-1 set to be updated http://atomicorp.com/channels/asl-2.0/centos/5/x86_64/repodata/filelists... [Errno 12] Timeout: <urlopen error timed out> Trying other mirror. Error: failure: repodata/filelists.xml.gz from asl-2.0: [Errno 256] No more mirrors to try. .. install failed!

Nothing pops out at me in yum.repos.d, how do I correct this?

Thanks much.

Sat, 03/07/2009 - 10:41
Joe
Joe's picture

You have a bum repo configured and it's causing yum to fail. Remove the atomicorp.com repository, and this (specific) problem will go away.&lt;br&gt;&lt;br&gt;Post edited by: Joe, at: 2009/03/07 10:41

--

Check out the forum guidelines!

Sat, 03/07/2009 - 12:36
mdtiberi

Well that's not a very good solution. Atomic is one of the better repos out there, not about to disable it.

Rebuilt the filelists.xml.gz after yum clean all and installing from the command line. All is ok.

Sat, 03/07/2009 - 14:56 (Reply to #3)
Joe
Joe's picture

Well, you <i>did</i> ask. The repo <i>was</i> the cause of your trouble. What you do with the advice is up to you. ;-)

--

Check out the forum guidelines!

Topic locked