magma-rocm_2.9.0+ds-3_amd64.changes REJECTED

[Santiago Vila]

On Thu, Nov 20, 2025 at 10:43:11PM -0700, Cordell Bloor wrote:

> On 2025-11-20 22:37, Debian FTP Masters wrote:
> > magma-rocm_2.9.0+ds.orig.tar.xz: Does not match file already existing in the pool.
> [...]
> Unfortunately, it seems I've screwed something up. I don't understand how to
> resolve this problem.

This is what the upload queue said before:

magma-rocm_2.9.0+ds-3_amd64.changes uploaded successfully to localhost
along with the files:
  magma-rocm_2.9.0+ds-3.dsc
  magma-rocm_2.9.0+ds.orig.tar.xz
  magma-rocm_2.9.0+ds-3.debian.tar.xz
  libmagma-rocm-dev_2.9.0+ds-3_amd64.deb
  libmagma-rocm-doc_2.9.0+ds-3_all.deb
  libmagma-rocm-test-dbgsym_2.9.0+ds-3_amd64.deb
  libmagma-rocm-test_2.9.0+ds-3_amd64.deb
  libmagma-sparse2-rocm-dbgsym_2.9.0+ds-3_amd64.deb
  libmagma-sparse2-rocm_2.9.0+ds-3_amd64.deb
  libmagma2-rocm-dbgsym_2.9.0+ds-3_amd64.deb
  libmagma2-rocm_2.9.0+ds-3_amd64.deb
  magma-rocm_2.9.0+ds-3_amd64.buildinfo

The problem here is that you tried to upload magma-rocm_2.9.0+ds.orig.tar.xz
again and *also* it differs from the one used the last time.

When using dpkg-buildpackage, this is fixed easily by placing the file
below the toplevel directory, that way dpkg-buildpackage knows that's
the file to reference in the *.changes file (and also it will
avoid uploading it again).

I'm not fluent enough with gbp to tell you the exact recipe with gbp,
but the underlying idea is the same: You can't upload a different
tar.xz than the one already in the archive.

Thanks.