RHEL5 Client packages missing on the builders

[Thorsten Leemhuis]

On 11.10.2008 22:15, Mike McGrath wrote:
> On Sat, 11 Oct 2008, Thorsten Leemhuis wrote:
>> On 10.10.2008 00:40, Paul Howarth wrote:
>>> On Thu, 9 Oct 2008 11:19:37 -0500 (CDT)
>>> "Jon Ciesla" <limb at jcomserv.net> wrote:
>>>
>>>> Trying to build wesnoth for EPEL-5.  Had the branch created, copied
>>>> the bits from FC-6, and built.  The failure is below.  The crucial
>>>> part is in the job.log:
>>>>
>>>> ERROR: Bad build req: No Package Found for fribidi-devel. Exiting.
>>>>
>>>> Except that fribidi-devel exists in RHEL5.  The Fedora fribidi
>>>> maintainer is at a loss:
>>>>
>>>> https://bugzilla.redhat.com/show_bug.cgi?id=441847
>>>>
>>>> . . .as am I.
>>>>
>>>> I've been banging my head against this for while.  Any thoughts?
>>> fribidi is in RHEL5 Client but not RHEL5 Server, though I thought EPEL
>>> built against a combined set of packages from the two...
>> Is anybody with the proper access to the builders is working on fixing this
>> soon? Complains like this have shown up multiple times in the past few days.
>> Is this ticket meant for fixing this?
>> https://fedorahosted.org/fedora-infrastructure/ticket/881
> Yes its being worked on and no, people endlessly commenting on epel-devel
> instead of the ticket or the infrastructure list doesn't make it get done
> more quickly.

Sorry,

> Again, from the begining, should have built it against CentOS.

I totally disagree and I'm glad that we build against RHEL, as the 
target was RHEL, to which CentOS should be 100% compatible. Which it is, 
but sometimes with a delay of 24 to 48 hours (normal updates) or a few 
weeks (packages that are part of a quarterly update; new release). That 
is a quite significant factor for EPEL, because if we'd build with 
CentOS we couldn't serve the RHEL users properly, as they now and then 
will end up with broken deps.

Cu
knurd