Skip to content
  1. Apr 17, 2018
  2. Apr 11, 2018
  3. Apr 10, 2018
    • Luca Boccassi's avatar
      Reconfigure bootstrapped packages after preseeding. · 277f0cec
      Luca Boccassi authored
      live-build supports preseeding configuration, but the configuration has
      to be installed after bootstrapping since it needs the debconf tools to
      be applied. But packages that have already been installed and configured
      in the bootstrap step will then ignore those preseeded configs.
      
      After applying each preseed file, parse the package list and manually
      reconfigure the relevant package(s) so that the configuration will be
      applied.
      277f0cec
    • Luca Boccassi's avatar
      Don't recommend gzip, it's essential · da011939
      Luca Boccassi authored
      Fixes Lintian Error.
      
      Gbp-Dch: Ignore
      da011939
  4. Apr 05, 2018
  5. Apr 04, 2018
  6. Mar 28, 2018
  7. Mar 23, 2018
    • Luca Boccassi's avatar
      ONIE: detect initrd compression instead of hard-coding · c1948b41
      Luca Boccassi authored
      Instead of hard-coding the decompression and compression formats,
      detect them at runtime.
      Install the required dependencies as well - they were mistakenly left
      out.
      
      Gbp-Dch: Ignore
      c1948b41
    • Luca Boccassi's avatar
      Add Acquire::AllowInsecureRepositories to fix apt-secure in sid · 0e91aeea
      Luca Boccassi authored
      The apt-secure option does not work anymore when building a sid image,
      as with apt 1.6 the existing options are no longer enough to get apt
      to accept an unsigned repository, which is necessary when using a
      local cached repository (offline build).
      
      Pass Acquire::AllowInsecureRepositories "true"; together with the
      other options when --apt-secure false is used to fix the issue.
      0e91aeea
  8. Mar 22, 2018
  9. Mar 09, 2018
    • Luca Boccassi's avatar
      UEFI: use uppercase EFI directory name for Tianocore · aa1ae838
      Luca Boccassi authored
      The Tianocore reference UEFI implementation, used for example by Qemu,
      wants the EFI directory name to be uppercase in the fat32 partition
      when Secure Boot is enabled, and will fail to load otherwise.
      aa1ae838
    • Luca Boccassi's avatar
      UEFI: add support for Secure Boot on amd64 and arm64 · 035518ff
      Luca Boccassi authored
      Support for UEFI Secure Boot is modelled after how it currently works
      in Ubuntu and on how it is going to work on Debian.
      A minimal bootloader, shim, is used as the first-stage and it then
      loads grub. Both have to be signed.
      shim-signed is already available in Debian so the filenames are
      already established, and the grub2 repository and packaging is common
      between the 2 distros so we can already be reasonably sure of what it
      is going to be.
      So if both are available, copy /usr/lib/shim/shim[x64|aa64].efi.signed
      as boot[x64|aa64].efi so that UEFI loads it first, and copy
      /usr/lib/grub/[x86_64|arm64]-efi-signed/grub[x64|aa64].efi.signed as
      grub[x64|aa64].efi.
      This grub2 EFI monolithic image is currently hard-coded in grub2's
      repository to look for a config file in efi/debian, so make a copy
      of the previously added minimal grub.cfg that loads the real one in
      that directory in both the fat32 and ISO 9660 partitions.
      
      The new option --uefi-secure-boot can be set to auto (default,
      enable or disable.
      In auto, the lack of the signed EFI binaries is intentionally left as a
      soft failure - live-build will simply fallback to using the locally
      generated non-signed grub2 monolithic EFI binary as the only
      bootloader. Given the difficulties surrounding the Secure Boot
      signing infrastructure this approach gives the most flexibility and
      makes sure things will "just work" once the packages are available,
      without the need to change anything in the configuration.
      This will also greatly help downstream distributions and users who
      want to do self-signing.
      The enable or disable options work as expected.
      
      Closes: #821084
      035518ff
    • Luca Boccassi's avatar
      UEFI: add minimal grub.cfg to fat32 partition · ac3ed236
      Luca Boccassi authored
      On some UEFI implementations, like the AMI found in the Supermicro
      X10SDV-TP8F development board, the fat32 partition will be loaded
      first and so Grub will set it the root, and then drop to the console
      as it cannot find any config on it.
      Add a minimal grub.cfg that allows Grub to find the main config on
      the ISO 9660 partition and load it.
      Closes: #892406
      ac3ed236
  10. Mar 02, 2018
  11. Feb 24, 2018
  12. Feb 23, 2018
    • Raphaël Hertzog's avatar
      Merge branch 'fix_offline_repo' into 'master' · ee8d06c4
      Raphaël Hertzog authored
      Fix build with local offline mirrors
      
      See merge request live-team/live-build!1
      ee8d06c4
    • Luca Boccassi's avatar
      Fix build with local offline mirrors · 9a0c6102
      Luca Boccassi authored
      Commit a15b5796 (#775989) dropped an early exit from the
      chroot_archives remove step in case the parent mirror chroot and binary
      parameters are the same and introduced a regression, as with the
      following live-build now fails when the parent mirror is using a file:/
      local apt repository (for example when the build worker is offline and
      uses a pre-built cache of packages).
      
      Example config:
      
        lb config --mirror-bootstrap "file:/pkgs" \
          --mirror-chroot "file:/pkgs/" \
          --mirror-binary "file:/pkgs" \
          --parent-mirror-bootstrap "file:/pkgs" \
          --parent-mirror-chroot "file:/pkgs/" \
          --parent-mirror-binary "file:/pkgs" \
          ...
      
      with /pkgs being a directory with the packages for the installation and
      the apt metadata (Packages/Sources/Release).
      
      The problem is that, with such a setup, the /pkgs directory is bind
      mounted inside the chroot as an optimisation in the install step,
      and umounted as one of the first actions in the remove step for
      chroot_archives.
      
      Before that fix, the script terminated immediately. But now it
      progresses and at the end it tries to run apt update inside the chroot
      which will fail since the repository directory has been umounted, and
      thus the packages and the apt metadata are no longer available, while
      still being listed in /etc/apt/sources.list.
      
      The proposed solution is to umount the local directory at the end of
      the remove step, rather than at the beginning.
      
      Closes: #891206
      9a0c6102
  13. Feb 14, 2018
  14. Feb 09, 2018
  15. Dec 21, 2017
  16. Dec 07, 2017
  17. Nov 20, 2017
  18. Sep 20, 2017
  19. Sep 18, 2017
Loading