Russ Allbery <[EMAIL PROTECTED]> writes:
> Goswin von Brederlow <[EMAIL PROTECTED]> writes:
>> Russ Allbery <[EMAIL PROTECTED]> writes:
>
>>> Not if you use pdebuild or similarly build in a chroot, which IMO
>>> everyone should be doing.
>
>> I use xen instances and that changes nothing at all.
>
? 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
> tha
Goswin von Brederlow <[EMAIL PROTECTED]> writes:
> Russ Allbery <[EMAIL PROTECTED]> writes:
>> Not if you use pdebuild or similarly build in a chroot, which IMO
>> everyone should be doing.
> I use xen instances and that changes nothing at all.
> 1. My ~/src is mounted inside the build environme
Peter Samuelson <[EMAIL PROTECTED]> 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 t
Russ Allbery <[EMAIL PROTECTED]> writes:
> Goswin von Brederlow <[EMAIL PROTECTED]> writes:
>> Russ Allbery <[EMAIL PROTECTED]> writes:
>
>>> This check would fail many packages that can still be built twice in a
>>> row (any package that runs autotools during the build process without
>>> doing a
[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 p
On Mon, Jul 02, 2007 at 09:50:52AM -0700, Russ Allbery wrote:
> Goswin von Brederlow <[EMAIL PROTECTED]> writes:
> >> This check would fail many packages that can still be built twice in a
> >> row (any package that runs autotools during the build process without
> >> doing a complicated dance to
Goswin von Brederlow <[EMAIL PROTECTED]> writes:
> Russ Allbery <[EMAIL PROTECTED]> writes:
>> This check would fail many packages that can still be built twice in a
>> row (any package that runs autotools during the build process without
>> doing a complicated dance to preserve the upstream-shipp
Russ Allbery <[EMAIL PROTECTED]> writes:
> Gerard Lledó <[EMAIL PROTECTED]> writes:
>
>> My understanding of debian is far from being complete, but in order to
>> be built for a second time a clean is performed before (at least, using
>> debuild). So directory should look like a fresh $ apt-get so
On 29/06/07 at 20:21 +0300, Gerard Lledó wrote:
> On 6/29/07, Santiago Vila <[EMAIL PROTECTED]> wrote:
> >On Fri, 29 Jun 2007, Adeodato Simó wrote:
> >
> >> * Santiago Vila [Fri, 29 Jun 2007 16:58:13 +0200]:
> >> > I don't know how much typical this example is, but the two "can't build
> >> > twice
On 6/29/07, Santiago Vila <[EMAIL PROTECTED]> wrote:
On Fri, 29 Jun 2007, Adeodato Simó wrote:
> * Santiago Vila [Fri, 29 Jun 2007 16:58:13 +0200]:
> > I don't know how much typical this example is, but the two "can't build
> > twice in a row" bugs I got were like that.
>
> The you should/could
On Fri, 29 Jun 2007, Adeodato Simó wrote:
> * Santiago Vila [Fri, 29 Jun 2007 16:58:13 +0200]:
> > I don't know how much typical this example is, but the two "can't build
> > twice in a row" bugs I got were like that.
>
> The you should/could remove the .mo files in your debian/rules clean
> targ
* Santiago Vila [Fri, 29 Jun 2007 16:58:13 +0200]:
> Consider the case where the .diff.gz for a package updates a .po file but
> not the corresponding .mo file (which are usually included in the original
> tarball as well).
> You need to run ./configure at least to be able to run the clean target
Gerard Lledó <[EMAIL PROTECTED]> writes:
> My understanding of debian is far from being complete, but in order to
> be built for a second time a clean is performed before (at least, using
> debuild). So directory should look like a fresh $ apt-get source
> packagename. And the contents of the file
Hi,
> I've been looking for FTBFS bugs in the BTS and I've noticed that
> there are lots of FTBFS if built twice.
>
> My understanding of debian is far from being complete, but in order to
> be built for a second time a clean is performed before (at least,
> using debuild). So directory should lo
On Fri, 29 Jun 2007, Gerard Lledó wrote:
> Hi,
>
> I've been looking for FTBFS bugs in the BTS and I've noticed that
> there are lots of FTBFS if built twice.
>
> My understanding of debian is far from being complete, but in order to
> be built for a second time a clean is performed before (at l
Hi,
I've been looking for FTBFS bugs in the BTS and I've noticed that
there are lots of FTBFS if built twice.
My understanding of debian is far from being complete, but in order to
be built for a second time a clean is performed before (at least,
using debuild). So directory should look like a f
17 matches
Mail list logo