Bug#189058: base-installer segfaults during install
On Wed, Apr 16, 2003 at 01:06:44PM -0400, Joe Nahmias wrote:
> Hello Chris!
>
> Chris Tillman wrote:
> > On Tue, Apr 15, 2003 at 11:23:48PM -0400, Joe Nahmias wrote:
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > >
> > > Also, poking around, I noticed that debootstrap writes an error log
> > > file into /target/var/log/debootstrap.err.log. This file contains:
> > >
> > > ==========8<=====================
> > > id: unknown user name: 0
> > > [: 0: unknown operand
> > > printf: No such file or directory
> > > printf: No such file or directory
> > > ==========>8=====================
> > >
> > > I guess this means that `id` in busybox-cvs is broken. You can
> > > reproduce this by running `id` from the shell on vc2. Should I file a
> > > bug??
> >
> > Definitely, I think you found it.
> Submitted! Bug #189309.
>
> > > After this, I added a "set -x" to /usr/sbin/debootstrap and reran the
> > > base-installer. Boy, did I get alot of output!! Anyways, it seems that
> > > the segfault happens in a call to just_get() which is defined in
> > > /usr/lib/debootstrap/functions. It is called as:
> > >
> > > `just_get http://ftp.us.debian.org/debian/dists/sarge/main/binary-i386/Packages.gz /target/debootstrap.invalid_dists_sarge_main_binary-i386_Packages.gz`
> > >
> > > After setting the "from" and "dest" variables, it does a `mkdir -p
> > > /target` and then does the tests on lines 169 and 171 and then
> > > segfaults _before_ calling wgetprogress (apparently, since it doesn't
> > > print the call to it).
> >
> > Anthony will appreciate your summarization in a debootstrap bug.
> > Sounds like you've got it nailed down to the line number.
> OK. I cloned/retitled/reassigned this bug to debootstrap (Bug #189311).
>
> Now, what should be done with this bug? Leave it until the underlying
> issues are addressed or close it?
It should not be closed. Usually bugs are closed by the
build system, when a package is accepted with a change log
that says it Closes: the bug.
Unless they're bogus, then the responsible maintainer sends
mail to e.g. 189311-done@bugs.debian.org.
>From Anthony's mail, it sounds like it's really a d-i library
issue; way beyond me, that's for sure.
--
http://Www.TruthAboutWar.org
Chris Tillman
- Linux Rox -
Reply to: