Bug#237169: install report: base system does not install for 20040308 installer
--On Saturday, March 13, 2004 14:01:48 -0500 Joey Hess <joeyh@debian.org>
wrote:
> Are you sure you told it to format and mount the partition? This could
> easily be leftovers from a previous install, and nothing that was run
> unmounts /target.
Yes, I'm sure.
I also think I've found one of the problem:
debian.mirrors.pair.com does not use any path prefix. "dists" and "pool"
are in the top level of the ftp or http root. As a result, $DIRECTORY is
the empty string.
from base-installer's postinst:
configure_apt () {
# let apt inside the chroot see the cdrom
umount /target$DIRECTORY 2>/dev/null || true
if [ "$PROTOCOL" = file ] ; then
[irrelevant stuff, since protocol is http]
fi
# Move files to where apt expects them to avoid another download or
copy.
APTLISTDIR=/target/var/lib/apt/lists
APTDIR=`echo $DIRECTORY | tr "/" "_"`
DEBOOTSTRAPLIST="$APTLISTDIR/debootstrap.invalid_dists_${DISTRIBUTION}"
APTLIST="$APTLISTDIR/${MIRROR}${APTDIR}_dists_${DISTRIBUTION}"
mv ${DEBOOTSTRAPLIST}_Release ${APTLIST}_Release
mv ${DEBOOTSTRAPLIST}_main_binary-${ARCH}_Packages
${APTLIST}_main_binary-${ARCH}_Packages
# sources.list uses space to separate the components, not comma
COMPONENTS=`echo $COMPONENTS | tr , " "`
APTSOURCE="$PROTOCOL://$MIRROR$DIRECTORY"
[ ! -d /target/etc/apt ] && mkdir -p /target/etc/apt
echo "deb $APTSOURCE $DISTRIBUTION $COMPONENTS" >
/target/etc/apt/sources.list
}
This also explains why the run that I produced the logfiles from is
different from the earlier runs (the earlier runs completed an "apt-get
update" before dying): In all the earlier runs, I had a /home filesystem.
This time around, to save formatting time, I didn't create it. As a result,
umount /target/ succeeded instead of getting a device busy error. I will
now re-run the install with /home present and get some new logfiles.
Reply to: