Hi all, got a problem I can't seem to find an answer to.
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?
-Jon
---------------------------- Original Message ---------------------------- Subject: Build Error (Job 396): wesnoth-1_2_8-1_el5 on fedora-5-epel From: buildsys@fedoraproject.org Date: Thu, October 9, 2008 11:09 am To: limb@jcomserv.net --------------------------------------------------------------------------
Job failed on arch ppc
Build logs may be found at http://buildsys.fedoraproject.org/logs/fedora-5-epel/396-wesnoth-1.2.8-1.el5...
-------------------------------------------------
Executing command: ['bash', '--login', '-c', 'rpmbuild -bs --target ppc --nodeps builddir/build/SPECS/wesnoth.spec'] Building target platforms: ppc Building for target ppc Wrote: /builddir/build/SRPMS/wesnoth-1.2.8-1.el5.src.rpm Child returncode was: 0 LEAVE do -->
On Thu, 9 Oct 2008 11:19:37 -0500 (CDT) "Jon Ciesla" limb@jcomserv.net wrote:
Hi all, got a problem I can't seem to find an answer to.
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...
Paul.
On 10.10.2008 00:40, Paul Howarth wrote:
On Thu, 9 Oct 2008 11:19:37 -0500 (CDT) "Jon Ciesla" limb@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
Not sure, but if I'd get that ticket in my inbox I wouldn't do anything as it seems a bit confusing to me ;-)
In case it helps: It long ago was agreed on to lot split EPEL in client and server add-on repos for RHEL5, as that would complicate things for packagers and users a lot; there was the idea to have a yum-plugin that automatically hides those epel packages that require things that are only part of the other RHEL5 variant -- but that was never written.
On the buildsys we afaik always had the packages from both client and server. When did that break? From the number of reports (that increased over the past few days afaics) it seems not that long ago...
Cu knurd
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@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.
Again, from the begining, should have built it against CentOS.
-Mike
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@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
Forgot something:
On 12.10.2008 10:01, Thorsten Leemhuis wrote:
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@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,
but the ticket really looked confusing -- at least to eyes it wasn't obvious what the ticket asked for, hence I thought it was worth asking here.
Cu knurd
epel-devel@lists.fedoraproject.org