Re: [Errno 256] No more mirrors to try

On Tue, Apr 13, 2010 at 9:14 AM, Maria Alandes Pradillo
<[email protected]> wrote:
> Hi all,
>
>> I don't think you'll have any luck with asking SL for a yum upgrade,
>> CentOS also has chosen to stay with the same version of yum. According
>> to the createrepo web site (http://createrepo.baseurl.org/) the
>> version we have on our server is incompatible with yum < 3.2.23 (and I
>> do not know how well the old version works with newer clients). I'm
>> not sure if we can work around it yet, I'm still looking into it. As
>> our server is a shared box with other projects we do not control the
>> software on it.
>
> May I ask if you have more news on a possible fix? I would just like to know if we can expect a fix soon. People installing gLite in SL4 rely on jpackage and this is now a big showstopper for sys admins to automate installations. If a fix is eventually available, what is the time scale to see it deployed in the repo?
>
> One of the gLite users has opened a bug for this in https://www.jpackage.org/bugzilla/show_bug.cgi?id=353, should we monitor that bug to track its progress?
>
> Thanks a lot,
> Maria

I don't think this is yum: I think this is an RPM deficit. It's not
even possible to install SRPM's from recent Fedora or RHEL 6 on RHEL 5
or RHEL 4: you have to do 'rpm2cpio' to extract the files, and work
from there to get RHEL 4 or RHEL 5 compatible packages built.

This may actually mandate building the entire jpackage 6 repository
under RHEL 4 or RHEL 5 for compatibility. I'm not so concerned aobut
RHEL 4, it's wildly out of date and should not be a large concern for
ongoing package development: it's better to jump from 5 or 6 years old
to only 3 years old, and work in RHEL 5.

Unfortunately, building that many packages from scratch is a lot of
work, and prone to minor configurtion or dependency difficulties: I
don't recommend it unless you have a client willing to fund you for a
year, and that kind of money and resource is better spent upgrading
your client.