vcswatch reports that
this package seems to have new commits in its VCS but has
not yet updated debian/changelog. You should consider updating
the Debian changelog and uploading this new version into the archive.
Here are the relevant commit logs:
commit 27b4226549f1db6b247f5cd491ea3aba3137cb34
Merge: 4cb44568 26cbbbe5
Author: Antonio Terceiro <terceiro@debian.org>
Date: Wed Apr 19 18:08:53 2023 +0000
Merge branch 'rm-obsolete-code' into 'master'
Drop obsolete scripts and mentions to them
See merge request ci-team/debci!246
commit 26cbbbe5b927e6ec7f458a62e4f95296d4a51f01
Author: Antonio Terceiro <terceiro@debian.org>
Date: Wed Apr 19 14:38:39 2023 -0300
Drop obsolete scripts and mentions to them
Since debci-batch has been removed in favor of external scheduling of
tests, some infrastructure left behind is not really useful anymore.
Right now, drop debci-list-dependencies, debci-list-packages,
debci-setup-chdist and references to them (which are unused anyway).
Gbp-Dch: full
commit 4cb44568812ec1abff83123883017f34ca6d784d
Author: Antonio Terceiro <terceiro@debian.org>
Date: Sat Apr 15 12:54:40 2023 -0300
spec_helper: bump required test coverage to 92%
commit ec91c2b882a73e7c5879f1cbfb41dc429b55fd85
Author: Antonio Terceiro <terceiro@debian.org>
Date: Sat Apr 15 12:41:21 2023 -0300
self_service: allow multiple API keys and add to manage them
commit 29a0e2b345801d541789d24d4e969b2ee98fc0db
Author: Antonio Terceiro <terceiro@debian.org>
Date: Mon Mar 13 16:30:10 2023 -0300
debci-generate-apt-sources: fix checks for non-free-firmware for suite codenames
It was only working correctly for the suites in use in ci.debian.net,
e.g. unstable, testing, stable etc. When given a suite codename (e.g.
bullseye, stretch) it would produce the correct response.
commit 691fe69c8954fd14e7c453a0c9655ba6eb6357c8
Merge: de2cabce 047a0fb6
Author: Antonio Terceiro <terceiro@debian.org>
Date: Sat Mar 11 20:14:18 2023 +0000
Merge branch 'consistent-logging' into 'master'
Make logging for all daemons consistent
See merge request ci-team/debci!244
commit 047a0fb67fbdd2651f5f1d1c6909995af161dc97
Author: Antonio Terceiro <terceiro@debian.org>
Date: Sat Mar 11 16:44:10 2023 -0300
debci-worker, debci-publisher: log errors even in quiet mode
commit 105032056e6ff8fe752114dba6ada5c02f827387
Author: Antonio Terceiro <terceiro@debian.org>
Date: Sat Mar 11 16:36:44 2023 -0300
Make logging for all daemons consistent
All daemons will now report using the same format:
$package $suite/$architecture/$backend ($run_id) $status [$duration]
This should make it easier to correlate logs from daemons that run on
different hosts.
commit f9d297f82c3ce5f81475c155aa143700003c8350
Author: Antonio Terceiro <terceiro@debian.org>
Date: Sat Mar 11 16:33:37 2023 -0300
Debci::Job: store and report backend
Report default backend if the database field is empty, to be backwards
compatible with jobs created before this was introduced.
commit de2cabce65d9afb552ea7f1ddc33546cf30c6981
Author: Antonio Terceiro <terceiro@debian.org>
Date: Sun Mar 5 20:57:37 2023 -0300
Split publishing of results into a separate daemon
We have been having reliability issues on s390x and ppc64el, and some
evidence that points to the publishing of results. By separating running
jobs from publishing their results, this should ease debugging
connectivity issues, while keeping the results around so that they can
be published later when the issue is solved.
The protocol between the worker and the publisher is very simple: the
worker will copy the results tarball in the designated results dir, and
after that will create a matching stamp file. The publisher waits for
events on stamp files, and tries to publish the corresponding results
file.
The publisher will try publishing at most 3 times, with a delay of 5
seconds between each attempt. On failure, the publisher will try again
later (e.g. when new results arrive).
Another property of this new design is that regardless of how many
workers a host is running, there will be a single process actually
pushing the results back to the master.