Re: Bits from the Stable Release Managers

2016-11-29 Thread Iustin Pop
On 2016-11-29 13:08:54, Adam D. Barratt wrote: > On 2016-11-28 23:07, Iustin Pop wrote: > > On 2016-11-27 20:42:26, Adam D. Barratt wrote: > > >* The bug should be of severity "important" or higher > > > > Quick question: assuming all the other conditions are met (minimal > > patch, > > clean

Re: Bits from the Stable Release Managers

2016-11-29 Thread Adam D. Barratt
On 2016-11-28 23:07, Iustin Pop wrote: On 2016-11-27 20:42:26, Adam D. Barratt wrote: * The bug should be of severity "important" or higher Quick question: assuming all the other conditions are met (minimal patch, clean debdiff, etc.), this seems to discourage normal bugs fixing. Is that

Re: Bits from the Stable Release Managers

2016-11-29 Thread Julien Cristau
On 11/29/2016 12:07 AM, Iustin Pop wrote: > On 2016-11-27 20:42:26, Adam D. Barratt wrote: >>* The bug should be of severity "important" or higher > > Quick question: assuming all the other conditions are met (minimal patch, > clean debdiff, etc.), this seems to discourage normal bugs fixing.

Re: Bits from the Stable Release Managers

2016-11-29 Thread Adam D. Barratt
On 2016-11-28 23:43, Santiago Vila wrote: On Mon, Nov 28, 2016 at 03:11:17PM +0100, Philipp Kern wrote: On 2016-11-28 14:38, Holger Levsen wrote: > thanks for this update! > > On Sun, Nov 27, 2016 at 08:42:26PM +, Adam D. Barratt wrote: > >* The update must be built in an (old)stable env

Re: Bits from the Stable Release Managers

2016-11-28 Thread Santiago Vila
On Mon, Nov 28, 2016 at 03:11:17PM +0100, Philipp Kern wrote: > On 2016-11-28 14:38, Holger Levsen wrote: > > thanks for this update! > > > > On Sun, Nov 27, 2016 at 08:42:26PM +, Adam D. Barratt wrote: > > >* The update must be built in an (old)stable environment or chroot > > > > afaik

Re: Bits from the Stable Release Managers

2016-11-28 Thread Iustin Pop
On 2016-11-27 20:42:26, Adam D. Barratt wrote: >* The bug should be of severity "important" or higher Quick question: assuming all the other conditions are met (minimal patch, clean debdiff, etc.), this seems to discourage normal bugs fixing. Is that intentional (i.e. there must be significant

Re: Bits from the Stable Release Managers

2016-11-28 Thread Julien Cristau
On 11/28/2016 05:18 PM, Mattia Rizzolo wrote: > On Mon, Nov 28, 2016 at 03:47:09PM +0100, Julien Cristau wrote: >> source only uploads work for stretch and up. There are no arch:all >> autobuilders for wheezy and jessie. > > Well, it doesn't even work for stretch, actually. > There are no autobui

Re: Bits from the Stable Release Managers

2016-11-28 Thread Holger Levsen
On Mon, Nov 28, 2016 at 03:47:09PM +0100, Julien Cristau wrote: > source only uploads work for stretch and up. There are no arch:all > autobuilders for wheezy and jessie. ic. does that mean than arch:any only uploads work for wheezy+jessie? -- cheers, Holger signature.asc Description

Re: Bits from the Stable Release Managers

2016-11-28 Thread Mattia Rizzolo
On Mon, Nov 28, 2016 at 03:47:09PM +0100, Julien Cristau wrote: > source only uploads work for stretch and up. There are no arch:all > autobuilders for wheezy and jessie. Well, it doesn't even work for stretch, actually. There are no autobuilders for stretch, and dak is rejecting such uploads. -

Re: Bits from the Stable Release Managers

2016-11-28 Thread Julien Cristau
On 11/28/2016 02:38 PM, Holger Levsen wrote: > Hi Adam, > > thanks for this update! > > On Sun, Nov 27, 2016 at 08:42:26PM +, Adam D. Barratt wrote: >>* The update must be built in an (old)stable environment or chroot > > afaik source only uploads work as well, dont they? (and technicall

Re: Bits from the Stable Release Managers

2016-11-28 Thread Philipp Kern
On 2016-11-28 14:38, Holger Levsen wrote: thanks for this update! On Sun, Nov 27, 2016 at 08:42:26PM +, Adam D. Barratt wrote: * The update must be built in an (old)stable environment or chroot afaik source only uploads work as well, dont they? (and technically the above obviously incl

Re: Bits from the Stable Release Managers

2016-11-28 Thread Holger Levsen
Hi Adam, thanks for this update! On Sun, Nov 27, 2016 at 08:42:26PM +, Adam D. Barratt wrote: >* The update must be built in an (old)stable environment or chroot afaik source only uploads work as well, dont they? (and technically the above obviously includes this, but I think it would be

Re: Bits from the Stable Release Managers

2015-05-29 Thread Wouter Verhelst
On Fri, May 29, 2015 at 11:28:38AM +0200, Cyril Brulebois wrote: > Wouter Verhelst (2015-05-27): > > On Mon, May 25, 2015 at 08:47:43PM +0200, Julien Cristau wrote: > > > On Mon, May 25, 2015 at 19:42:48 +0100, Simon McVittie wrote: > > > > > > > On 25/05/15 18:24, Lisandro Damián Nicanor Pérez M

Re: Bits from the Stable Release Managers

2015-05-29 Thread Cyril Brulebois
Wouter Verhelst (2015-05-27): > On Mon, May 25, 2015 at 08:47:43PM +0200, Julien Cristau wrote: > > On Mon, May 25, 2015 at 19:42:48 +0100, Simon McVittie wrote: > > > > > On 25/05/15 18:24, Lisandro Damián Nicanor Pérez Meyer wrote: > > > > On Sunday 24 May 2015 21:27:47 Adam D. Barratt wrote: >

Re: Bits from the Stable Release Managers

2015-05-27 Thread Jakub Wilk
* Wouter Verhelst , 2015-05-27, 12:53: Maybe dak should refuse uploads of a _$arch.changes file that does not refer to any _$arch.deb files with an appropriate error message? Then this isn't an issue. What about packages that produce only arch:all binaries? dpkg-buildpackage generates _$arch.ch

Re: Bits from the Stable Release Managers

2015-05-27 Thread Wouter Verhelst
On Wed, May 27, 2015 at 12:37:09PM +0200, Jakub Wilk wrote: > * Wouter Verhelst , 2015-05-27, 10:12: > >Maybe dak should refuse uploads of a _$arch.changes file that does not > >refer to any _$arch.deb files with an appropriate error message? Then this > >isn't an issue. > > What about packages th

Re: Bits from the Stable Release Managers

2015-05-27 Thread Jakub Wilk
* Wouter Verhelst , 2015-05-27, 10:12: Maybe dak should refuse uploads of a _$arch.changes file that does not refer to any _$arch.deb files with an appropriate error message? Then this isn't an issue. What about packages that produce only arch:all binaries? dpkg-buildpackage generates _$arch.

Re: Bits from the Stable Release Managers

2015-05-27 Thread Wouter Verhelst
On Mon, May 25, 2015 at 08:47:43PM +0200, Julien Cristau wrote: > On Mon, May 25, 2015 at 19:42:48 +0100, Simon McVittie wrote: > > > On 25/05/15 18:24, Lisandro Damián Nicanor Pérez Meyer wrote: > > > On Sunday 24 May 2015 21:27:47 Adam D. Barratt wrote: > > > [snip] > > >> Due to the way that th

Re: Bits from the Stable Release Managers

2015-05-26 Thread Ansgar Burchardt
Hi, On 05/26/2015 04:13 PM, Niels Thykier wrote: > On 2015-05-26 15:42, Ian Campbell wrote: >> Perhaps the infrastructure could use something which doesn't clash with >> real person usages, e.g. "_$arch-buildd.changes" perhaps? >> > I believe dak has been changed to not care about the file name, b

Re: Bits from the Stable Release Managers

2015-05-26 Thread Niels Thykier
On 2015-05-26 15:42, Ian Campbell wrote: > [...] > > Perhaps the infrastructure could use something which doesn't clash with > real person usages, e.g. "_$arch-buildd.changes" perhaps? > > (Eventually I mean). > > Ian. > Hi, I believe dak has been changed to not care about the file name, but

Re: Bits from the Stable Release Managers

2015-05-26 Thread Ian Campbell
On Mon, 2015-05-25 at 20:47 +0200, Julien Cristau wrote: > On Mon, May 25, 2015 at 19:42:48 +0100, Simon McVittie wrote: > > > On 25/05/15 18:24, Lisandro Damián Nicanor Pérez Meyer wrote: > > > On Sunday 24 May 2015 21:27:47 Adam D. Barratt wrote: > > > [snip] > > >> Due to the way that the archi

Re: Bits from the Stable Release Managers

2015-05-25 Thread Lisandro Damián Nicanor Pérez Meyer
On Monday 25 May 2015 19:42:48 Simon McVittie wrote: [snip] > Post-jessie devscripts has "mergechanges -f -i" for source+all uploads, > which amalgamates source, arch-dep and/or arch-indep changes into > foo_1.2-3_multi.changes, discarding any arch-dep binaries. For instance > https://tracker.debi

Re: Bits from the Stable Release Managers

2015-05-25 Thread Julien Cristau
On Mon, May 25, 2015 at 19:42:48 +0100, Simon McVittie wrote: > On 25/05/15 18:24, Lisandro Damián Nicanor Pérez Meyer wrote: > > On Sunday 24 May 2015 21:27:47 Adam D. Barratt wrote: > > [snip] > >> Due to the way that the archive manages uploads to proposed-updates, if > >> you upload a .changes

Re: Bits from the Stable Release Managers

2015-05-25 Thread Simon McVittie
On 25/05/15 18:24, Lisandro Damián Nicanor Pérez Meyer wrote: > On Sunday 24 May 2015 21:27:47 Adam D. Barratt wrote: > [snip] >> Due to the way that the archive manages uploads to proposed-updates, if >> you upload a .changes file which only includes source and >> architecture:all packages, please

Re: Bits from the Stable Release Managers

2015-05-25 Thread Lisandro Damián Nicanor Pérez Meyer
On Sunday 24 May 2015 21:27:47 Adam D. Barratt wrote: [snip] > Due to the way that the archive manages uploads to proposed-updates, if > you upload a .changes file which only includes source and > architecture:all packages, please ensure that you rename it to something > other than "_$arch.changes"