1. 07 Oct, 2021 2 commits
  2. 14 Sep, 2021 2 commits
    • Ritesh Raj Sarraf's avatar
    • Ritesh Raj Sarraf's avatar
      Add Priority: optional to package · 4966b063
      Ritesh Raj Sarraf authored
      
      
      Without it, other tools fall apart, like:
      
      ```
      Sep 14 11:53:57 niobium bs_publish[6672]: .changes put in a distribution not listed within it!
      Sep 14 11:53:57 niobium bs_publish[6672]: Ignoring as --ignore=wrongdistribution given.
      Sep 14 11:53:57 niobium bs_publish[6672]: No priority specified for '/srv/obs/repos/apertis:/v2022dev3:/sdk/default/x86_64/apertis-flatdeb_0.2021.1bv2022dev3b3_amd64.changes'!
      ```
      
      Never the less, per Debian Policy too, this is a must have attribute
      
      ```
      Each package must have a priority value, which is set in the metadata for the Debian archive and is also included in the package’s control files (see Priority). This information is used to control which packages are included in standard or minimal Debian installations.
      ```
      Signed-off-by: Ritesh Raj Sarraf's avatarRitesh Raj Sarraf <ritesh.sarraf@collabora.com>
      4966b063
  3. 17 Jun, 2021 2 commits
  4. 13 Apr, 2021 2 commits
  5. 12 Jan, 2021 3 commits
  6. 25 Nov, 2020 4 commits
  7. 24 Nov, 2020 2 commits
  8. 02 Jul, 2020 2 commits
  9. 23 Mar, 2020 3 commits
  10. 06 Mar, 2020 1 commit
  11. 05 Mar, 2020 1 commit
  12. 02 Mar, 2020 2 commits
  13. 28 Feb, 2020 1 commit
  14. 26 Feb, 2020 2 commits
  15. 10 Feb, 2020 3 commits
  16. 28 Jan, 2020 3 commits
    • Frederic Danis's avatar
      Fix systemd-nspawn error when running in gitlab CI · ca23a6af
      Frederic 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: Frederic Danis's avatarFrédéric Danis <frederic.danis@collabora.com>
      ca23a6af
    • Frederic Danis's avatar
      Fix systemd-nspawn error when running in gitlab CI · b6ad8d9c
      Frederic 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: Frederic Danis's avatarFrédéric Danis <frederic.danis@collabora.com>
      b6ad8d9c
    • Frederic Danis's avatar
      apps: Allow to use remote repository for runtime · a446d60e
      Frederic Danis authored
      
      
      The remote-url allows to set a remote url instead of a local directory
      to use for Platform and SDK runtime.
      Signed-off-by: Frederic Danis's avatarFrédéric Danis <frederic.danis@collabora.com>
      a446d60e
  17. 27 Jan, 2020 3 commits
  18. 24 Jan, 2020 2 commits