Make fetching of backports and proposed-updates repositories optional

The Apertis pipeline imports backport and/or proposed-updates versions by default, this is not needed and leads to miss some security updates. Because, importing versions from backports and proposed-updates is not part of our standard workflow, this should only be optional to avoid confusing the pipeline.

See infrastructure/ci-package-builder!316 (merged) for the ci-package-builder part.

https://phabricator.apertis.org/T9538

mentioned in merge request infrastructure/ci-package-builder!316 (merged)

changed the description

@ritesh this should simplify our life when importing debian updates.

Not sure if it will work for repos already in a dirty state, for example when *-backports versions were already imported in our git repo, but I guess we will have to clean them manually.

I successfully tested this change in local with debootstrap

mentioned in issue infrastructure/apertis-issues#505 (closed)

marked this merge request as draft

Ah! the dashboard tracks the *-updates repos, but apertis-pkg-pull-updates checked in *-proposed-updates which may contain updates not (yet) desired for Apertis (packages which are still in a testing period in Debian).

Instead we should maybe change apertis-pkg-pull-updates to check by default *-updates repos like it is done for *-security (and was done for *-proposed-updates).

resolved all threads

approved this merge request

added 1 commit

• f49d5040 - apertis-pkg-pull-updates: pull updates from *-updates repositories

Compare with previous version

added 2 commits

• 13958b68 - apertis-pkg-pull-updates: pull updates from *-updates repositories
• b9176678 - Release apertis-dev-tools version 0.2023.11

Compare with previous version

resolved all threads

marked this merge request as ready

merged