EPEL Something wrong with el5 ppc builders?

[Susi Lehtola]

Hi,

my builds consistently fail on el5 ppc.

DEBUG util.py:264:  Error Downloading Packages:
DEBUG util.py:264:    tzdata-2013c-1.el5.ppc: failed to retrieve
tzdata-2013c-1.el5.ppc.rpm from build DEBUG util.py:264:  error was
[Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not
Found"

Is this a known issue?

[Trond Hasle Amundsen]

Susi Lehtola  writes:
> my builds consistently fail on el5 ppc.
>
> DEBUG util.py:264:  Error Downloading Packages:
> DEBUG util.py:264:    tzdata-2013c-1.el5.ppc: failed to retrieve
> tzdata-2013c-1.el5.ppc.rpm from build DEBUG util.py:264:  error was
> [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not
> Found"

Typically this happens when the internal repo in Koji contains an older
version of the package, than what's actually present in the external
repo. The tzdata package was updated recently. Glibc requires tzdata, so
all builds will fail. Somebody probably just needs to do a 'koji
regen-repo' for the EPEL5 build tag.

Regards,

[Kevin Fenzi]

On Wed, 10 Jul 2013 16:14:44 +0200
Trond Hasle Amundsen  wrote:
> Susi Lehtola  writes:
> > my builds consistently fail on el5 ppc.
> >
> > DEBUG util.py:264:  Error Downloading Packages:
> > DEBUG util.py:264:    tzdata-2013c-1.el5.ppc: failed to retrieve
> > tzdata-2013c-1.el5.ppc.rpm from build DEBUG util.py:264:  error was
> > [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404
> > Not Found"
>
> Typically this happens when the internal repo in Koji contains an
> older version of the package, than what's actually present in the
> external repo. The tzdata package was updated recently. Glibc
> requires tzdata, so all builds will fail. Somebody probably just
> needs to do a 'koji regen-repo' for the EPEL5 build tag.

Or you just need to wait and retry after it automatically does the next
one. ;)

I see builds that worked not too long ago, so I think this is already
fixed?

kevin