Skip to content
Snippets Groups Projects
  1. Jul 02, 2020
    • Ludovico de Nittis's avatar
      Add support to install additional packages to the base chroot · 5ca647e9
      Ludovico de Nittis authored
      
      This gives us a way to drop in configuration changes (in particular apt
      pinning preferences) as soon as possible after the debootstrap run,
      allowing non-default pinning to be used to install the extra packages
      for the Platform and SDK.
      
      Please note that `$keyringpackage`, and the automatic installation of
      `apt-transport-https`, have been removed because this new option can be
      considered a generalization of both of them.
      So if your suite needs `apt-transport-https`, or if you were using
      `$keyringpackage`, list the needed packages with the
      `additional_base_packages` option instead.
      
      Signed-off-by: default avatarLudovico de Nittis <ludovico.denittis@collabora.com>
      5ca647e9
  2. Mar 23, 2020
  3. Mar 05, 2020
  4. Mar 02, 2020
  5. Feb 28, 2020
  6. Feb 26, 2020
  7. Feb 10, 2020
  8. Jan 28, 2020
    • Frédéric Danis's avatar
      Fix systemd-nspawn error when running in gitlab CI · ca23a6af
      Frédéric Danis authored
      
      When running in gitlab CI with docker the following error may occur:
       Failed to register machine: Unit machine-root.scope already exists.
      
      We only use systemd-nspawn for temporary containers which are not intended
      to be used interactively, so it is not useful for them to be listed by
      machined.
      
      Registering with machined can also be harmful: because our root directory
      is named `root`, if two concurrent flatdeb instances communicate with the
      same machined instance, the second one will try to use the same name as
      the first and so will fail to register, causing flatdeb to fail.
      
      This can be avoided by preventing the systemd-nspawn container from
      registering with machined (which is supported since systemd v209).
      
      Signed-off-by: default avatarFrédéric Danis <frederic.danis@collabora.com>
      ca23a6af
  9. Jan 27, 2020
  10. Jan 24, 2020
  11. Jan 21, 2020
  12. Nov 28, 2019
  13. Nov 25, 2019
  14. Oct 08, 2019
  15. Oct 07, 2019
  16. Oct 03, 2019
    • Simon McVittie's avatar
      Automatically download debug symbols for everything in the Platform · 690b609a
      Simon McVittie authored
      
      This reduces the need to have a giant metapackage with all the shared
      libraries' detached debug symbols; now we only need to do that for
      libraries that are still using legacy debug symbols (foo-dbg).
      
      This also means we tolerate transient uninstallability for debug
      symbols: we'll simply produce a runtime without those debug symbols.
      This is particularly important when taking binaries from
      debian-security, which does not have a corresponding debug symbols
      archive (although when security updates get mirrored into
      proposed-updates, their detached debug symbols do appear there).
      
      Finally, it also means we don't run into problems with version skew
      between debug symbols and the actual libraries, particularly when
      adding buster-proposed-updates-debug (which, in general, will be
      strictly newer than buster + buster-security) in the hope of getting
      detached debug symbols for buster-security.
      
      Signed-off-by: default avatarSimon McVittie <smcv@collabora.com>
      690b609a
  17. Oct 02, 2019
  18. Sep 19, 2019
  19. Aug 22, 2019
Loading