[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[Git][ftp-team/dak][deploy] 10 commits: Always run CD push then follow with a normal one, if a push is wanted



Title: GitLab

Joerg Jaspert pushed to branch deploy at Debian FTP Team / dak

Commits:

  • db44aca1
    by Joerg Jaspert at 2025-11-15T11:56:48+01:00
    Always run CD push then follow with a normal one, if a push is wanted
    
  • 875cfc2b
    by Jochen Sprickerhof at 2025-11-16T21:33:17+00:00
    backports-conf: throw away binaries after NEW
    
    Same as b717942d.
    
  • bffbeeed
    by Joerg Jaspert at 2025-11-16T21:49:56+00:00
    Merge branch 'drop_backports_new' into 'master'
    
    backports-conf: throw away binaries after NEW
    
    See merge request ftp-team/dak!295
  • e95c00b5
    by Matthias Klumpp at 2025-11-16T21:51:32+00:00
    dep11: Correctly validate translated keys in YAML files
    
    Not sure why this worked before, but it seems to be failing now...
    According to the voluptuous documentation, this is the correct way to
    declare the expected schema.
    
  • afa0b4da
    by Joerg Jaspert at 2025-11-16T21:52:11+00:00
    Merge branch 'master' into 'master'
    
    dep11: Correctly validate translated keys in YAML files
    
    See merge request ftp-team/dak!297
  • 49eefa7f
    by Ivo De Decker at 2025-11-16T21:55:17+00:00
    dak/dominate.py: keep binaries for at least 1 day
    
    Don't remove binaries that have been in the archive for less than 1 day.
    
    When multiple version of the same binary are uploaded without a dinstall
    between them, the older versions are never published to the ftp-master archive.
    They are only published in the buildd archive. This means they aren't available
    in shapshot.debian.org either. Some of these binaries show up in buildinfo
    files of other uploads, making it impossible to reproduce the binaries from
    those uploads.
    
    This change keeps all binaries around for at least a day, to allow them to be
    published in the ftp-master archive and show up on snapshot.debian.org.
    
    This does not happen for suites with build queues:
    - avoid changing the behavior of dak dominate for (old)stable
    - binaries from these suites enter the archive via suites with build queues
      anyway
    
    Closes: #1096129
    
  • 9f1009f7
    by Ivo De Decker at 2025-11-16T21:55:17+00:00
    Tests: add function to shift the psql 'now()' forward.
    
    This can be used to test functionality that is only triggered after a certain
    time has passed.
    
  • d14aa674
    by Ivo De Decker at 2025-11-16T21:55:17+00:00
    Update testsuite for change in dak/dominate.py
    
    dak/dominate.py: keep binaries for at least 1 day
    
    Actually test this change in test 2000-dinstall. The other tests were updated
    to shift the sql time where necessary to get the same result as before.
    
  • df29a241
    by Joerg Jaspert at 2025-11-16T22:00:30+00:00
    Merge branch 'dominate-1day' into 'master'
    
    dak/dominate.py: keep binaries for at least 1 day
    
    See merge request ftp-team/dak!298
  • 6fe7429e
    by Joerg Jaspert at 2025-11-17T22:33:17+01:00
    Merge branch 'master' into deploy
    
    * master:
      Update testsuite for change in dak/dominate.py
      Tests: add function to shift the psql 'now()' forward.
      dak/dominate.py: keep binaries for at least 1 day
      dep11: Correctly validate translated keys in YAML files
      backports-conf: throw away binaries after NEW
      Always run CD push then follow with a normal one, if a push is wanted
    

33 changed files:

The diff was not included because it is too large.

Reply to: