ppc.koji.fedoraproject.org back online

[Josh Boyer]

Hi All,

As the subject says, the buildsystem is back online.  It has been
upgraded to koji 1.6.0 and the two builder instances are running a new
enough kernel to build for F14 now.  They should also be able to build
from the Fedora git repos as well.

I would like to thank Stephen Smoogen and Dennis Gilmore for their
extraordinary help in getting the machines rebuilt and accessible.

Let the building begin.

josh

[Stephen John Smoogen]

On Tue, Dec 21, 2010 at 11:56, Josh Boyer <jwboyer(a)gmail.com&gt; wrote:
>  Hi All,
>
>  As the subject says, the buildsystem is back online.  It has been
>  upgraded to koji 1.6.0 and the two builder instances are running a new
>  enough kernel to build for F14 now.  They should also be able to build
>  from the Fedora git repos as well.
>
>  I would like to thank Stephen Smoogen and Dennis Gilmore for their
>  extraordinary help in getting the machines rebuilt and accessible. 
Thankyou but I need to thank Dennis also :). The only issue will be a
downtime in January sometime where we will move the ppc and s390 boxes
to a network and rack dedicated to them and testing. After that it
will be all ponies :)!

>  Let the building begin.
>
>  josh
>
>  _______________________________________________
>  Fedora-ppc mailing list
>  Fedora-ppc(a)lists.infradead.org
>  http://lists.infradead.org/mailman/listinfo/fedora-ppc
>  


-- 
Stephen J Smoogen.
"The core skill of innovators is error recovery, not failure avoidance."
Randy Nelson, President of Pixar University.
"Let us be kind, one to another, for most of us are fighting a hard
battle." -- Ian MacLaren

[Adrian Reber]

On Tue, Dec 21, 2010 at 01:56:13PM -0500, Josh Boyer wrote:
>  As the subject says, the buildsystem is back online.  It has been
>  upgraded to koji 1.6.0 and the two builder instances are running a new
>  enough kernel to build for F14 now.  They should also be able to build
>  from the Fedora git repos as well. 
Great. Thanks!

So, I am interested in doing builds. Is there a plan? First f14 then
f15? Or do we only look at f15? I do not see much sense looking at f14
and would much rather like to focus on f15.

Do I just take the rawhide packages and rebuild them? Is there some
documentation how to use koji for the ppc setup? I looked at

http://fedoraproject.org/wiki/Architectures/PowerPC

but I was not able to find something about how to configure koji to
connect to the ppc setup? I would really like to start rebuilding
packages but right now I do not know where to start.

		Adrian

[Karsten Hopp]

  Am 22.12.2010 08:21, schrieb Adrian Reber:
>  On Tue, Dec 21, 2010 at 01:56:13PM -0500, Josh Boyer wrote:
>  >  As the subject says, the buildsystem is back online.  It has been
>  >  upgraded to koji 1.6.0 and the two builder instances are running a new
>  >  enough kernel to build for F14 now.  They should also be able to build
>  >  from the Fedora git repos as well.
>
>  Great. Thanks!
>
>  So, I am interested in doing builds. Is there a plan? First f14 then
>  f15? Or do we only look at f15? I do not see much sense looking at f14
>  and would much rather like to focus on f15.
>
>  Do I just take the rawhide packages and rebuild them? Is there some
>  documentation how to use koji for the ppc setup? I looked at
>
>  http://fedoraproject.org/wiki/Architectures/PowerPC
>
>  but I was not able to find something about how to configure koji to
>  connect to the ppc setup? I would really like to start rebuilding
>  packages but right now I do not know where to start.
>
>  		Adrian
>
>  
I'd say that we should skip F-14 and concentrate on building rawhide.
F-14 has already been released and even F-15 might be already
finished when we finally got everything compiled and the installer
fixed. We should have a meeting at F-15 release time to decide if
we're only a few weeks lagging behind the primary archs or if we
need even more time and go for F-16.
I've played catch-up on Fedora-s390x and can tell you that it
isn't fun at all ;-(
Lets release when we're close to the primary archs and not
when we're lagging at least one release behind.


    Karsten

[Subrata Modak]

On Wed, 2010-12-22 at 10:59 +0100, Karsten Hopp wrote:
>  Am 22.12.2010 08:21, schrieb Adrian Reber:
>  > On Tue, Dec 21, 2010 at 01:56:13PM -0500, Josh Boyer wrote:
>  > >  As the subject says, the buildsystem is back online.  It has been
>  > >  upgraded to koji 1.6.0 and the two builder instances are running a new
>  > >  enough kernel to build for F14 now.  They should also be able to build
>  > >  from the Fedora git repos as well.
>  >
>  > Great. Thanks!
>  >
>  > So, I am interested in doing builds. Is there a plan? First f14 then
>  > f15? Or do we only look at f15? I do not see much sense looking at f14
>  > and would much rather like to focus on f15.
>  >
>  > Do I just take the rawhide packages and rebuild them? Is there some
>  > documentation how to use koji for the ppc setup? I looked at
>  >
>  > http://fedoraproject.org/wiki/Architectures/PowerPC
>  >
>  > but I was not able to find something about how to configure koji to
>  > connect to the ppc setup? I would really like to start rebuilding
>  > packages but right now I do not know where to start.
>  >
>  > 		Adrian
>  >
>  >
>  
>  I'd say that we should skip F-14 and concentrate on building rawhide.
>  F-14 has already been released and even F-15 might be already
>  finished when we finally got everything compiled and the installer
>  fixed. We should have a meeting at F-15 release time to decide if
>  we're only a few weeks lagging behind the primary archs or if we
>  need even more time and go for F-16.
>  I've played catch-up on Fedora-s390x and can tell you that it
>  isn't fun at all ;-(
>  Lets release when we're close to the primary archs and not
>  when we're lagging at least one release behind. 
I endorse that. Lets target F15 for PPC64 and S390X.

Regards--
Subrata

>  
>  
>      Karsten
>  
>  _______________________________________________
>  Fedora-ppc mailing list
>  Fedora-ppc(a)lists.infradead.org
>  http://lists.infradead.org/mailman/listinfo/fedora-ppc

[Karsten Hopp]

  Am 22.12.2010 12:05, schrieb Subrata Modak:
>  On Wed, 2010-12-22 at 10:59 +0100, Karsten Hopp wrote:
>  >  Am 22.12.2010 08:21, schrieb Adrian Reber:
>  >  >  On Tue, Dec 21, 2010 at 01:56:13PM -0500, Josh Boyer wrote:
>  >  >  >   As the subject says, the buildsystem is back online.  It has been
>  >  >  >   upgraded to koji 1.6.0 and the two builder instances are running a
> new
>  >  >  >   enough kernel to build for F14 now.  They should also be able to
> build
>  >  >  >   from the Fedora git repos as well.
>  >  >
>  >  >  Great. Thanks!
>  >  >
>  >  >  So, I am interested in doing builds. Is there a plan? First f14 then
>  >  >  f15? Or do we only look at f15? I do not see much sense looking at f14
>  >  >  and would much rather like to focus on f15.
>  >  >
>  >  >  Do I just take the rawhide packages and rebuild them? Is there some
>  >  >  documentation how to use koji for the ppc setup? I looked at
>  >  >
>  >  >  http://fedoraproject.org/wiki/Architectures/PowerPC
>  >  >
>  >  >  but I was not able to find something about how to configure koji to
>  >  >  connect to the ppc setup? I would really like to start rebuilding
>  >  >  packages but right now I do not know where to start.
>  >  >
>  >  >  		Adrian
>  >  >
>  >  >
>  >
>  >  I'd say that we should skip F-14 and concentrate on building rawhide.
>  >  F-14 has already been released and even F-15 might be already
>  >  finished when we finally got everything compiled and the installer
>  >  fixed. We should have a meeting at F-15 release time to decide if
>  >  we're only a few weeks lagging behind the primary archs or if we
>  >  need even more time and go for F-16.
>  >  I've played catch-up on Fedora-s390x and can tell you that it
>  >  isn't fun at all ;-(
>  >  Lets release when we're close to the primary archs and not
>  >  when we're lagging at least one release behind.
>
>  I endorse that. Lets target F15 for PPC64 and S390X.
>
>  Regards--
>  Subrata 
Well, F-14 s390x will be released once I've figured out how to sign
the packages with Fedora's signing server 'sigul'. All development is
already done, Dan is now rebuilding F-14 updates and Rawhide, afaik.

    Karsten

[Dan Horák]

Karsten Hopp píše v St 22. 12. 2010 v 12:14 +0100:
>  Am 22.12.2010 12:05, schrieb Subrata Modak:
>  > On Wed, 2010-12-22 at 10:59 +0100, Karsten Hopp wrote:
>  > >  Am 22.12.2010 08:21, schrieb Adrian Reber:
>  > >  >  On Tue, Dec 21, 2010 at 01:56:13PM -0500, Josh Boyer wrote:
>  > >  >  >   As the subject says, the buildsystem is back online.  It has
> been
>  > >  >  >   upgraded to koji 1.6.0 and the two builder instances are running
> a new
>  > >  >  >   enough kernel to build for F14 now.  They should also be able to
> build
>  > >  >  >   from the Fedora git repos as well.
>  > >  >
>  > >  >  Great. Thanks!
>  > >  >
>  > >  >  So, I am interested in doing builds. Is there a plan? First f14 then
>  > >  >  f15? Or do we only look at f15? I do not see much sense looking at f14
>  > >  >  and would much rather like to focus on f15.
>  > >  >
>  > >  >  Do I just take the rawhide packages and rebuild them? Is there some
>  > >  >  documentation how to use koji for the ppc setup? I looked at
>  > >  >
>  > >  >  http://fedoraproject.org/wiki/Architectures/PowerPC
>  > >  >
>  > >  >  but I was not able to find something about how to configure koji to
>  > >  >  connect to the ppc setup? I would really like to start rebuilding
>  > >  >  packages but right now I do not know where to start.
>  > >  >
>  > >  >  		Adrian
>  > >  >
>  > >  >
>  > >
>  > >  I'd say that we should skip F-14 and concentrate on building rawhide.
>  > >  F-14 has already been released and even F-15 might be already
>  > >  finished when we finally got everything compiled and the installer
>  > >  fixed. We should have a meeting at F-15 release time to decide if
>  > >  we're only a few weeks lagging behind the primary archs or if we
>  > >  need even more time and go for F-16.
>  > >  I've played catch-up on Fedora-s390x and can tell you that it
>  > >  isn't fun at all ;-(
>  > >  Lets release when we're close to the primary archs and not
>  > >  when we're lagging at least one release behind.
>  >
>  > I endorse that. Lets target F15 for PPC64 and S390X.
>  >
>  > Regards--
>  > Subrata
>  
>  Well, F-14 s390x will be released once I've figured out how to sign
>  the packages with Fedora's signing server 'sigul'. All development is
>  already done, Dan is now rebuilding F-14 updates and Rawhide, afaik. 
On s390x the F-14 updates are behind the primary Fedora for something
between few hours and few days (depends whether there is koji-shadow
running for rawhide or not) and Rawhide is getting closer every day,
today with only about 500 packages older than in primary. I consider
that as big success.


		Dan

[Dan Horák]

Karsten Hopp píše v St 22. 12. 2010 v 10:59 +0100:
>  Am 22.12.2010 08:21, schrieb Adrian Reber:
>  > On Tue, Dec 21, 2010 at 01:56:13PM -0500, Josh Boyer wrote:
>  > >  As the subject says, the buildsystem is back online.  It has been
>  > >  upgraded to koji 1.6.0 and the two builder instances are running a new
>  > >  enough kernel to build for F14 now.  They should also be able to build
>  > >  from the Fedora git repos as well.
>  >
>  > Great. Thanks!
>  >
>  > So, I am interested in doing builds. Is there a plan? First f14 then
>  > f15? Or do we only look at f15? I do not see much sense looking at f14
>  > and would much rather like to focus on f15.
>  >
>  > Do I just take the rawhide packages and rebuild them? Is there some
>  > documentation how to use koji for the ppc setup? I looked at
>  >
>  > http://fedoraproject.org/wiki/Architectures/PowerPC
>  >
>  > but I was not able to find something about how to configure koji to
>  > connect to the ppc setup? I would really like to start rebuilding
>  > packages but right now I do not know where to start.
>  >
>  > 		Adrian
>  >
>  >
>  
>  I'd say that we should skip F-14 and concentrate on building rawhide.
>  F-14 has already been released and even F-15 might be already
>  finished when we finally got everything compiled and the installer
>  fixed. We should have a meeting at F-15 release time to decide if
>  we're only a few weeks lagging behind the primary archs or if we
>  need even more time and go for F-16.
>  I've played catch-up on Fedora-s390x and can tell you that it
>  isn't fun at all ;-( 
/me agrees, it wasn't easy. Being only few days behind the primary koji
is optimal, especially for rawhide where things change very often.

Some rounds of the "build-previous" script and manual dependency fixing
coordinated between a group of people can prepare enough builds in a
reasonable time and then koji-shadow can be restarted. Other option is
to go directly with koji-shadow pointed to the dist-f15 tag in primary
koji. I have no idea what way would be more effective, but my guess
would be that using koji-shadow only will solve things like the soname
bumps automagically. A lot of manual work will be definitely needed in
both. Other important factor is the available builder and hub capacity.


		Dan

[Adrian Reber]

On Wed, Dec 22, 2010 at 10:59:49AM +0100, Karsten Hopp wrote:
>   Am 22.12.2010 08:21, schrieb Adrian Reber:
>  >On Tue, Dec 21, 2010 at 01:56:13PM -0500, Josh Boyer wrote:
>  >>  As the subject says, the buildsystem is back online.  It has been
>  >>  upgraded to koji 1.6.0 and the two builder instances are running a new
>  >>  enough kernel to build for F14 now.  They should also be able to build
>  >>  from the Fedora git repos as well.
>  >
>  >Great. Thanks!
>  >
>  >So, I am interested in doing builds. Is there a plan? First f14 then
>  >f15? Or do we only look at f15? I do not see much sense looking at f14
>  >and would much rather like to focus on f15.
>  >
>  >Do I just take the rawhide packages and rebuild them? Is there some
>  >documentation how to use koji for the ppc setup? I looked at
>  >
>  >http://fedoraproject.org/wiki/Architectures/PowerPC
>  >
>  >but I was not able to find something about how to configure koji to
>  >connect to the ppc setup? I would really like to start rebuilding
>  >packages but right now I do not know where to start.
>  >
>  
>  I'd say that we should skip F-14 and concentrate on building rawhide.
>  F-14 has already been released and even F-15 might be already
>  finished when we finally got everything compiled and the installer
>  fixed. We should have a meeting at F-15 release time to decide if
>  we're only a few weeks lagging behind the primary archs or if we
>  need even more time and go for F-16.
>  I've played catch-up on Fedora-s390x and can tell you that it
>  isn't fun at all ;-(
>  Lets release when we're close to the primary archs and not
>  when we're lagging at least one release behind. 
Good to hear from someone with secondary arch experience. As I am also
for skipping f14, I like what you say ;-). So how do I use the ppc koji?
I am ready to start using it.

		Adrian

[Josh Boyer]

On Wed, Dec 22, 2010 at 6:35 AM, Adrian Reber <adrian(a)lisas.de&gt; wrote:
>  On Wed, Dec 22, 2010 at 10:59:49AM +0100, Karsten Hopp wrote:
> >  Am 22.12.2010 08:21, schrieb Adrian Reber:
> > >On Tue, Dec 21, 2010 at 01:56:13PM -0500, Josh Boyer wrote:
> > >>  As the subject says, the buildsystem is back online.  It has been
> > >>  upgraded to koji 1.6.0 and the two builder instances are running a new
> > >>  enough kernel to build for F14 now.  They should also be able to build
> > >>  from the Fedora git repos as well.
> > >
> > >Great. Thanks!
> > >
> > >So, I am interested in doing builds. Is there a plan? First f14 then
> > >f15? Or do we only look at f15? I do not see much sense looking at f14
> > >and would much rather like to focus on f15.
> > >
> > >Do I just take the rawhide packages and rebuild them? Is there some
> > >documentation how to use koji for the ppc setup? I looked at
> > >
> > >http://fedoraproject.org/wiki/Architectures/PowerPC
> > >
> > >but I was not able to find something about how to configure koji to
> > >connect to the ppc setup? I would really like to start rebuilding
> > >packages but right now I do not know where to start.
> > >
> >
> > I'd say that we should skip F-14 and concentrate on building rawhide.
> > F-14 has already been released and even F-15 might be already
> > finished when we finally got everything compiled and the installer
> > fixed. We should have a meeting at F-15 release time to decide if
> > we're only a few weeks lagging behind the primary archs or if we
> > need even more time and go for F-16.
> > I've played catch-up on Fedora-s390x and can tell you that it
> > isn't fun at all ;-(
> > Lets release when we're close to the primary archs and not
> > when we're lagging at least one release behind.
>
>  Good to hear from someone with secondary arch experience. As I am also
>  for skipping f14, I like what you say ;-). So how do I use the ppc koji?
>  I am ready to start using it. 
There's two different ways.  The first is that someone needs to run
koji-shadow on it it so it builds the RPMs built in the primary koji.
The tags might need to be adjusted before that can happen.

The other way is just as a package maintainer.  It's really no
different than using the primary koji hub.  The only thing you need to
do is point your build/scratch-build at this hub instead.  You can
either create a separate koji config pointing to this hub, or just use
the -s option:

koji -s http://ppc.koji.fedoraproject.org/kojihub build <whatever>

It's setup to use your existing Fedora cert already.

josh

[Adrian Reber]

On Wed, Dec 22, 2010 at 06:51:09AM -0500, Josh Boyer wrote:
>  The other way is just as a package maintainer.  It's really no
>  different than using the primary koji hub.  The only thing you need to
>  do is point your build/scratch-build at this hub instead.  You can
>  either create a separate koji config pointing to this hub, or just use
>  the -s option:
>  
>  koji -s http://ppc.koji.fedoraproject.org/kojihub build <whatever>
>  
>  It's setup to use your existing Fedora cert already. 
I tried a scratch build with a SRPM and got an error:

 koji -s http://ppc.koji.fedoraproject.org/kojihub build --scratch dist-rawhide
/media/raidhome/adrian/fedora/binutils/binutils-2.20.51.0.12-2.fc15.src.rpm
Uploading srpm:
/media/raidhome/adrian/fedora/binutils/binutils-2.20.51.0.12-2.fc15.src.rpm
[====================================] 100% 00:01:20  15.87 MiB 201.19 KiB/sec
Created task: 114591
Task info: http://koji.fedoraproject.org/koji/taskinfo?taskID=114591
Watching tasks (this may be safely interrupted)...
114591 build (dist-rawhide, binutils-2.20.51.0.12-2.fc15.src.rpm): open (dooku)
114591 build (dist-rawhide, binutils-2.20.51.0.12-2.fc15.src.rpm): open (dooku) ->
FAILED: Fault: <Fault 1: 'Traceback (most recent call last):\n  File
"/usr/sbin/kojid", line 1437, in runTask\n    response = (handler.run(),)\n 
File "/usr/sbin/kojid", line 1513, in run\n    return
self.handler(*self.params,**self.opts)\n  File "/usr/sbin/kojid", line 1934, in
handler\n    h = self.readSRPMHeader(srpm)\n  File "/usr/sbin/kojid", line 2006,
in readSRPMHeader\n    fo = koji.openRemoteFile(relpath, **opts)\n  File
"/usr/lib/python2.6/site-packages/koji/__init__.py", line 1361, in
openRemoteFile\n    fo = open(fn)\nIOError: [Errno 2] No such file or directory:
\'/mnt/koji/work/cli-build/1293028721.705156.veLRzoZF/binutils-2.20.51.0.12-2.fc15.src.rpm\'\n'>
  0 free  0 open  0 done  1 failed

114591 build (dist-rawhide, binutils-2.20.51.0.12-2.fc15.src.rpm) failed

and

koji -s http://ppc.koji.fedoraproject.org/kojihub build --scratch dist-rawhide 
git://pkgs.fedoraproject.org/binutils?#531a74d49fbcb04b3bf2d012f5c82d6cab...

gives me

DEBUG util.py:267:  file:///mnt/koji/repos/dist-f14-build/24304/ppc/repodata/repomd.xml:
[Errno 14] Could not open/read
file:///mnt/koji/repos/dist-f14-build/24304/ppc/repodata/repomd.xml
DEBUG util.py:267:  Trying other mirror.
DEBUG util.py:267:  Error: Cannot retrieve repository metadata (repomd.xml) for
repository: build. Please verify its path and try again

		Adrian

[Josh Boyer]

On Wed, Dec 22, 2010 at 9:46 AM, Adrian Reber <adrian(a)lisas.de&gt; wrote:
>  On Wed, Dec 22, 2010 at 06:51:09AM -0500, Josh Boyer wrote:
> > The other way is just as a package maintainer.  It's really no
> > different than using the primary koji hub.  The only thing you need to
> > do is point your build/scratch-build at this hub instead.  You can
> > either create a separate koji config pointing to this hub, or just use
> > the -s option:
> >
> > koji -s http://ppc.koji.fedoraproject.org/kojihub build <whatever>
> >
> > It's setup to use your existing Fedora cert already.
>
>  I tried a scratch build with a SRPM and got an error:
>
>   koji -s http://ppc.koji.fedoraproject.org/kojihub build --scratch dist-rawhide
> /media/raidhome/adrian/fedora/binutils/binutils-2.20.51.0.12-2.fc15.src.rpm
>  Uploading srpm:
> /media/raidhome/adrian/fedora/binutils/binutils-2.20.51.0.12-2.fc15.src.rpm
>  [====================================] 100% 00:01:20  15.87 MiB 201.19 KiB/sec
>  Created task: 114591
>  Task info: http://koji.fedoraproject.org/koji/taskinfo?taskID=114591
>  Watching tasks (this may be safely interrupted)...
>  114591 build (dist-rawhide, binutils-2.20.51.0.12-2.fc15.src.rpm): open (dooku)
>  114591 build (dist-rawhide, binutils-2.20.51.0.12-2.fc15.src.rpm): open (dooku) ->
> FAILED: Fault: <Fault 1: 'Traceback (most recent call last):\n  File
> "/usr/sbin/kojid", line 1437, in runTask\n    response = (handler.run(),)\n
>  File "/usr/sbin/kojid", line 1513, in run\n    return
> self.handler(*self.params,**self.opts)\n  File "/usr/sbin/kojid", line 1934, in
> handler\n    h = self.readSRPMHeader(srpm)\n  File "/usr/sbin/kojid", line 2006,
> in readSRPMHeader\n    fo = koji.openRemoteFile(relpath, **opts)\n  File
> "/usr/lib/python2.6/site-packages/koji/__init__.py", line 1361, in
> openRemoteFile\n    fo = open(fn)\nIOError: [Errno 2] No such file or directory:
> \'/mnt/koji/work/cli-build/1293028721.705156.veLRzoZF/binutils-2.20.51.0.12-2.fc15.src.rpm\'\n'>
>   0 free  0 open  0 done  1 failed
>
>  114591 build (dist-rawhide, binutils-2.20.51.0.12-2.fc15.src.rpm) failed 
This was a misconfigured builder.  I fixed it and resubmitted this
task and it seems to be working:

http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114596

Sorry about the inconvenience!

josh

[Adrian Reber]

On Wed, Dec 22, 2010 at 10:08:25AM -0500, Josh Boyer wrote:
>  > 114591 build (dist-rawhide,
> binutils-2.20.51.0.12-2.fc15.src.rpm) failed
>  
>  This was a misconfigured builder.  I fixed it and resubmitted this
>  task and it seems to be working:
>  
>  http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114596
>  
>  Sorry about the inconvenience! 
No problem. Thanks for fixing it.

I found another error:

$ git clone -n git://pkgs.fedoraproject.org/binutils binutils
pkgs.fedoraproject.org[0: 209.132.181.4]: errno=Connection timed out
fatal: unable to connect a socket (Connection timed out)
Cloning into binutils...

from http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114600

		Adrian

[Josh Boyer]

On Wed, Dec 22, 2010 at 10:18 AM, Adrian Reber <adrian(a)lisas.de&gt; wrote:
>  On Wed, Dec 22, 2010 at 10:08:25AM -0500, Josh Boyer wrote:
> > > 114591 build (dist-rawhide, binutils-2.20.51.0.12-2.fc15.src.rpm) failed
> >
> > This was a misconfigured builder.  I fixed it and resubmitted this
> > task and it seems to be working:
> >
> > http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114596
> >
> > Sorry about the inconvenience!
>
>  No problem. Thanks for fixing it.
>
>  I found another error:
>
>  $ git clone -n git://pkgs.fedoraproject.org/binutils binutils
>  pkgs.fedoraproject.org[0: 209.132.181.4]: errno=Connection timed out
>  fatal: unable to connect a socket (Connection timed out)
>  Cloning into binutils...
>
>  from http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114600 
Hm.  Indeed.  The main hub can resolve and clone that, but the other
builder can't.  I suspect this is an issue with the PHX2 firewall
setup and not really much to do with koji.

Dennis, is there an additional step needed to get access to
pkgs.fedoraproject.org on the builders?  Maybe a /etc/hosts entry?

josh

[Dennis Gilmore]

On Wednesday, December 22, 2010 09:25:12 am Josh Boyer wrote:
>  On Wed, Dec 22, 2010 at 10:18 AM, Adrian Reber
> <adrian(a)lisas.de&gt; wrote:
>  > On Wed, Dec 22, 2010 at 10:08:25AM -0500, Josh Boyer wrote:
>  >> > 114591 build (dist-rawhide, binutils-2.20.51.0.12-2.fc15.src.rpm)
>  >> > failed
>  >> 
>  >> This was a misconfigured builder.  I fixed it and resubmitted this
>  >> task and it seems to be working:
>  >> 
>  >> http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114596
>  >> 
>  >> Sorry about the inconvenience!
>  > 
>  > No problem. Thanks for fixing it.
>  > 
>  > I found another error:
>  > 
>  > $ git clone -n git://pkgs.fedoraproject.org/binutils binutils
>  > pkgs.fedoraproject.org[0: 209.132.181.4]: errno=Connection timed out
>  > fatal: unable to connect a socket (Connection timed out)
>  > Cloning into binutils...
>  > 
>  > from http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114600
>  
>  Hm.  Indeed.  The main hub can resolve and clone that, but the other
>  builder can't.  I suspect this is an issue with the PHX2 firewall
>  setup and not really much to do with koji.
>  
>  Dennis, is there an additional step needed to get access to
>  pkgs.fedoraproject.org on the builders?  Maybe a /etc/hosts entry?
>  
>  josh 
add a hosts entry with the ip 10.5.125.44

Dennis

[Josh Boyer]

On Wed, Dec 22, 2010 at 2:47 PM, Dennis Gilmore <dennis(a)ausil.us&gt; wrote:
>  On Wednesday, December 22, 2010 09:25:12 am Josh Boyer wrote:
> > On Wed, Dec 22, 2010 at 10:18 AM, Adrian Reber <adrian(a)lisas.de&gt; wrote:
> > > On Wed, Dec 22, 2010 at 10:08:25AM -0500, Josh Boyer wrote:
> > >> > 114591 build (dist-rawhide, binutils-2.20.51.0.12-2.fc15.src.rpm)
> > >> > failed
> > >>
> > >> This was a misconfigured builder.  I fixed it and resubmitted this
> > >> task and it seems to be working:
> > >>
> > >> http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114596
> > >>
> > >> Sorry about the inconvenience!
> > >
> > > No problem. Thanks for fixing it.
> > >
> > > I found another error:
> > >
> > > $ git clone -n git://pkgs.fedoraproject.org/binutils binutils
> > > pkgs.fedoraproject.org[0: 209.132.181.4]: errno=Connection timed out
> > > fatal: unable to connect a socket (Connection timed out)
> > > Cloning into binutils...
> > >
> > > from http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114600
> >
> > Hm.  Indeed.  The main hub can resolve and clone that, but the other
> > builder can't.  I suspect this is an issue with the PHX2 firewall
> > setup and not really much to do with koji.
> >
> > Dennis, is there an additional step needed to get access to
> > pkgs.fedoraproject.org on the builders?  Maybe a /etc/hosts entry?
> >
> > josh
>  add a hosts entry with the ip 10.5.125.44 
OK added and I can do the clone from command line now.  Hopefully this
builder is set now.

josh

[Adrian Reber]

On Fri, Dec 24, 2010 at 07:26:57AM -0500, Josh Boyer wrote:
>  >> > $ git clone -n git://pkgs.fedoraproject.org/binutils
> binutils
>  >> > pkgs.fedoraproject.org[0: 209.132.181.4]: errno=Connection timed out
>  >> > fatal: unable to connect a socket (Connection timed out)
>  >> > Cloning into binutils...
>  >> >
>  >> > from http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114600
>  >>
>  >> Hm.  Indeed.  The main hub can resolve and clone that, but the other
>  >> builder can't.  I suspect this is an issue with the PHX2 firewall
>  >> setup and not really much to do with koji.
>  >>
>  >> Dennis, is there an additional step needed to get access to
>  >> pkgs.fedoraproject.org on the builders?  Maybe a /etc/hosts entry?
>  >>
>  >> josh
>  > add a hosts entry with the ip 10.5.125.44
>  
>  OK added and I can do the clone from command line now.  Hopefully this
>  builder is set now. 
Now the git part seems to work but there seems to be a problem getting
the sources. I am not really sure what it means but I suppose it cannot
download the tarball from the lookaside cache.

http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114607

I found nothing in the logs which looks like an error.

		Adrian

[Josh Boyer]

On Fri, Dec 24, 2010 at 7:53 AM, Adrian Reber <adrian(a)lisas.de&gt; wrote:
>  On Fri, Dec 24, 2010 at 07:26:57AM -0500, Josh Boyer wrote:
> > >> > $ git clone -n git://pkgs.fedoraproject.org/binutils binutils
> > >> > pkgs.fedoraproject.org[0: 209.132.181.4]: errno=Connection timed out
> > >> > fatal: unable to connect a socket (Connection timed out)
> > >> > Cloning into binutils...
> > >> >
> > >> > from http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114600
> > >>
> > >> Hm.  Indeed.  The main hub can resolve and clone that, but the other
> > >> builder can't.  I suspect this is an issue with the PHX2 firewall
> > >> setup and not really much to do with koji.
> > >>
> > >> Dennis, is there an additional step needed to get access to
> > >> pkgs.fedoraproject.org on the builders?  Maybe a /etc/hosts entry?
> > >>
> > >> josh
> > > add a hosts entry with the ip 10.5.125.44
> >
> > OK added and I can do the clone from command line now.  Hopefully this
> > builder is set now.
>
>  Now the git part seems to work but there seems to be a problem getting
>  the sources. I am not really sure what it means but I suppose it cannot
>  download the tarball from the lookaside cache.
>
>  http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114607
>
>  I found nothing in the logs which looks like an error. 
fedpkg wasn't installed on either box.  I forgot this when doing the
transition to git based SCM.  I've resubmitted the task.  We'll see
how it goes now.  Sigh..

http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114621

josh

[Dennis Gilmore]

On Wednesday, December 29, 2010 08:14:14 am Josh Boyer wrote:
>  On Fri, Dec 24, 2010 at 7:53 AM, Adrian Reber <adrian(a)lisas.de&gt;
> wrote:
>  > On Fri, Dec 24, 2010 at 07:26:57AM -0500, Josh Boyer wrote:
>  >> >> > $ git clone -n git://pkgs.fedoraproject.org/binutils binutils
>  >> >> > pkgs.fedoraproject.org[0: 209.132.181.4]: errno=Connection timed
>  >> >> > out fatal: unable to connect a socket (Connection timed out)
>  >> >> > Cloning into binutils...
>  >> >> > 
>  >> >> > from
> http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114600
>  >> >> 
>  >> >> Hm.  Indeed.  The main hub can resolve and clone that, but the other
>  >> >> builder can't.  I suspect this is an issue with the PHX2 firewall
>  >> >> setup and not really much to do with koji.
>  >> >> 
>  >> >> Dennis, is there an additional step needed to get access to
>  >> >> pkgs.fedoraproject.org on the builders?  Maybe a /etc/hosts entry?
>  >> >> 
>  >> >> josh
>  >> > 
>  >> > add a hosts entry with the ip 10.5.125.44
>  >> 
>  >> OK added and I can do the clone from command line now.  Hopefully this
>  >> builder is set now.
>  > 
>  > Now the git part seems to work but there seems to be a problem getting
>  > the sources. I am not really sure what it means but I suppose it cannot
>  > download the tarball from the lookaside cache.
>  > 
>  > http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114607
>  > 
>  > I found nothing in the logs which looks like an error.
>  
>  fedpkg wasn't installed on either box.  I forgot this when doing the
>  transition to git based SCM.  I've resubmitted the task.  We'll see
>  how it goes now.  Sigh..
>  
>  http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114621
>  
>  josh 
fedpkg needs to be installed in the chroot not on the box. make sure the
srpm-
build group matches the primary arch one

Dennis

[Josh Boyer]

On Wed, Dec 29, 2010 at 9:36 AM, Dennis Gilmore <dennis(a)ausil.us&gt; wrote:
>  fedpkg needs to be installed in the chroot not on the box. make sure
> the srpm-
>  build group matches the primary arch one 
Ah, right.  The tags and groups need to be fixed up in general still.
I'll try to get to it later, but if someone else with admin privs
wants to do it, that would be great.

josh

[Josh Boyer]

On Wed, Dec 29, 2010 at 10:00 AM, Josh Boyer <jwboyer(a)gmail.com&gt; wrote:
>  On Wed, Dec 29, 2010 at 9:36 AM, Dennis Gilmore
> <dennis(a)ausil.us&gt; wrote:
> > fedpkg needs to be installed in the chroot not on the box. make sure the srpm-
> > build group matches the primary arch one
>
>  Ah, right.  The tags and groups need to be fixed up in general still.
>  I'll try to get to it later, but if someone else with admin privs
>  wants to do it, that would be great. 
OK.  Hopefully I have the tags and build groups setup properly now for
f15.  I resubmitted the binutils task again.  We'll see what else I've
missed I guess.

http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114623

josh

[Josh Boyer]

On Fri, Dec 31, 2010 at 11:58 AM, Josh Boyer <jwboyer(a)gmail.com&gt; wrote:
>  On Wed, Dec 29, 2010 at 10:00 AM, Josh Boyer
> <jwboyer(a)gmail.com&gt; wrote:
> > On Wed, Dec 29, 2010 at 9:36 AM, Dennis Gilmore <dennis(a)ausil.us&gt; wrote:
> >> fedpkg needs to be installed in the chroot not on the box. make sure the srpm-
> >> build group matches the primary arch one
> >
> > Ah, right.  The tags and groups need to be fixed up in general still.
> > I'll try to get to it later, but if someone else with admin privs
> > wants to do it, that would be great.
>
>  OK.  Hopefully I have the tags and build groups setup properly now for
>  f15.  I resubmitted the binutils task again.  We'll see what else I've
>  missed I guess.
>
>  http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114623 
That one failed, but I fixed a few more items and eventually it worked:

http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114662

I guess we're good for now?

josh

[Adrian Reber]

On Fri, Dec 31, 2010 at 03:54:43PM -0500, Josh Boyer wrote:
>  On Fri, Dec 31, 2010 at 11:58 AM, Josh Boyer
> <jwboyer(a)gmail.com&gt; wrote:
>  > On Wed, Dec 29, 2010 at 10:00 AM, Josh Boyer <jwboyer(a)gmail.com&gt; wrote:
>  >> On Wed, Dec 29, 2010 at 9:36 AM, Dennis Gilmore <dennis(a)ausil.us&gt; wrote:
>  >>> fedpkg needs to be installed in the chroot not on the box. make sure the
> srpm-
>  >>> build group matches the primary arch one
>  >>
>  >> Ah, right.  The tags and groups need to be fixed up in general still.
>  >> I'll try to get to it later, but if someone else with admin privs
>  >> wants to do it, that would be great.
>  >
>  > OK.  Hopefully I have the tags and build groups setup properly now for
>  > f15.  I resubmitted the binutils task again.  We'll see what else I've
>  > missed I guess.
>  >
>  > http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114623
>  
>  That one failed, but I fixed a few more items and eventually it worked:
>  
>  http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114662
>  
>  I guess we're good for now? 
So far I see no more errors. Thanks for your work!

		Adrian

[Adrian Reber]

On Sat, Jan 01, 2011 at 01:25:04AM +0100, Adrian Reber wrote:
>  > That one failed, but I fixed a few more items and eventually it
> worked:
>  > 
>  > http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114662
>  > 
>  > I guess we're good for now?
>  
>  So far I see no more errors. Thanks for your work! 
Found another problem:

Traceback (most recent call last):
  File "/usr/sbin/kojid", line 1437, in runTask
    response = (handler.run(),)
  File "/usr/sbin/kojid", line 1513, in run
    return self.handler(*self.params,**self.opts)
  File "/usr/sbin/kojid", line 1934, in handler
    h = self.readSRPMHeader(srpm)
  File "/usr/sbin/kojid", line 2007, in readSRPMHeader
    h = koji.get_rpm_header(fo)
  File "/usr/lib/python2.6/site-packages/koji/__init__.py", line 787, in
get_rpm_header
    hdr = ts.hdrFromFdno(fo.fileno())
  File "/usr/lib64/python2.6/site-packages/rpm/transaction.py", line 154, in
hdrFromFdno
    raise rpm.error("error reading package header")
error: error reading package header

http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114707

Sounds like: http://lists.fedoraproject.org/pipermail/buildsys/2010-August/003224.html

		Adrian

[Adrian Reber]

On Sat, Jan 01, 2011 at 10:26:42AM +0100, Adrian Reber wrote:
>  On Sat, Jan 01, 2011 at 01:25:04AM +0100, Adrian Reber wrote:
>  > > That one failed, but I fixed a few more items and eventually it worked:
>  > > 
>  > > http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114662
>  > > 
>  > > I guess we're good for now?
>  > 
>  > So far I see no more errors. Thanks for your work!
>  
>  Found another problem:
>  
>  Traceback (most recent call last):
>    File "/usr/sbin/kojid", line 1437, in runTask
>      response = (handler.run(),)
>    File "/usr/sbin/kojid", line 1513, in run
>      return self.handler(*self.params,**self.opts)
>    File "/usr/sbin/kojid", line 1934, in handler
>      h = self.readSRPMHeader(srpm)
>    File "/usr/sbin/kojid", line 2007, in readSRPMHeader
>      h = koji.get_rpm_header(fo)
>    File "/usr/lib/python2.6/site-packages/koji/__init__.py", line 787, in
> get_rpm_header
>      hdr = ts.hdrFromFdno(fo.fileno())
>    File "/usr/lib64/python2.6/site-packages/rpm/transaction.py", line 154, in
> hdrFromFdno
>      raise rpm.error("error reading package header")
>  error: error reading package header
>  
>  http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114707
>  
>  Sounds like: http://lists.fedoraproject.org/pipermail/buildsys/2010-August/003224.html
and, the packages I am building are not used for the following builds. I
can see from the logs that the dist-f15 repo is created with the files
inherited from f14. The dist-rawhide repo is created from the correct
files but those repos seem to be not used for following builds.

I was looking at the fedora-release package.

		Adrian

[Josh Boyer]

On Sat, Jan 1, 2011 at 7:33 AM, Adrian Reber <adrian(a)lisas.de&gt; wrote:
>  On Sat, Jan 01, 2011 at 10:26:42AM +0100, Adrian Reber wrote:
> > On Sat, Jan 01, 2011 at 01:25:04AM +0100, Adrian Reber wrote:
> > > > That one failed, but I fixed a few more items and eventually it worked:
> > > >
> > > > http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114662
> > > >
> > > > I guess we're good for now?
> > >
> > > So far I see no more errors. Thanks for your work!
> >
> > Found another problem:
> >
> > Traceback (most recent call last):
> >   File "/usr/sbin/kojid", line 1437, in runTask
> >     response = (handler.run(),)
> >   File "/usr/sbin/kojid", line 1513, in run
> >     return self.handler(*self.params,**self.opts)
> >   File "/usr/sbin/kojid", line 1934, in handler
> >     h = self.readSRPMHeader(srpm)
> >   File "/usr/sbin/kojid", line 2007, in readSRPMHeader
> >     h = koji.get_rpm_header(fo)
> >   File "/usr/lib/python2.6/site-packages/koji/__init__.py", line 787, in
> get_rpm_header
> >     hdr = ts.hdrFromFdno(fo.fileno())
> >   File "/usr/lib64/python2.6/site-packages/rpm/transaction.py", line 154,
> in hdrFromFdno
> >     raise rpm.error("error reading package header")
> > error: error reading package header
> >
> > http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114707
> >
> > Sounds like:
> http://lists.fedoraproject.org/pipermail/buildsys/2010-August/003224.html 
Yes, it does sound like that.  I would have thought it to be fixed in
koji 1.6.0 already though.  Maybe not.  Dan, do you know if the
workaround is still needed in 1.6?

>  and, the packages I am building are not used for the following
> builds. I
>  can see from the logs that the dist-f15 repo is created with the files
>  inherited from f14. The dist-rawhide repo is created from the correct
>  files but those repos seem to be not used for following builds.
>
>  I was looking at the fedora-release package. 
I think I fixed that now.  It was an issue with inheritance priority.

josh

[Dan Horák]

Josh Boyer píše v So 01. 01. 2011 v 08:37 -0500: 
>  On Sat, Jan 1, 2011 at 7:33 AM, Adrian Reber <adrian(a)lisas.de&gt;
> wrote:
>  > On Sat, Jan 01, 2011 at 10:26:42AM +0100, Adrian Reber wrote:
>  >> On Sat, Jan 01, 2011 at 01:25:04AM +0100, Adrian Reber wrote:
>  >> > > That one failed, but I fixed a few more items and eventually it
> worked:
>  >> > >
>  >> > > http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114662
>  >> > >
>  >> > > I guess we're good for now?
>  >> >
>  >> > So far I see no more errors. Thanks for your work!
>  >>
>  >> Found another problem:
>  >>
>  >> Traceback (most recent call last):
>  >>   File "/usr/sbin/kojid", line 1437, in runTask
>  >>     response = (handler.run(),)
>  >>   File "/usr/sbin/kojid", line 1513, in run
>  >>     return self.handler(*self.params,**self.opts)
>  >>   File "/usr/sbin/kojid", line 1934, in handler
>  >>     h = self.readSRPMHeader(srpm)
>  >>   File "/usr/sbin/kojid", line 2007, in readSRPMHeader
>  >>     h = koji.get_rpm_header(fo)
>  >>   File "/usr/lib/python2.6/site-packages/koji/__init__.py", line 787,
> in get_rpm_header
>  >>     hdr = ts.hdrFromFdno(fo.fileno())
>  >>   File "/usr/lib64/python2.6/site-packages/rpm/transaction.py", line
> 154, in hdrFromFdno
>  >>     raise rpm.error("error reading package header")
>  >> error: error reading package header
>  >>
>  >> http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114707
>  >>
>  >> Sounds like:
> http://lists.fedoraproject.org/pipermail/buildsys/2010-August/003224.html
>  
>  Yes, it does sound like that.  I would have thought it to be fixed in
>  koji 1.6.0 already though.  Maybe not.  Dan, do you know if the
>  workaround is still needed in 1.6? 
Seems it's still needed, but I didn't try to push it to upstream as the
workaround is rather a dirty hack. I'm surprised it should be needed in
the ppc koji where the builder and hub are on the same local network
AFAIK.


Dan

[Josh Boyer]

On Sat, Jan 1, 2011 at 9:27 AM, Dan Horák <dan(a)danny.cz&gt; wrote:
>  Josh Boyer píše v So 01. 01. 2011 v 08:37 -0500:
> > On Sat, Jan 1, 2011 at 7:33 AM, Adrian Reber <adrian(a)lisas.de&gt; wrote:
> > > On Sat, Jan 01, 2011 at 10:26:42AM +0100, Adrian Reber wrote:
> > >> On Sat, Jan 01, 2011 at 01:25:04AM +0100, Adrian Reber wrote:
> > >> > > That one failed, but I fixed a few more items and eventually it
> worked:
> > >> > >
> > >> > > http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114662
> > >> > >
> > >> > > I guess we're good for now?
> > >> >
> > >> > So far I see no more errors. Thanks for your work!
> > >>
> > >> Found another problem:
> > >>
> > >> Traceback (most recent call last):
> > >>   File "/usr/sbin/kojid", line 1437, in runTask
> > >>     response = (handler.run(),)
> > >>   File "/usr/sbin/kojid", line 1513, in run
> > >>     return self.handler(*self.params,**self.opts)
> > >>   File "/usr/sbin/kojid", line 1934, in handler
> > >>     h = self.readSRPMHeader(srpm)
> > >>   File "/usr/sbin/kojid", line 2007, in readSRPMHeader
> > >>     h = koji.get_rpm_header(fo)
> > >>   File "/usr/lib/python2.6/site-packages/koji/__init__.py", line
> 787, in get_rpm_header
> > >>     hdr = ts.hdrFromFdno(fo.fileno())
> > >>   File "/usr/lib64/python2.6/site-packages/rpm/transaction.py",
> line 154, in hdrFromFdno
> > >>     raise rpm.error("error reading package header")
> > >> error: error reading package header
> > >>
> > >> http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114707
> > >>
> > >> Sounds like:
> http://lists.fedoraproject.org/pipermail/buildsys/2010-August/003224.html
> >
> > Yes, it does sound like that.  I would have thought it to be fixed in
> > koji 1.6.0 already though.  Maybe not.  Dan, do you know if the
> > workaround is still needed in 1.6?
>
>  Seems it's still needed, but I didn't try to push it to upstream as the
>  workaround is rather a dirty hack. I'm surprised it should be needed in
>  the ppc koji where the builder and hub are on the same local network
>  AFAIK. 
OK.  I'll try to patch them soon.  I've seen it on machines elsewhere
that are sitting on the same switch even, so apparently it's not that
uncommon?

josh

[Adrian Reber]

On Sat, Jan 01, 2011 at 10:18:07AM -0500, Josh Boyer wrote:
>  >> >> Found another problem:
>  >> >>
>  >> >> Traceback (most recent call last):
>  >> >>   File "/usr/sbin/kojid", line 1437, in runTask
>  >> >>     response = (handler.run(),)
>  >> >>   File "/usr/sbin/kojid", line 1513, in run
>  >> >>     return self.handler(*self.params,**self.opts)
>  >> >>   File "/usr/sbin/kojid", line 1934, in handler
>  >> >>     h = self.readSRPMHeader(srpm)
>  >> >>   File "/usr/sbin/kojid", line 2007, in readSRPMHeader
>  >> >>     h = koji.get_rpm_header(fo)
>  >> >>   File "/usr/lib/python2.6/site-packages/koji/__init__.py",
> line 787, in get_rpm_header
>  >> >>     hdr = ts.hdrFromFdno(fo.fileno())
>  >> >>   File
> "/usr/lib64/python2.6/site-packages/rpm/transaction.py", line 154, in
> hdrFromFdno
>  >> >>     raise rpm.error("error reading package header")
>  >> >> error: error reading package header
>  >> >>
>  >> >> http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=114707
>  >> >>
>  >> >> Sounds like:
> http://lists.fedoraproject.org/pipermail/buildsys/2010-August/003224.html
>  >>
>  >> Yes, it does sound like that.  I would have thought it to be fixed in
>  >> koji 1.6.0 already though.  Maybe not.  Dan, do you know if the
>  >> workaround is still needed in 1.6?
>  >
>  > Seems it's still needed, but I didn't try to push it to upstream as the
>  > workaround is rather a dirty hack. I'm surprised it should be needed in
>  > the ppc koji where the builder and hub are on the same local network
>  > AFAIK.
>  
>  OK.  I'll try to patch them soon.  I've seen it on machines elsewhere
>  that are sitting on the same switch even, so apparently it's not that
>  uncommon? 
Did you have time to apply that patch? I have seen this now with glibc
and gdb and I think, if this patch actually solves the problem, I need
it to continue with the f15 rebuilds.

		Adrian