(mirror of https://github.com/vyos/vyos-live-build.git) https://git.amelek.net/vyos/vyos-live-build.git/atom?h=cla 2021-02-16T20:22:12+00:00 2021-02-16T20:22:12+00:00 Roland Clobus rclobus@rclobus.nl 2021-02-16T17:23:04+00:00 urn:sha1:2c7c90487addb7f741be24418b5ae1caed51f562 Use the hexadecimal version of SOURCE_DATE_EPOCH, limited to the lower 32 bits 2021-01-15T09:22:29+00:00 Roland Clobus rclobus@rclobus.nl 2021-01-02T16:40:55+00:00 urn:sha1:15fab34ea2e154cee5e6d53da7f5c80b300ca77f 2021-01-15T09:22:29+00:00 Roland Clobus rclobus@rclobus.nl 2020-10-04T11:55:12+00:00 urn:sha1:2b0559fd110fa5a1a3e997b064d15f8e67d8fe60 2021-01-01T16:51:02+00:00 Roland Clobus rclobus@rclobus.nl 2021-01-01T16:51:02+00:00 urn:sha1:037e93fe37f8b5d974e3e6219fa6ee94ad5cf504 2020-10-12T12:41:58+00:00 Marcel Partap mpartap@gmx.net 2020-06-22T15:24:31+00:00 urn:sha1:ce39f3e507a8d03b1c986c400d797f13f82ae9d5 avoids spitting out warning > [2020-06-07 22:30:32] lb binary_grub-efi > P: Begin preparing Grub based EFI support... > Reading package lists... > Building dependency tree... > Reading state information... > Package grub-efi-amd64-signed is not available, but is referred to by another package. > This may mean that the package is missing, has been obsoleted, or > is only available from another source > > E: Package 'grub-efi-amd64-signed' has no installation candidate > W: UEFI Secure Boot disabled due to missing signed Grub/Shim. 2020-05-05T18:55:28+00:00 Lyndon Brown jnqnfe@gmail.com 2020-05-05T15:45:57+00:00 urn:sha1:18eefdd6f38631e15e56a2bd7a25bba50b05acfa it removes one or more, so should be plural for clarity Gbp-Dch: Short 2020-05-05T18:55:28+00:00 Lyndon Brown jnqnfe@gmail.com 2020-05-05T15:42:44+00:00 urn:sha1:919a464b64b4bda52a56b8732ea5ef7727649cf0 it installs one or more, so should be plural for clarity Gbp-Dch: Short 2020-05-04T21:15:09+00:00 Lyndon Brown jnqnfe@gmail.com 2020-05-04T17:20:02+00:00 urn:sha1:a542d52141acef0e2d2bb78253d6b5df4305dcd1 when loopback support was introduced, it initially duplicated the code for generating a grub2 config, before the duplicated code was removed from the grub-pc script, effectively thus moving grub config generation to the loopback feature script. grub-efi support was added after this. this results in a misleading filename, since the `binary_loopback_cfg` script is essential for use of grub-pc|grub-efi, and actually only has a single line of code on top that's needed for adding actual loopback support on top. (when grub-pc and grub-efi are not used, the entire script is still needed for loopback support to work). so here we rename it to make better sense, and correct/clarify bits of documentation. Gbp-Dch: Short 2020-05-04T20:40:13+00:00 Lyndon Brown jnqnfe@gmail.com 2020-05-04T15:12:45+00:00 urn:sha1:d7883ec32b2bb907fce17fb759c08c5cd9851fc3 the design choice from when EFI support was introduced was to change `--bootloader` to `--bootloaders`, with users specifying their selection of BIOS and EFI bootloaders together. at this time there were not even any decent validation checks being performed, and invalid combinations could cause some chaos. since then proper validation was put in place, including checking that only a single instance of each of BIOS and EFI bootloaders exists in the selection. here we tweak things such that we stick with the same option, but we split the selection up such that we store the BIOS and EFI selections separately within the saved config file, and offer it up to scripts to help simplify those scripts. we must however retain support for splitting from the combined option, both because we still use it in the combined option, and for backwards compatibility with older saved configs. Gbp-Dch: Short 2020-05-04T20:40:13+00:00 Lyndon Brown jnqnfe@gmail.com 2020-05-04T13:28:37+00:00 urn:sha1:3f840aeeba982a858a881271a3bb48bca5b50dd8 thus far, config bootloader validation only did the basic check that each bootloader specified was a known and supported bootloader, it did not check combinations. it now checks combinations, and strips out the previous "bootloader role" stuff. the no-bootloaders warning is duplicated, covering two slightly different situations (empty string, and whitespace string). this is anticipated to be just temporary, with this just being the first step in better handling bootloader selections. Gbp-Dch: Short