On Sun, Oct 11, 2015 at 12:11:59PM +0200, Holger Levsen wrote:
> On Samstag, 10. Oktober 2015, Santiago Vila wrote:
> > This suggests that the problem is maybe related to one or more of the
> > dh_* tools and/or different filesystem ordering, as the source
> > packages themselves do not seem to be doing anything "strange".
> Thanks, that's very useful to track, as it now became obvious to me that it
> only affects very few packages, which is somewhat relieving…
> As a "rather wild guess" I believe this is caused by dpkg, as
> is also affected, which is using /usr/share/R/debian/r-cran.mk in
> debian/rules, which is using cdbs, which is calling dh_stripnondeterminism,
> while the others are using plain old manual dh_* invocations in debian/rules,
> thus are not calling dh_stripnondeterminism… and as this is found with and
> without stripnondeterminism I suppose the cause is elsewhere… hence dpkg.
But everything dpkg does is to take a "snapshot" of whatever you put
in debian/$(package) without altering any files or directories. What
you see in data.tar.gz is whatever you put it there first.
r-cran-checkmate uses r-cran.mk which includes debhelper.mk which in
turn still uses lots of dh_* commands, so I keep my bet :-) which
is dh_install or alike + disorderfs.
Reproducible-builds mailing list