On 2025-06-30, Chris Lamb wrote:
> Whilst working on the Reproducible Builds effort [0], we noticed that
> python-django-import-export could not be built reproducibly.
>
> This is because the testsuite generates files with nondetermistic
> filenames under a django-import-export directory, which then gets
> installed to under dist-packages in the binary package.
...
> --- a/debian/rules 2025-06-30 10:15:46.318712173 -0700
> --- b/debian/rules 2025-06-30 10:19:10.660680730 -0700
> @@ -4,6 +4,7 @@
> export PYBUILD_NAME=django-import-export
> export SETUPTOOLS_SCM_PRETEND_VERSION=$(DEB_VERSION_UPSTREAM)
> export DJANGO_SETTINGS_MODULE=tests.settings
> +export PYBUILD_AFTER_TEST=rm -rfv {build_dir}/django-import-export/*
>
> %:
> dh $@ --with python3 --buildsystem=pybuildThis is still an issue, according to both reproduce.debian.net: https://reproduce.debian.net/excuses.html?source_name=python-django-import-export and tests.reproducible-builds.org: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/python-django-import-export.html Was able to confirm that the patch still fixes the issue. I would like to perform an NMU applying this in next couple weeks, please let me know if there are any outstanding concerns. live well, vagrant
signature.asc
Description: PGP signature
