Bug#525593: Processing of belpic_2.6.0-6.1_amd64.changes

2009-07-19 Thread Wouter Verhelst
Please don't do random NMU's without getting approval from the maintainer. Belpic has serious issues in that some builds work, while others don't, depending on the state of the build-deps; the only way to defend against this is by extensive testing, which you _cannot_ have done since you don't

Bug#525593: Processing of belpic_2.6.0-6.1_amd64.changes

2009-07-19 Thread Cyril Brulebois
Wouter Verhelst wou...@debian.org (19/07/2009): Please don't do random NMU's without getting approval from the maintainer. That's why it's in DELAYED and can be cancelled. Belpic has serious issues in that some builds work, while others don't, depending on the state of the build-deps; the

Bug#525593: Processing of belpic_2.6.0-6.1_amd64.changes

2009-07-19 Thread Wouter Verhelst
On Sun, Jul 19, 2009 at 05:48:04PM +0200, Cyril Brulebois wrote: Wouter Verhelst wou...@debian.org (19/07/2009): Please don't do random NMU's without getting approval from the maintainer. That's why it's in DELAYED and can be cancelled. The procedure, last I checked, was still 'use

Bug#525593: Processing of belpic_2.6.0-6.1_amd64.changes

2009-07-19 Thread Cyril Brulebois
Wouter Verhelst wou...@debian.org (19/07/2009): The procedure, last I checked, was still 'use DELAYED/7 or ask for explicit approval'. 5.11.1 says DELAYED/2 for RC bugfixes. I'm sorry I missed 1 day after months of RC-bugginess. Sorry, I thought I had done that before; apparently I haven't.