[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#452664: Can't upgrade libc6 in cowbuilder



reassign 452664 cowdancer
thanks

On Sat, Dec 01, 2007 at 03:27:35PM +0000, Bas Zoetekouw wrote:
> Hi Pierre!
> 
> You wrote:
> 
> > > When I tried to upgrade my cowbuilder environment (i386 env on amd64),
> > > I got this error:
> > 
> >   you do that using linux32 ? (I don't think it matters much but who
> > knows...). Could you also try to reproduce that in a simple
> > deboostrapped chroot to see if the cowbuilder LD_PRELOAD isn;'t the
> > culprit ?
> 
> This bug is starting to look more and more like a Heisenbug.  Upgrading libc6
> only fails about half of the time, but other packages (tzdata for example) also
> fail sometimes with similar "out of memory errors":
> 
> etting up tzdata (2007i-2) ...
> cowdancer: unexpected WIFEXITED status in waitpid
> /var/lib/dpkg/info/tzdata.postinst: line 29: /etc/timezone: Cannot allocate memory
> dpkg: error processing tzdata (--configure):
>  subprocess post-installation script returned error exit status 1
> Errors were encountered while processing:
>  tzdata
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> However, the bug goes away if I unset the libcowdancer.so LD_PRELOAD, I guess
> that's where the problem is in.
> 
> Some more debugging shows that the errors occors in the call to debconf:
> 
> + PERL_DL_NONLAZY=1
> ++ export PERL_DL_NONLAZY
> ++ '[' '' ']'
> ++ exec /usr/share/debconf/frontend /var/lib/dpkg/info/libc6.postinst configure 2.7-3
> cowdancer: unexpected WIFEXITED status in waitpid
> /var/lib/dpkg/info/libc6.postinst: line 142: /etc/ld.so.conf: Cannot allocate memory
> 
> 
> So, I guess this really is a bug in cowdancer, although I have no idea
> what the problem could be. 

  hmm probably.

-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org

Attachment: pgpokSZJQmc9e.pgp
Description: PGP signature


Reply to: