On (30/06/06 01:13), Junichi Uekawa wrote:
> Hi,
> 
> > I have just encountered this bug again, I was making the mistake as
> > running ipcs as an unpriveledged user outside the chroot, so it couldn't
> > see the appropriate queues. My apologies for this mistake.
> > 
> > Since I rebooted I have build several packages, I had maybe one failure
> > in that time, and the build just previous to the one that triggered the
> > problem did not fail.
> > 
> > I have attached the output of ipcs. There is one msq removed from what
> > there was when it failed. 1234 is the uid in ~/.pbuilderrc.
> > 
> > Have you any more suggestions for debugging?
> 
> It's sounding like more of a problem on fakeroot, but can you narrow
> the problem down to a package?  Does it happen when you're building a
> particular package? Or is it always?

Yes I think it might be fakeroot, or at least the way {cow,p}builder uses
fakeroot. Perhaps it is #229050, which doesn't seem to have had much
attention. You know better than me whether it is possible that
cowbuilder triggers that behaviour. Though one of the messaes in that
report says that it doesn't even need to be threaded.

It can be when building any package, and I haven't seen a pattern
forming yet, but it seems that there are a couple of queues left over
after some builds, and then a failed build increases the number even
more. Then it reaches the point where there are no spare ones, and I
have to manually clean them. This then allows me to continue a bit.

Attached are a couple of my build logs, I have just modified the script
to include ipcs output before and afterwards. Hopefully this will help
track the problem down.

> 
> Something I would suspect would be the environment.  checking 'env'
> output 

attached, I can't see anything odd.

> and looking at ldd output of packages and checking their
> versions might be worthwhile.

ldd of the packages I am building, or the ones I am using?

> 
> At least, it doesn't seem to be a problem reproduced on many systems, 
> which is just weird.
> 

Yes, I'm not sure what the crucial difference is.

-- 
  James Westby
  [EMAIL PROTECTED]
  http://jameswestby.net/



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to