vyos-live-build.git/scripts/build/binary_iso, branch cla (mirror of https://github.com/vyos/vyos-live-build.git)
https://git.amelek.net/vyos/vyos-live-build.git/atom?h=cla2021-02-14T21:38:19+00:00Fix build on architecture without syslinux2021-02-14T21:38:19+00:00Luca Boccassibluca@debian.org2021-02-14T21:37:35+00:00urn:sha1:b968e2c0f7625f679bbbe6db12feb30f4b7f3598
Don't run xorriso with -isohybrid-mbr if LB_BOOTLOADER_BIOS is
not set to syslinux
Closes: #982746
Apply SOURCE_DATE_EPOCH to newly generated files and create a log2021-01-15T09:22:29+00:00Roland Clobusrclobus@rclobus.nl2021-01-02T16:41:50+00:00urn:sha1:91e1e65c873291d11495730d8ce6df5940706c2bSOURCE_DATE_EPOCH is always set2021-01-15T09:22:29+00:00Roland Clobusrclobus@rclobus.nl2020-10-04T11:49:06+00:00urn:sha1:9d2405166970c02b978cef817dd15c9cec9ed615Delay resolving the timestamp for the ISO volume to the moment the ISO-image is created2020-12-13T20:33:24+00:00Roland Clobusrclobus@rclobus.nl2020-12-13T17:33:54+00:00urn:sha1:3f7dd00fcb83177e679e9f1449200dee11dc1531Bugfix: use minutes instead of month in the time of the modification date field2020-12-07T07:36:42+00:00Roland Clobusrclobus@rclobus.nl2020-12-07T07:36:42+00:00urn:sha1:4eae44d13da639fcb9a23bf660c2a58e6a3466a4binary_iso: Execute mkdir binary/.disk before writing to it2020-11-24T11:24:14+00:00Matthijs Kooijmanmatthijs@stdin.nl2020-11-24T11:16:16+00:00urn:sha1:e772dfd6d2849892ec03f611f621336676cf8b2b
Before commit 9f3e5fe8d (Fix the way the .disk/mkisofs file is created)
all these commands (`mkdir`, write to `binary/.disk/mkisofs` and
`xorriso`) were in the same `binary.sh` script. Since that commit, the
write was extracted, to prevent issues with quoting, but the related
mkdir was left in `binary.sh`. This means that the write is now executed
first, and the `mkdir` only afterwards, making the `mkdir` quite pointless.
In practice, this did not break becaue binary_disk also does the same
`mkdir` and runs before `binary_iso`, but if one runs commands manually
and skips `binary_iso`, then this does break.
Even though this is not really a supported usecase, just move the mkdir
outside of `binary.sh`, so it runs *before* the write again as intended.
s/Remove_package/Remove_packages/2020-05-05T18:55:28+00:00Lyndon Brownjnqnfe@gmail.com2020-05-05T15:45:57+00:00urn:sha1:18eefdd6f38631e15e56a2bd7a25bba50b05acfa
it removes one or more, so should be plural for clarity
Gbp-Dch: Short
s/Install_package/Install_packages/2020-05-05T18:55:28+00:00Lyndon Brownjnqnfe@gmail.com2020-05-05T15:42:44+00:00urn:sha1:919a464b64b4bda52a56b8732ea5ef7727649cf0
it installs one or more, so should be plural for clarity
Gbp-Dch: Short
binary_iso: properly handle multiple bootloaders2020-05-04T20:48:03+00:00Lyndon Brownjnqnfe@gmail.com2020-05-04T16:28:48+00:00urn:sha1:3a523c3fc12ef23e720020e2bad151fc91b8b35d
with LB_BOOTLOADER_BIOS and LB_BOOTLOADER_EFI introduced, we can simplify
and correct things here.
previously it was possible for more than one of each type to be added.
Gbp-Dch: Short
config: fix stale live-build version in iso-preparer2020-05-03T22:20:39+00:00Lyndon Brownjnqnfe@gmail.com2020-05-03T17:02:04+00:00urn:sha1:9bc35759aab95d849cba38bcb6fd1bb072df9907
using `$VERSION` as part of the default `$LB_ISO_PREPARER` means that when
you simply run `lb config` once, this variable is stored as a part of the
string, and replaced on use, but if you run `lb config` twice, it gets
replaced with a fixed version, that is then used in all subsequent builds.
let's replace with a placeholder (`@LB_VERSION@`) that can be used both in
the default, or in user strings, and will be replaced on use only.
this means that subsequent builds will always reflect the actual version
of live-build used.
Gbp-Dch: Ignore