| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
The preliminary fix in 1.0.67 wasn't sufficient, and was extended in
1.0.72 in a different manner. Let's standardize all for loops.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Because debootstrap is relatively slow, I've named the test according
to what is being bootstrapped (Debian testing) rather than the checks
that are performed, with the intention that additional checks can
be added to it.
Signed-off-by: Simon McVittie <smcv@debian.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In a plain chroot or on real hardware, it is preferable to use mknod
to create /dev/ptmx. This works as intended with older chroot managers
such as sbuild and pbuilder, which were designed for the semantics of
"legacy" /dev/pts (a single non-virtualized pty subsystem per kernel)
and so mount /dev/pts without the newinstance option. It also works
in newer kernels where /dev/pts always behaves as though the
newinstance option was given, because on those kernels, opening a
(c,5,2) device node automatically looks for an adjacent pts directory
and uses its ptmx device node instead.
However, if we are running debootstrap inside a restricted container
such as lxc or systemd-nspawn, mknod ptmx c 5 2 might not be allowed.
If so, fall back to a symlink with a warning. This mode is fine if
the debootstrap will be used with systemd-nspawn or lxc, or if a
devtmpfs will be mounted over its /dev, but will not work for older
chroot managers like sbuild or pbuilder, because those chroot
managers leave the ptmxmode mount option at its default 000, causing
permission to open the pts/ptmx device node to be denied.
Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817236
Signed-off-by: Simon McVittie <smcv@debian.org>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
#844221).
|
| |
|
|
|
|
|
|
| |
The initial tr|sed|tr looked nice on paper but doesn't work within a d-i
context, so let's switch to a shell-only implementation supplied by
Ansgar Burchardt.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- make a separate split_inline_sig function
- move downloading all three files to download_release_sig
- don't check InRelease signature if signature checking is disabled
Thanks to Ansgar Burchardt for the suggestions.
Signed-off-by: Julien Cristau <jcristau@debian.org>
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| | |
Thanks to Marco d'Itri for the patch.
|
| | |
|
| | |
|
| |
| |
| |
| | |
Bug: https://bugs.debian.org/825034
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Bug: https://bugs.debian.org/548880
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In old releases, notably in Debian 6 (Squeeze), multiple packages ship
the same files using diversions (e.g. bash/dash). As debootstrap
naively extracts packages without implementing diversions itself, it
relies on tar replacing the files without an error.
Ideally we could use `tar --keep-directory-symlink`, but this is
likely not portable enough. So continue to use `tar -k`, but only for
future releases. Note that this requires no file conflicts among
packages debootstrap installs (which is a good idea anyway as they
might be extracted in the wrong order).
Bug: https://bugs.debian.org/838388
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
The code using makedev to create devices.tar.gz was removed in
26ae52971b21e14c6c81af3b8aa0211bc3553dd2
|
| |
| |
| |
| |
| | |
Just as jessie, jessie-kfreebsd doesn't support merged-/usr well
enough.
|
| | |
|
| |
| |
| |
| |
| |
| | |
Pushed by mistake.
This reverts commit fc9b919df580daf1183649bf197cb2c06a41e95b.
|
| |
| |
| |
| | |
Thanks, David Schneider!
|
| | |
|
|/
|
|
|
| |
Split up detached signature from signed data, in effect re-creating a
Release and Release.gpg pair that we can verify with gpgv.
|
| |
|
|
|
|
| |
Bug: https://bugs.debian.org/837649
|
| |
|
|
|
|
| |
No package changes needed
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Using the `dpkg-deb` extractor, or more precise `dpkg-deb -f`, together
with busybox' `tar` results in failure: `dpkg-deb` passes additional
options to `tar` that are not understood by busybox' implementation such
as `--warning=no-timestamp`.
We can avoid this by feigning the installation of `dpkg` in the second
stage. Here it is possible to call the installed `dpkg-deb` together
with the installed (GNU) `tar`.
|
| |
|
|
|
|
|
|
| |
Unlike suite names (stable, testing, ...), the codename from the Release
file does not change meaning over time. So the codename should be used
for any hacks that should only happen for some releases.
|