Hey!

Starting with 0.7.0, the two-stage bootstrap doesn't work anymore with
sid (didn't test another suite):

cdebootstrap --foreign --flavour=build sid /var/tmp/sid
chroot /var/tmp/sid /sbin/cdebootstrap-foreign

[...]
Unpacking mawk (1.3.3-17) over (1.3.3-17) ...
dpkg: regarding .../base-files_9.4_amd64.deb containing base-files, pre-dependency problem:
 base-files pre-depends on awk
  mawk provides awk but is unpacked but not configured.

dpkg: error processing archive /var/cache/bootstrap/base-files_9.4_amd64.deb (--install):
 pre-dependency problem - not installing base-files
[...]
Errors were encountered while processing:
 /var/cache/bootstrap/base-files_9.4_amd64.deb
Failed to run dpkg!

It works fine with cdebootstrap 0.6.5. I didn't investigate more since
I am not familiar with those pre-dependencies stuff.

- -- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages cdebootstrap depends on:
ii  debian-archive-keyring      2014.3
ii  gpgv                        1.4.19-5
ii  libbz2-1.0                  1.0.6-8
ii  libc6                       2.19-22
ii  libdebian-installer-extra4  0.101
ii  libdebian-installer4        0.101
ii  liblzma5                    5.1.1alpha+20120614-2.1
ii  wget                        1.16.3-3
ii  zlib1g                      1:1.2.8.dfsg-2+b1

cdebootstrap recommends no packages.

cdebootstrap suggests no packages.

- -- debconf-show failed
iQIcBAEBCAAGBQJWEEr0AAoJEJWkL+g1NSX5s9QP/0lot7GUwbQwAgQd5nBUU6hx
MgUcWMq86ie8Ju5QTnX0LK8HKovRB3hTgXw5EljiFiwaWlj3drubeCzY17I5AwF1
zG35GPD7wwckLEeCDiF6v4XYgeiIyncVPrlsXqJRcjQNY/cQ/GZoQ7R5u+j0Mkmg
anUy1xCJo99jOuPX7vmTMqstfJhRJBHM/i5Kyl3Ppd1ssvVLolpqYj9ix7RlZ5bh
dUhHEEyieKoMKgdM2gGMaFw1jqatNc+1gMimnR6V7xifKJyGIRVT2ySOm/FtF8IS
D2gI7/mJoTi2u00Nc6/XVOaJIf9rW/Xi40gU7F7wWSN/fjlvabha3BNw/r1sp+Bv
YrgQnOt8rCOsJRSO5rq9Gpr7j4TNxs+8UvLKgwpnwZ4WoFsi3caTy8w4PiEem59M
BjNkxhRV1+PGCPYITd74Iob2AQKXHenr/EzUcVcitL756gUemzIfxvC0KfeqcOBq
CTmHlhYhEBwQlyBzZZaOLC4c37Mhd7/MEjn5RobKa3Rz3JRQb7r6f95Fg/qR720b
dyTC8fbwU9auT7FzYZRF+Po3LoACP3bPNjCYQgfV7z0B+KmZFF43r4dSFSZMNESL
YPYTVK+jAfptDt2/79ZzBdessSEWiFUuYCxV7MByx2KWt4R0HbQj5bTR2kP4wuYJ
t7arDAY8xPdqyGwOrMTk
=g9CI
-----END PGP SIGNATURE-----

 ❦  3 octobre 2015 23:39 +0200, Vincent Bernat <bernat@debian.org> :

Without --foreign, the list of packages used for dpkg --unpack and the
list of packages for dpkg --install is different (no mawk or basefiles
in the second set). With --foreign, the two lists are identical.

I suppose that the paths taken with and without --foreign in
action_install_essential() are different, but I am unable to follow the
logic.

Any hint?