[Adding 877...@bugs.debian.org to CC] Hi jathan,
> Also I want to ask you what does it mean you actually use > /usr/share/dpkg/pkg-info.mk for SOURCE_DATE_EPOCH See, for example: https://github.com/lamby/pkg-python-daiquiri/blob/debian/sid/debian/rules#L3 If you take a look at the /usr/share/dpkg/pkg-info.mk file itself, it should be fairly clear what it exports to the outside environment. In the python-daiquiri example, I'm using DEB_VERSION_UPSTREAM for a reproducibility-related reason, but you should be able to see how it applies to SOURCE_DATE_EPOCH too :) > Thanks a lot and sorry for my delay to reply, No worries about the delay. Note that I've added 877...@bugs.debian.org to the CC; generally when a question pertains to a specific bug, it's a great idea to ensure that the conversation is archived there. Keeps everyone sane too as it's easy to "load" context after a few days/weeks. :) Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- _______________________________________________ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
