Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
config --config.
|
|
directories in lb_config --config option.
|
|
|
|
|
|
or non-free is not enabled.
|
|
firmware inclusion in ubuntu mode anyway.
Also, we're not keeping this as ubuntu should just update their archive
structure for content files to match debian. Not worth keeping temporary
extra turns just for ubuntu.
|
|
|
|
|
|
#685791).
|
|
|
|
|
|
|
|
|
|
bootstrap_cdebootstrap too (Closes: #694102).
|
|
into bootloader configurations (Closes: #694723).
|
|
other live packages.
|
|
|
|
warning messages during live-boots medium integrity check.
|
|
|
|
|
|
actually included, to avoid cluttering debconf db by default on all systems.
|
|
old-style Contents files in the archive.
|
|
by Thanatermesis <thanatermesis@gmail.com> (Closes: #685924).
|
|
Thanatermesis <thanatermesis@gmail.com> (Closes: #693250).
|
|
|
|
<frank@familie-gard.de> (Closes: #691930).
|
|
this option in the first place.
|
|
switching to sysvinit for those distributions that default to systemd.
|
|
might not always pull in sysvinit packages anymore.
|
|
|
|
was really supported anyway.
|
|
|
|
into the bootstrapped chroot to avoid sids apt failing on mirrors with bzip2 indices only.
|
|
When we rebuild an image with changed local archives,
we would preferably remove the already existing preferences files.
However, there's no way to make sure that we remove enough or too
much, hence we don't remove any at all and stay with the dogma:
"If you change something in the config tree affecting $stage,
you need to rebuild that stage from scratch."
So for pinning changes for local archives, this means, since it's
affecting the chroot stage, we'll have to rebuild the chroot stage:
"lb clean --chroot && lb chroot"
|
|
|
|
unrecognized option message.
|
|
config/includes.debian-installer.
|
|
|
|
from within the config tree in lb_config.
|
|
custom templates should be used instead.
Rather than doing all the heavy lifting in live-build that nobody really
uses and which is quite inflexible, users should (in line with the syslinux
handling) either stick with the default grub configurations, or, supply
a custom one to live-build, rather than partial/single files only.
|
|
|