Report outdated packages imported from a different channel
All threads resolved!
All threads resolved!
https://phabricator.apertis.org/T9291
Some Apertis packages come from a different Debian release. In order keep them in sync, active descendant branches are analyzed to determine in which apertis versions they landed. Then, this information is used to report on the dashboard which apertis releases need to be updated.
Signed-off-by: Dylan Aïssi dylan.aissi@collabora.com
Merge request reports
Activity
Filter activity
requested review from @wlozano
- Resolved by Dylan Aïssi
- Resolved by Dylan Aïssi
- Resolved by Dylan Aïssi
It makes sense to me and I imagine that you have tested it against different scenarios, right?
added 1 commit
- 0d59b744 - Report outdated packages imported from a different channel
added 14 commits
-
0d59b744...362eee47 - 12 commits from branch
master
- beec43db - Add Bullseye-backports, Bookworm and Sid in data/sources.yaml
- 381c6124 - Report outdated packages imported from a different channel
-
0d59b744...362eee47 - 12 commits from branch
mentioned in merge request !137 (merged)
added 5 commits
-
381c6124...24fef11c - 3 commits from branch
master
- e25566ee - Add Bullseye-backports, Bookworm and Sid in data/sources.yaml
- 642b329b - Report outdated packages imported from a different channel
-
381c6124...24fef11c - 3 commits from branch
added 4 commits
-
642b329b...444e8aa6 - 2 commits from branch
master
- 32b9e3f0 - Add Bullseye-backports, Bookworm and Sid in data/sources.yaml
- b44af864 - Report outdated packages imported from a different channel
-
642b329b...444e8aa6 - 2 commits from branch
added 1 commit
- 697eb1e3 - Check git debian branches to ensure they correspond to a tracked Debian release
Please register or sign in to reply