Re: FTBFS if built twice in a row
On 17/07/07 at 11:53 +0200, Goswin von Brederlow wrote:
> Peter Samuelson <firstname.lastname@example.org> writes:
> > [Lucas Nussbaum]
> >> The problem is that it isn't required to have exactly the same source
> >> tree after "./configure ; make ; make clean". It's just required that
> >> "./configure ; make ; make clean ; ./configure ; make" works. It is
> >> possible that the first build modifies some files, but that the package
> >> can still be built, without being differerent from the one from the
> >> first build.
> > How about this then: if you debuild without -b, -B, or -nc, it builds a
> > source package before building the binary packages. What if it were to
> > build another source package afterwards, and compare the two .diff.gz
> > files? Timestamps in the diff would be ignored. But if the actual
> > file contents of the diff were different, that would IMO be a bug.
> > --
> > Peter Samuelson | org-tld!p12n!peter | http://p12n.org/
> debuild; debuild -S; debdiff should give zero changes. Often enough
> that isn't true though.
Being pedantic doesn't help if nobody fixes the bugs. Only about half of
the ~400 "FTBFS if built twice in a row" bugs have been fixed so far.
So if you want to move forward with this issue, you have to figure out a
reasonable way (that adds at most hundreds of bugs at each step, not
A good second step could be to check that the .debs generated by the
first and second builds are reasonably identical. (excluding timestamps,
| Lucas Nussbaum
| email@example.com http://www.lucas-nussbaum.net/ |
| jabber: firstname.lastname@example.org GPG: 1024D/023B3F4F |