At Tue, 19 Dec 2006 17:56:58 -0500,
Hubert Chan wrote:
>
> On 2006-12-19 17:28:06 -0500 Junichi Uekawa <[EMAIL PROTECTED]>
> wrote:
>
> >>> This usually sounds like a genuine cowdancer bug.
> >>> > However, it might be a bit difficult to track it down.
> >>> > Could you put some probes in, such as what's the env var
> >>> (especially
> >>> LD_PRELOAD and LD_LIBRARY_PATH values) at the point of error, so
> >>> that
> >>> I can see what's wrong?
> >>> > That way we may be able to narrow down the problem to a small
> >>> testcase
> >>> which makes debugging so much easier.
> >>
> >> On another thought, it could be yet another of 'libacl' breakage.
> >> Does it still happen after recreating the chroot with latest sid ?
> >
> >
> > On yet another thought, libacl breakage was 17 Dec - 18 Dec, so
> > probably it doesn't apply. Humph.
> >
>
> It happened several months ago -- I just got around to reporting the
> bug just now. So it's probably not that.
>
> Also, the pbuilder and cowbuilder setups should be exactly the same --
> I build the pbuilder tarball by just tar-ing up the cowbuilder
> directory. So everything should be exactly the same.
>
>
> I'll add stuff to print out the environment when I get a chance, and
> I'll let you know what happens.
I could reproduce the build with the current package in sid.
adding -v option to dh_fixperms, I got this:
find debian/gnustep-base-common -print0 2>/dev/null | xargs -0r chown
--no-dereference 0:0
cowdancer: mkstemp: Bad file descriptor
chown: changing ownership of
`debian/gnustep-base-common/usr/share/GNUstep/Libraries/gnustep-base/NSTimeZones/localtime':
Cannot allocate memory
dh_fixperms: command returned error code
make: *** [binary-indep] Error 1
'./usr/share/GNUstep/Libraries/gnustep-base/NSTimeZones/localtime'
looks like a symbollic link, and apparently, that is probably the
problem. My guess is that cowbuilder is not handling chown of a
symbollic link correctly.
regards,
junichi
--
[EMAIL PROTECTED],netfort.gr.jp} Debian Project
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
