Vagrant Cascadian wrote:
> In unstable and experimental we do test build paths, but also pass
> DEB_BUILD_OPTIONS=reproducible=+fixfilepath, which passes the
> -ffile-prefix-map=BUILDPATH=. argument, stripping the build path, but
> sometimes leaves traces; the length of the build path is different
> (e.g. /1/2/3 vs. /1/2/3/4), so it leaves a different amount of
> padded/empty space.
As a slight aside, the build path varies between the two builds is
currently:
/build/1st/notcurses-2.1.3+dfsg.1/
/build/2/notcurses-2.1.3+dfsg.1/2nd/
… which is actually 2 bytes difference, not 4. Still, it may be
referenced twice (making 4…), and padding/alignment is a thing on most
architectures.
(I point this out in case others are confused about a 2-byte
difference offset elsewhere in the future, rather than suggesting it
is the cause in this specific instance.)
Best wishes,
--
o
⬋ ⬊ Chris Lamb
o o reproducible-builds.org 💠
⬊ ⬋
o
_______________________________________________
Reproducible-builds mailing list
Reproducible-builds@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/reproducible-builds
