>> I'm still seeing this message on a frequent basis from both
>> cron and yum update:
>>
>> Error: failure: repodata/repomd.xml from BlueQuartz: [Errno 256] No
>> more mirrors to try.
>
> Yes, I see this also.
> I wonder if the registrant of domain bluequartz.org
> yasuda<at>BAKKERS.ORG
> Would be willing to allow other mirrors or some fix!
I suggested this in the past and was shot down saying that it means anyone could
setup a mirror, put a rogue RPM on there and automatically install it on any
number of peoples machines.
While I agree with the theory there are a huge number of mirrors out there.
CentOS are always asking for public mirrors and will then add you to their
public mirrors file so I'm not sure how it is any less of a risk for them.
Programming wise it is very easy to do, people could add a single line to
crontab which will rsync the whole repository down. Users can submit their
mirrors to the mailing list and someone (ideally on bluequartz.org) then keeps
an updated text file for all the mirrors. A quick change to the yum config file
(which could be done via yum update) and we never need see this error again!
You could even skip the last bit and leave it open to the users. If they want
to use the mirror system they can make the change to the yum config file.
I actually already mirror the repo - http://mirrors.dogsbody.org/
Total Size : 3.2Gb
Total Files : 9645
Total Dirs : 139
Going forward we could even monitor the mirrors to check for ones that weren't
being updated, this wouldn't even need to be done by someone at bluequartz.org
as everyone would have access to the mirrors list and what was supposed to be
mirrored :-)
Just thinking is loud :-)
Dan