| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
| |
Bug: https://bugs.debian.org/825034
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
| |
Just as jessie, jessie-kfreebsd doesn't support merged-/usr well
enough.
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
(setup_devices now only deals with static device nodes) and move the calls
to setup_devices from the beginning of the second stage to the end of the
first stage. setup_dynamic_devices mounts the appropriate filesystems
which provide dynamic device nodes for the architectures which need one
in debootstrap (kfreebsd and hurd). This fixes a bug in --second-stage
introduced in 1.0.34 and exposed by the devices-related changes of 1.0.76:
the second stage debootstrap runs "dpkg --print-architecture >/dev/null" at
the very beginning of the program when /dev is still empty, so it creates an
empty regular file in place of /dev/null and this will cause mknod to fail
later. (Closes: #813232)
|
| |
|
|
| |
installations. This makes it possible to copy certificates that were built into the installer to /usr/local/share/ca-certificates/ and thus have them continue to be trusted after installation.
|
| |
|
|
|
|
|
| |
It may still be necessary to copy certificates into place, but there's at
least a reasonable chance that somebody installing from HTTPS may want to
keep using it, and we have to install apt-transport-https at this point
otherwise they won't be able to do that end-to-end.
|
| | |
|
| |
|
|
| |
debian-installer-utils. This is the primary way to disable daemon startup.
|
| | |
|
| |
|
|
|
| |
Thanks to Mark Hymers. Closes: #619700
Ack by otavio
|
| |
|
|
|
|
|
|
|
|
| |
* Recommend debian-archive-keyring, and if it is installed,
default to checking gpg signatures of the Release file against it
when bootstrapping sid, squeeze, wheezy, etch, and lenny.
Closes: #560038
* Add --no-check-gpg option that can be used to disable release file
verification.
* Needs base-installer 1.117.
|
| |
|
|
| |
returned to a single-directory db layout.
|
| |
|
|
| |
--print-architecture) -> . symlink, to cope with multiarch dpkg.
|
| |
|
|
| |
install of a package.
|
| |
|
|
|
|
| |
diversion problem. (#329394)
r65231
|
| |
|
|
|
|
|
| |
Afaics, neither CONF_BASE_FAIL_FIVE nor CONF_BASE_FAIL is used anywhere
(in eg, base-installer), so I unified those also.
r65230
|
| |
|
|
| |
r65229
|
| |
|
|
|
|
| |
Ptach by Karl Goetz. Closes: #601821
r65224
|
|
|
and add a section to README explaining an easy way to run
debootstrap w/o installing it. Closes: #345762
r62297
|
