1. 12 Dec, 2022 1 commit
  2. 08 Dec, 2022 1 commit
  3. 10 Nov, 2022 1 commit
  4. 18 Oct, 2022 1 commit
  5. 26 Sep, 2022 1 commit
  6. 22 Aug, 2022 1 commit
  7. 18 Aug, 2022 1 commit
  8. 17 Aug, 2022 1 commit
  9. 24 Jun, 2022 2 commits
    • Sjoerd Simons's avatar
      c201aa35
    • Ariel D'Alessandro's avatar
      aptly: Don't re-publish repositories on project updates · 7f373e09
      Ariel D'Alessandro authored
      
      
      Aptly is currently re-publishing (dropping and publishing again)
      repositories when the project configuration is changed. This is
      performed to update the components and architectures of the published
      distribution based on the updated project configuration.
      
      OBS/aptly contains a hack allowing the usage of slashes `/` in the
      publish distribution field, which we're currently using to have the
      snapshots published in the same prefix and using a distribution name
      with the form: `$release/snapshots/$timestamp`. This makes the snapshots
      folder to be inside the same `dists` directory where the repositories
      are published.
      
      There's a bug in the above implementation, where:
      * OBS project configuration is updated, triggering a re-publishing of
        the distribution.
      * Aptly drops the published distribution.
      * If aptly doesn't have any other distribution published in the same
        prefix, it will remove the entire `dists` folder, with all the
        snapshots in it.
      * Aptly publishes the distribution again.
      
      This bug is making aptly to drop all the snapshots, as it assumes these
      can't be stored within the published distribution.
      
      Let's HACK this quickly by disabling the re-publishing temporarily. Note
      that OBS will create the aptly repositories and publish them on the
      first project configuration, but it won't re-publish it at all on
      further config updates.
      
      Signed-off-by: Ariel D'Alessandro's avatarAriel D'Alessandro <ariel.dalessandro@collabora.com>
      7f373e09
  10. 23 Jun, 2022 1 commit
  11. 22 Jun, 2022 1 commit
  12. 17 Jun, 2022 3 commits
  13. 16 Jun, 2022 3 commits
  14. 15 Jun, 2022 1 commit
  15. 13 Jun, 2022 1 commit
  16. 10 Jun, 2022 1 commit
  17. 08 Jun, 2022 1 commit
  18. 27 May, 2022 2 commits
  19. 16 May, 2022 11 commits
  20. 12 May, 2022 5 commits