Am Freitag, 23. Dezember 2011, 20:17:13 schrieb Goswin von Brederlow:
> Lars Wirzenius writes:
> > On Fri, Dec 23, 2011 at 10:41:07AM +, Roger Leigh wrote:
> >> The suggestion that "git clean" be a solution appears to have caused
> >> some level of outrage. However, at least for '3.0 (git)',
Lars Wirzenius writes:
> On Fri, Dec 23, 2011 at 10:41:07AM +, Roger Leigh wrote:
>> The suggestion that "git clean" be a solution appears to have caused
>> some level of outrage. However, at least for '3.0 (git)', all the
>> sources are known to git, and 'git clean' is a reliable and simple
On 23/12/11 at 11:16 +0100, Jakub Wilk wrote:
> >>>On 20/12/11 at 22:01 +0200, Peter Eisentraut wrote:
> With recent dpkg(-source) changes, many packages are again
> failing to build twice in a row, because of uncommitted
> upstream changes.
>
> Yes, I'd expect that the situation is mu
On Fri, Dec 23, 2011 at 10:41:07AM +, Roger Leigh wrote:
> The suggestion that "git clean" be a solution appears to have caused
> some level of outrage. However, at least for '3.0 (git)', all the
> sources are known to git, and 'git clean' is a reliable and simple
> solution to the problem. T
On Fri, Dec 23, 2011 at 10:41:07AM +, Roger Leigh wrote:
> The suggestion that "git clean" be a solution appears to have caused
> some level of outrage. However, at least for '3.0 (git)', all the
> sources are known to git, and 'git clean' is a reliable and simple
> solution to the problem.
A
On Fri, Dec 23, 2011 at 11:16:34AM +0100, Jakub Wilk wrote:
> >>>On 20/12/11 at 22:01 +0200, Peter Eisentraut wrote:
> With recent dpkg(-source) changes, many packages are again
> failing to build twice in a row, because of uncommitted
> upstream changes.
>
> Yes, I'd expect that the s
On 20/12/11 at 22:01 +0200, Peter Eisentraut wrote:
With recent dpkg(-source) changes, many packages are again failing
to build twice in a row, because of uncommitted upstream changes.
Yes, I'd expect that the situation is much worse than it used to be. Not
only because of dpkg-source changes
* Charles Plessy , 2011-12-21, 10:30:
Personally I have given up making packages buildable twice in a row
using “debian clean” for the packages I maintain with git,
Thanks for the heads-up. I will avoid your packages when doing QA work.
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-devel-
Charles Plessy writes:
> Le Tue, Dec 20, 2011 at 10:01:44PM +0200, Peter Eisentraut a écrit :
>> With recent dpkg(-source) changes, many packages are again failing to
>> build twice in a row, because of uncommitted upstream changes. Fixing
>> this was a lenny release goal, maybe it should be on
Lucas Nussbaum writes:
> On 20/12/11 at 23:16 +, brian m. carlson wrote:
>> On Tue, Dec 20, 2011 at 09:36:47PM +0100, Lucas Nussbaum wrote:
>> > On 20/12/11 at 22:01 +0200, Peter Eisentraut wrote:
>> > > With recent dpkg(-source) changes, many packages are again failing to
>> > > build twice
Hi,
Am Dienstag, den 20.12.2011, 21:36 +0100 schrieb Lucas Nussbaum:
> On 20/12/11 at 22:01 +0200, Peter Eisentraut wrote:
> > With recent dpkg(-source) changes, many packages are again failing to
> > build twice in a row, because of uncommitted upstream changes. Fixing
> > this was a lenny relea
On 20/12/11 at 23:16 +, brian m. carlson wrote:
> On Tue, Dec 20, 2011 at 09:36:47PM +0100, Lucas Nussbaum wrote:
> > On 20/12/11 at 22:01 +0200, Peter Eisentraut wrote:
> > > With recent dpkg(-source) changes, many packages are again failing to
> > > build twice in a row, because of uncommitte
Le Tue, Dec 20, 2011 at 10:01:44PM +0200, Peter Eisentraut a écrit :
> With recent dpkg(-source) changes, many packages are again failing to
> build twice in a row, because of uncommitted upstream changes. Fixing
> this was a lenny release goal, maybe it should be one again?!? Most
> importantly,
On Tue, Dec 20, 2011 at 09:36:47PM +0100, Lucas Nussbaum wrote:
> On 20/12/11 at 22:01 +0200, Peter Eisentraut wrote:
> > With recent dpkg(-source) changes, many packages are again failing to
> > build twice in a row, because of uncommitted upstream changes. Fixing
> > this was a lenny release goa
On 20/12/11 at 22:01 +0200, Peter Eisentraut wrote:
> With recent dpkg(-source) changes, many packages are again failing to
> build twice in a row, because of uncommitted upstream changes. Fixing
> this was a lenny release goal, maybe it should be one again?!? Most
> importantly, maybe someone wh
With recent dpkg(-source) changes, many packages are again failing to
build twice in a row, because of uncommitted upstream changes. Fixing
this was a lenny release goal, maybe it should be one again?!? Most
importantly, maybe someone who has access to one of those build grids
can run the old tes
16 matches
Mail list logo
