Problem Statement/Rationale

APT in Debian/Ubuntu determines packages to be upgraded by their version, but the mongodb APT repositories for Ubuntu Bionic, Focal and Debian Stretch, Buster, Bullseye in version 4.4 (the only ones I am tracking, this might affect every APT-packaged version) recently (Fetched by our mirror 2022-07-19, 06:30:00 UTC+0) swapped the file mongodb-database-tools_100.5.4_amd64.deb.

What is going wrong? What action would you like the Engineering team to take?

Republishing existing APT packages will lead to "invisible" inconsistencies between installations being done before and after the swap.

old: b6d55e2b7dc050642073bd7a6d0bad449f62801ea394bbb8b27699f5341f6964 47713644 mongodb-database-tools_100.5.4_amd64.deb
new: 1ee620e15949f1d8e582d4171ed97e2783edfe0eb8d051a687347a32b98ad4f2 47707804 mongodb-database-tools_100.5.4_amd64.deb

(<SHA256 checksum> <size in bytes> <filename>)

Diffoscope shows many differences, seemingly because a different snapshot of the repository was used as the package source, like:
-/data/mci/9e93c64b1446d47d4c4f9e3a5e5a9a6e/src/github.com/mongodb/mongo-tools/vendor/github.com/klauspost/compress/zstd/enc_dfast.go:598+/data/mci/97b50401c08c58659bbd679862d0143e/src/github.com/mongodb/mongo-tools/vendor/github.com/klauspost/compress/zstd/enc_dfast.go:598

The file contents seem unchanged for most files that are not build artifacts, but the files were moved from

Steps to Reproduce

How could an engineer replicate the issue you’re reporting?

Expected Results

What do you expect to happen?

Actual Results

What do you observe is happening?

Additional Notes

Any additional information that may be useful to include.