- Jul 18, 2024
-
-
Dylan Aïssi authored
Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
Dylan Aïssi authored
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>
-
- Jul 17, 2024
-
-
Dylan Aïssi authored
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>
-
- Jul 16, 2024
-
-
Dylan Aïssi authored
Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
Dylan Aïssi authored
Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
Dylan Aïssi authored
Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
Dylan Aïssi authored
To make it less austere Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
Dylan Aïssi authored
Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
Dylan Aïssi authored
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>
-
Dylan Aïssi authored
Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
- Jul 12, 2024
-
-
Dylan Aïssi authored
Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
Dylan Aïssi authored
Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
Dylan Aïssi authored
Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
Dylan Aïssi authored
Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
Dylan Aïssi authored
Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
Dylan Aïssi authored
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>
-
Dylan Aïssi authored
Otherwise, it returns an 404 error. Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
- Jul 11, 2024
-
-
Dylan Aïssi authored
Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
Dylan Aïssi authored
buster is no longer tracked, and currently only debian/bullseye-backports is used. Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
- Jul 10, 2024
-
-
Dylan Aïssi authored
Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
Dylan Aïssi authored
Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
Dylan Aïssi authored
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>
-
- Jul 04, 2024
-
-
Dylan Aïssi authored
This makes it easier to check the Debian's package status. Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
- Jul 01, 2024
-
-
Dylan Aïssi authored
The delta entry required the branch as first level to store data. Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
- Jun 28, 2024
-
-
- Jun 17, 2024
-
-
Dylan Aïssi authored
Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
- May 27, 2024
-
-
Dylan Aïssi authored
Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
- Apr 08, 2024
-
-
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>
-
- Apr 04, 2024
-
-
Dylan Aïssi authored
Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
- Mar 27, 2024
-
-
Dylan Aïssi authored
Only packaging data are required in the cache file, that was the previous behavior, but it was mistakenly reverted in 254b71ed. Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
Dylan Aïssi authored
Just after adding apertis/v202*-security and -updates branches to be tracked by the dashboard, the returned version is "None" because the cache file is not yet updated. This "None" value makes the pipeline failing with: Traceback (most recent call last): File "/builds/infrastructure/dashboard/./bin/packaging-updates-upstream-linux", line 209, in <module> results = compute_linux_updates(data) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/builds/infrastructure/dashboard/./bin/packaging-updates-upstream-linux", line 134, in compute_linux_updates process = subprocess.run( ^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/subprocess.py", line 571, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['git', '-c', 'versionsort.suffix=-', 'ls-remote', '--exit-code', '--tags', '--refs', '--sort=version:refname', 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git ', 'vNone*']' returned non-zero exit status 2. To avoid failures, just skip this branch for this iteration. Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
- Mar 25, 2024
-
-
Emanuele Aina authored
If a package only appears on OBS the dashboard fails with an exception: Traceback (most recent call last): File "/builds/-RogsxNE/0/infrastructure/dashboard/./bin/packaging-check-invariants", line 854, in <module> checker.check_git_and_obs_versions(package) File "/builds/-RogsxNE/0/infrastructure/dashboard/./bin/packaging-check-invariants", line 238, in check_git_and_obs_versions if package.git.default_branch: ^^^^^^^^^^^ File "/builds/-RogsxNE/0/infrastructure/dashboard/./bin/packaging-check-invariants", line 79, in __getattr__ item = super(DictWrapper, self).__getitem__(attr) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ KeyError: 'git' Signed-off-by:
Emanuele Aina <emanuele.aina@collabora.com>
-
- Mar 20, 2024
-
-
Dylan Aïssi authored
Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
Dylan Aïssi authored
Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
- Mar 14, 2024
-
-
Dylan Aïssi authored
Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
Dylan Aïssi authored
Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
- Mar 01, 2024
-
-
Dylan Aïssi authored
Sometimes, we need to import and modify packages from Debian. To make the initial review easier, an apertis/v202* branch is created from the debian one, then a merge request is created against it adding debian/apertis/* files. During the review, tha apertis branch doesn't have any debian/apertis/* files and the dashboard fails with: Traceback (most recent call last): File "/builds/infrastructure/dashboard/./bin/packaging-check-invariants", line 857, in <module> checker.check_git_and_obs_versions(package) File "/builds/infrastructure/dashboard/./bin/packaging-check-invariants", line 271, in check_git_and_obs_versions component = branch.component ^^^^^^^^^^^^^^^^ File "/builds/infrastructure/dashboard/./bin/packaging-check-invariants", line 79, in __getattr__ item = super(DictWrapper, self).__getitem__(attr) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ KeyError: 'component' The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/builds/infrastructure/dashboard/./bin/packaging-check-invariants", line 867, in <module> raise Error(package.name) from e Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
- Feb 23, 2024
-
-
Walter Lozano authored
Apertis v2022 is no longer supported, so drop its configuration to save resources and avoid misunderstandings. Signed-off-by:
Walter Lozano <walter.lozano@collabora.com>
-
- Feb 22, 2024
-
-
Dylan Aïssi authored
Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-