Chaskiel M Grundman wrote:
> 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
Thanks for finding this. I think I've fixed it in CVS, won't be
available for a few days in the archive though.
> 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.
I looked again at your report, and one possibility is some breakage that
was present in base-installer on or about March 9th. That took a while
to get moved into testing, and I think it happened yesterday. The fixed
version is on debian.mirrors.pair.com now. I expect this will probably
fix your problem.
--
see shy jo
Attachment:
signature.asc
Description: Digital signature