Submitted by samsaffy on Sun, 06/13/2010 - 13:21
See error below. I have tried yum clean all, --skip-broken, package-cleanup --problems, package-cleanup --dupes, rpm -Va --nofiles --nodigest but constantly get the same errors. Please can somebody help?
Now updating webmin ..
Installing package(s) with command yum -y install webmin ..
Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package webmin.noarch 0:1.510-1 set to be updated
http://software.virtualmin.com/gpl/rhel/5/x86_64/repodata/filelists.xml.gz: [Errno -1] Metadata file does not match checksum
Trying other mirror.
Error: failure: repodata/filelists.xml.gz from virtualmin: [Errno 256] No more mirrors to try.
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest
.. install failed!
No packages were installed. Check the messages above for the cause of the error
Status:
Closed (fixed)
Comments
Submitted by samsaffy on Sun, 06/13/2010 - 13:31 Comment #1
The repo meta data was broken for about five minutes last night due to a bug in my syncing script. Just run "yum clean all", and it'll fetch new meta data.
Submitted by samsaffy on Sun, 06/13/2010 - 16:41 Comment #3
Hi Joe,
I have tried running a yum clean all already and the same error seems to appear. Is there anything else i can try other than a yum clean all. Do i need to restart server after this has been done or run any other commands before i try to update to latest package?
thanks, sam
No, you definitely don't need to reboot.
Try "yum clean all" again.
I just regenerated the metadata. Maybe something was wrong even after the changes last night. I've confirmed that it's working now for i386 CentOS 5. If you're on x86_64, and it still happens, there may still be an issue with that repo (but I think everything is fine for all yum repos, now).
Submitted by samsaffy on Sun, 06/13/2010 - 17:32 Comment #5
great thanks now working ok. Thanks for your help. much appreciated
Submitted by Issues on Sun, 06/27/2010 - 19:20 Comment #6
Automatically closed -- issue fixed for 2 weeks with no activity.