Stephan Sürken writes: > On Di, 2016-09-20 at 21:09 +0200, Julien Cristau wrote: >> > It always exits here with exit code 2, without any further error >> > message (not even when using --verbose). >> > >> There should be a log inside the target directory. > > ah, sure ;). > > debootstrap/debootstrap.log says: > > --- > gpgv: Signature made Sat Apr 25 13:01:30 2015 CEST > gpgv: using RSA key AED4B06F473041FA > gpgv: Good signature from "Debian Archive Automatic Signing Key (6.0/squeeze) > <ftpmas...@debian.org>" > gpgv: Signature made Sat Apr 25 13:05:42 2015 CEST > gpgv: using RSA key 64481591B98321F9 > gpgv: Good signature from "Squeeze Stable Release Key > <debian-rele...@lists.debian.org>" > tar: ./usr/share/man/man1/sh.1.gz: Cannot create symlink to 'dash.1.gz': File > exists > tar: ./bin/sh: Cannot create symlink to 'dash': File exists > tar: Exiting with failure status due to previous errors
Ah, I'm to blame for that. [1] added `-k` to the options passed to tar in order to avoid replacing the new symlinks from / to /usr with real directories. However it looks like tar returns an error when there are actual file conflicts (as opposed to just symlink vs. directory). Only adding -k for newer distributions (i.e. the ones that merged-/usr supports) should work around the problem. Just --keep-directory-symlink would of course be ideal, but I doubt it is supported everywhere (being a long option to start with). Ansgar [1] https://anonscm.debian.org/cgit/d-i/debootstrap.git/commit/?id=6b79352a205a96cee441ae0c6247c4616097a517