Don't report Debian updates if they already have been imported in Apertis

Don't report Debian updates if they already have been imported in Apertis using the debian-security repository before being available in the main Debian repository through a point release.

https://phabricator.apertis.org/T8870

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

requested review from @em

That is not enough, I just found a case (dask.distributed) where an update is marked as available but is already imported in Apertis.

For dask.distributed, we use the branch debian/bullseye-proposed-updates.

Yep, it's not just about -security. For a branch $foo you may need to look to all the $foo-* branches.

I'm still not persuaded this is the right thing to do compared to fixing the update script to update debian/bullseye if a new version has been landed to Bullseye.

I'd propose to take this MR to drop some noise in the short term, but also leave T8870 open to teach apertis-pkg-pull-updates to properly fast-forward branches (and then revert this).

I agree, this MR is just to hide wrong tags under the carpet. I will have a look at apertis-pkg-pull-updates.

--> pkg/apertis-dev-tools!26 (merged)

Fyi, !111 (merged)

I close this MR in favor of pkg/apertis-dev-tools!26 (merged).

closed