[Debian-pan-maintainers] Bug#1078268: pyfai: please make the package build reproducible

[James Addison]

On Fri, 9 Aug 2024 at 21:14, Vagrant Cascadian
<vagrant at reproducible-builds.org> wrote:
>
> user reproducible-builds at lists.alioth.debian.org
> usertags 1064748 +randomness -buildpath
> thanks
>
> On 2024-08-09, James Addison wrote:
> > Usertags: buildpath cpu
> ...
> > The first cause of non-determinism is the use of temporary directory paths by
> > the meson-python build process; the resulting paths are embedded in some of the
> > extension modules (for example, this[4] CRC32 module) produced in the output
> > binary package.
> >
> > The meson-python build generates and uses a temporary, randomized build
> > directory path only when no build-dir setting is already configured.  So we may
> > be able to resolve this problem by choosing an appropriate static build-dir.
>
> Typically we have used buildpath to mean the build directory that the
> build is performed in, which can be worked around by building in the
> same path, not randomized temporary files or directories used during the
> build.
>
> I think "randomness" would be a more appropriate usertag here, and have
> adjusted appropriately.

Thanks, Vagrant - it's possible that I'm splitting hairs, but the randomized
temporary path is created below the working build directory, and the problem
occurs due to the embedding of that complete resulting path (build dir plus
randomized suffix) in the compiled extension files.

In other words: if we resolved the randomness, but then varied the build path,
I believe the results would again become non-reproducible.

Perhaps we could include both tags?