Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Let's use lowercase for them, since we will use uppercase for
anchors as is already the case in channels.yaml and sources.yaml.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

No need to compute delta for this branch since we now focus on v2025pre.
Moreover, v2025dev3 will be released and therefore frozen soon.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Running the dashboard locally leaves a folder
"__pycache__" that we want to ignore.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

packaging-updates-upstream-linux: also check for mainline updates if Apertis kernel >= Debian kernel

We should also check for kernel.org updates when Debian provides
kernel of a series since Debian can stop tracking a series that
we still use in Apertis.

Currently, Debian has stopped providing linux 6.6.x, so Apertis
is ahead of Debian by using linux from kernel.org, in this case
we cannot rely on Debian for 6.6.x updates then we have to track
directly kernel.org.

This change fixes a bug that was never noticed before, because
the main users of the dashboard are baseline maintainers who
are usually different than our kernel maintainer.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Otherwise tags from the series 6.10 will also be
fetched for the series 6.1, which is not expected
since we want to stay on the same series.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Using "git" to define "kernel.org" is confusing here since
it could be salsa git, apertis git, etc.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

This allows to quickly run trigger-* jobs without waiting for
the dashboard to be built (which takes a while).

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Since bullseye-backports is going to close, we now
track bookworm for v2023 which still provides 6.1.x.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

To make it less austere

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Updates from backports, testing or unstable are made on
a case-by-case basis, and should be triggered automatically.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Late 2021, dashboard's reports gained their own format. See
c0c77cb6


Since then, trigger-updates was not compatible anymore.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Otherwise, it returns an 404 error.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

buster is no longer tracked, and currently only debian/bullseye-backports
is used.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Dylan Aïssi authored 8 months ago and Walter Lozano committed 8 months ago

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Initial versions of these packages were uploaded with an incorrect
packaging revision. The new uploads have a correct version, but git
still has the old and wrong tags which confuses the dashboard.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

This makes it easier to check the Debian's package status.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

The delta entry required the branch as first level to store data.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Dylan Aïssi authored 1 year ago and Walter Lozano committed 11 months ago

Packages versions coming from Debian are correctly parsed, so we don't have to
whitelist them, however in Apertis we use the ~v202X suffix which is to
misinterpreted by dashboard and lead to confusion when comparing versions.
For example, the dashboard the of downstream complains about:

Version in apertis/v2023/5.2.5~ds0-1+apertis0 is higher than version 5.2.5~ds0-1+apertis0~v2023 in upstream apertis/v2023

Which is true, but due to our workflow, the version apertis/v2023/5.2.5~ds0-1+apertis0
should not land in v2023 this is the reason of why we add the problematic
suffix allowing us to backport targeted changes to a previous release.
Adding the logic in the dashboard to correctly interpret the ~v202X is
not trivial, so for now we can teach it to ignore some versions.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>