v2026dev0 was released three weeks ago, so according to
our policy it's time to drop it completely, see:
https://www.apertis.org/guides/maintenance/apertis_release_process/#dashboard-update



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>

Delta compution is resource-intensive. Thus, we have to select
on which Apertis releases to run it.

For now, we run it only on the last stable release (v2025)
and on the last development channel (v2026dev1).

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

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

The dashboard needs the real source name of the package and
not the repository name.

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

The dashboard needs the real source name of the package and
not the repository name.

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

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

v2024 is still used but since packaging-check-delta requires many
ressources, we need to restrict branches on which it runs otherwise
the job packaging-check-delta reaches its timeout and the dashboard
is no longer updated.

So let's keep the last two apertis streams (v2025 and v2026)
until packaging-check-delta is improved to avoid timeouts.

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

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

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

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

Already defined and inherited from v2023.

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

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

v2025dev3 was marked as closed two weeks ago, so according to
our policy it's time to drop it completely, see:
https://www.apertis.org/guides/maintenance/apertis_release_process/#dashboard-update



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

Apertis v2025dev3 was released:
- https://www.apertis.org/release/v2025/v2025dev3/releasenotes/



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

The file was moved when the repository was reorganized.
See:
apertis-infrastructure@41fed1b1



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>

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>