Unable to add tarballs in new package revision

Background

Apertis' infrastructure doesn't support adding a new upstream tarball (for package with multiple upstream tarballs) in a new package revision without changing the upstream version

docker.io is a package with multiple upstream tarballs, we first imported 26.1.5+dfsg1-4 in v2026dev2 without any issue, but now I try to import 26.1.5+dfsg1-9 and it fails to build because they added a new upstream tarball docker.io_26.1.5+dfsg1.orig-buildkit.tar.xz in 26.1.5+dfsg1-6 which is missing on our side. Since it's the same upstream version than the first version, our pipeline doesn't import it.

We can still workaround by manually importing the missing tarball:

dget -d https://deb.debian.org/debian/pool/main/d/docker.io/docker.io_26.1.5+dfsg1-9.dsc
cd docker.io/
pristine-lfs commit ../docker.io_26.1.5+dfsg1.orig-buildkit.tar.xz
git push origin pristine-lfs

Reproducibility

How often the issue is hit when repeating the steps to reproduce and changing nothing?

Put the ✅ in the most appropriate entry:

1. ✅ always, but very rare bug
2. often, but not always
3. rarely

Impact of bug

Block the automatic update of the package.

Outcomes

TBD

Management data

This section is for management only, it should be the last one in the description.

/cc @em @balasubramanian @sudarshan @wlozano

Phabricator link: https://phabricator.apertis.org/T11023