1. 01 Jun, 2022 2 commits
  2. 19 May, 2022 1 commit
  3. 31 Mar, 2022 1 commit
    • Ryan Gonzalez's avatar
      Install copyright_report files · cb5b8ea5
      Ryan Gonzalez authored
      Documentation files are excluded from installations made to the Docker
      images, with a few exceptions to this rule, including `copyright` files.
      This extends it to also include `copyright_report` files, as they are
      useful to have installed for the purpose of being able to examine
      dependencies' reports while building packages.
      As the files are all plain text and shorter than the corresponding
      `copyright` file (as they omit the full license text), the effect on the
      built image sizes should be negligible.
      Signed-off-by: Ryan Gonzalez's avatarRyan Gonzalez <ryan.gonzalez@collabora.com>
  4. 11 Mar, 2022 1 commit
  5. 28 Jan, 2022 3 commits
  6. 31 Dec, 2021 1 commit
  7. 15 Dec, 2021 1 commit
  8. 24 Nov, 2021 1 commit
  9. 23 Nov, 2021 1 commit
  10. 22 Nov, 2021 1 commit
  11. 15 Nov, 2021 1 commit
  12. 14 Nov, 2021 1 commit
  13. 15 Oct, 2021 4 commits
  14. 11 Oct, 2021 1 commit
  15. 04 Oct, 2021 1 commit
  16. 15 Sep, 2021 1 commit
  17. 31 Aug, 2021 1 commit
    • Walter Lozano's avatar
      Use simple yml style · f874bb69
      Walter Lozano authored and Emanuele Aina's avatar Emanuele Aina committed
      In order to avoid issues with scan-copyrights not dealing with !!bool in
      yaml files, switch to a simpler format.
      This kind of issue was seen in packages that ship their own configuration
      in d/fill.copyright.blanks.yml, and uses the skip (boolean) option,
      which triggers an error an prevents the pipeline to succeed.
      As the issue seems to be an upstream bug, as a workaround change the
      default_style used by yaml dumper from | to the default one, which
      does not add !!bool.
      Previously the default_style | was needed as scan-copyright used
      YAML::Tiny and it was not able to parse the files properly, however,
      after switching to YAML::XS this doesn't seem to be an issue any more,
      so default_style can be used with its default.
      Signed-off-by: Walter Lozano's avatarWalter Lozano <walter.lozano@collabora.com>
  18. 23 Aug, 2021 1 commit
  19. 18 Aug, 2021 1 commit
  20. 30 Jul, 2021 1 commit
  21. 26 Jul, 2021 1 commit
    • Emanuele Aina's avatar
      pkg-merge-upstream-to-downstreams: Python 3.7 (v2021) compatibility · 00290d35
      Emanuele Aina authored
      Try to be compatible tiwh Python 3.7 as shipped in Buster so the tool
      can work on projects where the default branch points to v2021, either
      because it's been dropped from v2022 or because it's a downstream that
      has not started mirroring v2022 yet.
            File "/usr/bin/apertis-pkg-merge-upstream-to-downstreams", line 65, in ensure_downstream_branch
              project_id = urllib.parse.quote(url.path.strip("/").removesuffix(".git"), safe="")
          AttributeError: 'str' object has no attribute 'removesuffix'
      Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
  22. 22 Jul, 2021 4 commits
  23. 14 Jul, 2021 1 commit
  24. 13 Jul, 2021 2 commits
    • Emanuele Aina's avatar
      pkg-merge-upstream-to-downstreams: Ensure the target branch exist · 86604333
      Emanuele Aina authored
      When pulling an update for a stable branch it should target a `-updates`
      or `-security` branch. However there's no guarantee that they exist, so
      the creaton of the merge may fail:
          remote:              WARNINGS: Error encountered with push options
          remote:       'merge_request.create' 'merge_request.remove_source_branch'
          remote:              'merge_request.target=apertis/v2021-security'
          remote:       'merge_request.title=Update from debian/buster-security for
          remote:     apertis/v2021-security': Branch apertis/v2021-security does not
          remote:                                  exist
      To avoid that, ensure to push the target branch before creating the MR.
      Unfortunately we can't simply use `git push` as the creation of
      protected branches is restricted to the Web UI and the API, so let's use
      the latter, even if it requires a bit of juggling.
      Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
    • Emanuele Aina's avatar
      pkg-merge-upstream-to-downstreams: Flush before suprocesses · f863f4ae
      Emanuele Aina authored
      To ensure the correct ordering of the output, flush stdout before
      launching suprocesses.
      This prevents the output of `apertis-pkg-merge-upstream-to-downstreams`
      from being printed much after the output of the suprocess when not
      running on a tty, like when piped to `less` or when being run in the CI.
      While it would be normally expected that the output of the merge follows
      the `Attempt merging` message, in practice it would be displayed
      immediately as it came from a suprocess, while the output of the program
      would be buffered until much later.
      Add some flushes to correctly handover the output buffering.
      Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
  25. 23 Jun, 2021 2 commits
  26. 18 Jun, 2021 2 commits
  27. 08 Jun, 2021 1 commit
  28. 07 Jun, 2021 1 commit