This avoids having more desktop managers, only xfwm4 will be installed
in the live image.

The part_*.mod modules are not inside the signed .efi-file, so they must
not be 'insmod'ed in secure boot mode.

In secure boot mode, only the unifont.pf2 is inside the signed
.efi-file. To make secure and non-secure boot identical, use only the
unifont.

The font size was reduced to fully capture the long live-build version.
Exported without Inkscape information.
Manually adjusted the coordinates to use integers instead of fractional
coordinates (for sharper conversion to png).

This adds the version information on the grub splash screen and offers
the image at 800x600 instead of 640x480, which looks less unsharp.

When (intel|amd64)-microcode is present, the structure of the ramdisk is
more complex. `lsinitramfs` can see all files.

See https://lists.debian.org/debian-live/2022/04/msg00014.html

memtest86+ switched to /boot/memtest86+ia32.{bin,efi} for 32bits to be
coherent with the usual EFI naming.

Roland Clobus authored Jan 14, 2023 and Luca Boccassi committed Jan 31, 2023

apt-secure will now accept the local repository and Calamares can be run
without network connections.

Roland Clobus authored Jan 14, 2023 and Luca Boccassi committed Jan 31, 2023

d-i and Calamares select the needed grub packages based on how the
computer is started (BIOS vs UEFI). Because the packages for each
variant conflict, they must be provided as .deb files.

Roland Clobus authored Jan 14, 2023 and Luca Boccassi committed Jan 31, 2023

Without the quotes, the * inside the exclusion lists will be treated as
a will card, instead of the literal star.

Roland Clobus authored Jan 08, 2023 and Luca Boccassi committed Jan 31, 2023

first.

The LIVE_BUILD location will only be added if LIVE_BUILD is set.

Commit 8403487d introduced in the chroot stage a naming scheme for local
archive keys which distinguishes between ASCII-armored keys and binary
ones, and then adds the appropriate extension (either `.asc` or `.gpg`,
respectively) when copying them to `/etc/apt/trusted.gpg.d`.

However, this change was not applied to the binary stage: ASCII-armored
and binary keys are still both copied with the `.asc` extension, which
introduces a discrepancy between the two stages. This, in turn,
may prevent using the same `.list` file for both stages, as entries
such as

    deb [signed-by=/etc/apt/trusted.gpg.d/my-repository.key.asc] ...

will fail in the chroot stage if `config/archives/my-repository.key`
is in binary format (as it will be copied with the `.gpg` extension),
while entries such as

    deb [signed-by=/etc/apt/trusted.gpg.d/my-repository.key.gpg] ...

will fail in the binary stage (as the key will this time be copied
with the `.asc` extension).

Previous commits to support Memtest86+ 6.00+ split the files into
"memtest" (backwards compatible / new BIOS name) and "memtest.efi"
(new EFI name).  However, the 6.00 non-EFI binaries are now
32/64-bit, and will not work with GRUB's linux16 boot when using GRUB
for BIOS boot.

- Legacy Memtest86+ pre-6.00 will continue to be "memtest", linux16
  (continue to support builds on current Debian stable bullseye)
- Change 6.00+ filename to "memtest.bin"
- GRUB memtest.cfg contains logic for legacy / new bios / new EFI
- Change EFI boot from "chainloader" to "linux", which allows for
  passing command line options to Memtest86+
- syslinux @MEMTEST@ will conditionally be memtest.bin or memtest
- @MEMTEST_BIN@ will conditionally be memtest.bin or memtest, but is
  completely legacy at this point (all internal code paths now check
  for @MEMTEST_DIR@/memtest or @MEMTEST_DIR@/memtest.bin)

Getting complicated, but this logic can be simplified again once we
no longer need to support current Debian stable.

Roland Clobus authored Nov 13, 2022 and Luca Boccassi committed Nov 14, 2022

If e.g. the required packages for the git build cannot be installed,
abort early instead of attempting to build the installer.

- BIOS: Final filename doesn't change (memtest), but now uses a
  64-bit version on amd64.
- EFI: Now included as memtest.efi; 32-bit on i386, 64-bit on amd64.
  As it's GRUB-only, we can test for the existence of memtest.efi
  (6.00+ only) in GRUB itself.
- Add @MEMTEST_DIR@ to facilitate directory-based testing in GRUB.

This expands upon the previous MVP commit
15e78a3e .

Ryan Finnie authored Oct 31, 2022 and Luca Boccassi committed Oct 31, 2022

memtest86+ 6.00-1 (in testing as of this date) adds and changes its
available binaries:

  - /boot/memtest86+x32.bin
  - /boot/memtest86+x32.efi
  - /boot/memtest86+x64.bin
  - /boot/memtest86+x64.efi

Future live-build functionality would ideally incorporate these new
binaries (x64 for amd64 builds, efi for grub-efi), but in the meantime,
this is an MVP update which supports either old memtest86.bin or new
memtest86+x32.bin.

"jobs:pages config key may not be used with 'rules': except"

Fixes: d2722e8f (Fix permissions and ownership of chroot_hosts and chroot_hostname copied files)

Roland Clobus authored Aug 10, 2022 and Luca Boccassi committed Aug 10, 2022

The request asked for 5 additional variables to be resolved for the SVG
images:
Added: LB_ISO_APPLICATION, LB_ISO_PUBLISHER and LB_LINUX_PACKAGES
Not added: LB_ISO_PREPARER: xorriso recommends not changing this
variable
Not added: LB_ISO_VOLUME: is can contain '@ISOVOLUME_TS@' which resolves
to a timestamp and would need additional handling

See https://lists.debian.org/debian-boot/2022/08/msg00035.html

For reproducibly building live-images, it turns out that the initial
build does not necessarily have to use a snapshot server.
Within a time slot of 6 hours (the interval between synchronisations of
the Debian archive) the reproducibility of a live image can be checked
by running the rebuild.sh script twice. The resulting ISO files should
be identical.

Currently it's only supported in the chroot/binary phases. Omitting
bootstrap was an oversight.

Note that config/archives/*.conf are assumed to be apt.conf files,
so the apt_auth files are required to end with .auth and will be renamed
to .conf when copied into the chroot.

Ensure that /etc/hosts and /etc/hostname have safe permissions and the right
ownership when copied from include directory.

Gbp-Dch: Ignore