Re: Updated proposal for improving the FTP NEW process

2018-03-06 Thread Joerg Jaspert
On 14967 March 1977, Gert Wollny wrote: I so like proposals from people who have never ever done any of the work they propose something one. BUt hey... > (1) Given that all new source package come with an ITP bug, when a > package must be rejected, the FTP team could CC this bug in the > rejectio

Re: Updated proposal for improving the FTP NEW process

2018-03-06 Thread Andrey Rahmatullin
On Wed, Mar 07, 2018 at 06:02:10AM +, Chris Lamb wrote: > Andrey Rahmatullin wrote: > > > > > I know for a fact that quite regularly licence checks on binNEW packages > > > > causes RC bugs to pop up. I acknowledge it may be a burder for the ftp > > > > team, but that reason alone probably de

Re: Updated proposal for improving the FTP NEW process

2018-03-06 Thread Chris Lamb
Andrey Rahmatullin wrote: > > > I know for a fact that quite regularly licence checks on binNEW packages > > > causes RC bugs to pop up. I acknowledge it may be a burder for the ftp > > > team, but that reason alone probably deserves to keep binNEW as it is. > > > > That would seem to justify so

Re: Updated proposal for improving the FTP NEW process

2018-03-06 Thread Adam Borowski
On Tue, Mar 06, 2018 at 06:15:10PM +, Ian Jackson wrote: > Adam Borowski writes ("Re: Updated proposal for improving the FTP NEW > process"): > > On Tue, Mar 06, 2018 at 03:17:11PM +, Ian Jackson wrote: > > > IMO Debian's rules should require that the revision should be > > > incremented

Re: Updated proposal for improving the FTP NEW process

2018-03-06 Thread Sean Whitton
Hello, On Tue, Mar 06 2018, Andrey Rahmatullin wrote: > On Mon, Mar 05, 2018 at 02:43:34PM -0700, Sean Whitton wrote: >> If a package is maintained in git, then re-using a version number >> means force-pushing a git tag > Just don't tag uploads until they are accepted. This means that uploading

Re: Updated proposal for improving the FTP NEW process

2018-03-06 Thread Holger Levsen
On Tue, Mar 06, 2018 at 05:54:55PM +0100, Adam Borowski wrote: > With my one of most active sponsors hat on: the current policy is that a > version that has never hit the archive must not have a separate changelog > entry, unless there are non-negligible users (such as a derivative, upstream > repo

Re: Updated proposal for improving the FTP NEW process

2018-03-06 Thread Sean Whitton
Hello, On Tue, Mar 06 2018, Adam Borowski wrote: > gaps in version numbering that come without an explanation also raise > an eyebrow (thus such a gap needs a comment in the changelog). I think this is the problem. Ian's concern about non-identical but identically versioned source packages flyi

Re: Rant about Debian reproducibility environment

2018-03-06 Thread Steffen Nurpmeso
Paride Legovini wrote: |On 2018-03-01 18:17, Steffen Nurpmeso wrote: |> But last week Paride committed "fixes"[1] after having been |> prodded by some third party, and indeed, now S-nail is |> reproducible on all Debian test boxes. The fix was to set the |> built-in identification for the OS

Re: (solved) Re: wireless fail after stretch installation

2018-03-06 Thread Brian
On Tue 06 Mar 2018 at 18:34:27 +, Ian Jackson wrote: > bw writes ("Re: (solved) Re: wireless fail after stretch installation"): > > I think the idea needs to be talked over a little better, because using > > e/n/i for wireless by default after first boot has implications if the > > user (who

Re: Updated proposal for improving the FTP NEW process

2018-03-06 Thread Lars Wirzenius
On Wed, 2018-03-07 at 00:30 +0500, Andrey Rahmatullin wrote: > On Tue, Mar 06, 2018 at 07:27:40PM +, Ian Campbell wrote: > > > I know for a fact that quite regularly licence checks on binNEW packages > > > causes RC bugs to pop up. I acknowledge it may be a burder for the ftp > > > team, but t

Re: Updated proposal for improving the FTP NEW process

2018-03-06 Thread Andrey Rahmatullin
On Tue, Mar 06, 2018 at 07:27:40PM +, Ian Campbell wrote: > > I know for a fact that quite regularly licence checks on binNEW packages > > causes RC bugs to pop up. I acknowledge it may be a burder for the ftp > > team, but that reason alone probably deserves to keep binNEW as it is. > > That

Re: Updated proposal for improving the FTP NEW process

2018-03-06 Thread Ian Campbell
On Tue, 2018-03-06 at 19:18 +0100, Mattia Rizzolo wrote: > On Tue, Mar 06, 2018 at 06:34:28PM +0100, Adam Borowski wrote: > > What might be reasonable is making the separation between binNEW and srcNEW > > more obvious, especially for us on the other side. This would also > > encourage the ftpmast

Re: (solved) Re: wireless fail after stretch installation

2018-03-06 Thread Brian Potkin
On Tue 06 Mar 2018 at 18:27:29 +, Ian Jackson wrote: > Brian writes ("Re: (solved) Re: wireless fail after stretch installation"): > > #694068, #696755, #727740 and #777439. > > Thanks. > > I have read the bug logs and Trent Buck's message here > https://bugs.debian.org/cgi-bin/bugreport.c

Bug#892205: ITP: magic-wormhole-transit-server -- Transit Relay server for Magic-Wormhole

2018-03-06 Thread Antoine Beaupre
Package: wnpp Severity: wishlist Owner: Antoine Beaupre * Package name: magic-wormhole-transit-server Version : 0.1.1 Upstream Author : Brian Werner * URL : https://github.com/warner/magic-wormhole-transit-relay * License : MIT Programming Lang: Python Desc

Re: Updated proposal for improving the FTP NEW process

2018-03-06 Thread Andrey Rahmatullin
On Tue, Mar 06, 2018 at 06:15:10PM +, Ian Jackson wrote: > > A changelog bloated with every replaced attempt is hard to read; gaps in > > version numbering that come without an explanation also raise an eyebrow > > (thus such a gap needs a comment in the changelog). > > How many replaced attem

Re: (solved) Re: wireless fail after stretch installation

2018-03-06 Thread Ian Jackson
bw writes ("Re: (solved) Re: wireless fail after stretch installation"): > I think the idea needs to be talked over a little better, because using > e/n/i for wireless by default after first boot has implications if the > user (who is clueless) later installs a desktop environment. If installing

Re: (solved) Re: wireless fail after stretch installation

2018-03-06 Thread Ian Jackson
Brian writes ("Re: (solved) Re: wireless fail after stretch installation"): > #694068, #696755, #727740 and #777439. Thanks. I have read the bug logs and Trent Buck's message here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694068#47 seems to suggest a way forward. Perhaps someone would

Re: Updated proposal for improving the FTP NEW process

2018-03-06 Thread Mattia Rizzolo
On Tue, Mar 06, 2018 at 06:34:28PM +0100, Adam Borowski wrote: > What might be reasonable is making the separation between binNEW and srcNEW > more obvious, especially for us on the other side. This would also > encourage the ftpmasters to skip license checks for binNEW -- but again, > without kno

Re: Updated proposal for improving the FTP NEW process

2018-03-06 Thread Ian Jackson
Adam Borowski writes ("Re: Updated proposal for improving the FTP NEW process"): > On Tue, Mar 06, 2018 at 03:17:11PM +, Ian Jackson wrote: > > IMO Debian's rules should require that the revision should be > > incremented (at least) when you have shared the previous revision with > > other pe

Re: Updated proposal for improving the FTP NEW process

2018-03-06 Thread Bastian Blank
Hi Steve Please don't top-post and fix the length of your lines. On Tue, Mar 06, 2018 at 10:22:22AM -0600, Steve Robbins wrote: > Or: change the mechanism to avoid a trip through NEW for simple cases that > Chris outlined: new binary or soname bump. Reserve NEW for truly new things. Can you de

Re: Updated proposal for improving the FTP NEW process

2018-03-06 Thread Adam Borowski
On Tue, Mar 06, 2018 at 10:22:22AM -0600, Steve Robbins wrote: > Or: change the mechanism to avoid a trip through NEW for simple cases that > Chris outlined: new binary or soname bump. Reserve NEW for truly new > things. Let's not try to be wiser than ftpmasters: if, despite the increased workloa

Re: Updated proposal for improving the FTP NEW process

2018-03-06 Thread Steve Robbins
Or: change the mechanism to avoid a trip through NEW for simple cases that Chris outlined: new binary or soname bump. Reserve NEW for truly new things. On March 5, 2018 9:00:06 AM CST, "W. Martin Borgert" wrote: >Quoting Chris Lamb : >>> In many cases, there is an issue open about the new bina

Re: (solved) Re: wireless fail after stretch installation

2018-03-06 Thread Brian
On Tue 06 Mar 2018 at 15:01:03 +, Ian Jackson wrote: > Brian writes ("Re: (solved) Re: wireless fail after stretch installation"): > > The plain and simple fact is that a user who installs over a wireless > > link and does not have network-manager does not have any connectivity > > to the inte

Re: Updated proposal for improving the FTP NEW process

2018-03-06 Thread Adam Borowski
On Tue, Mar 06, 2018 at 03:17:11PM +, Ian Jackson wrote: > Scott Kitterman writes ("Re: Updated proposal for improving the FTP NEW > process"): > > If you consider it absurd to not increment the revision due to > > changes that never made it in the archive, then I don't know where > > it stop

Re: Updated proposal for improving the FTP NEW process

2018-03-06 Thread Ian Jackson
Scott Kitterman writes ("Re: Updated proposal for improving the FTP NEW process"): > If you consider it absurd to not increment the revision due to > changes that never made it in the archive, then I don't know where > it stops. IMO Debian's rules should require that the revision should be incre

Re: (solved) Re: wireless fail after stretch installation

2018-03-06 Thread Ian Jackson
Brian writes ("Re: (solved) Re: wireless fail after stretch installation"): > The plain and simple fact is that a user who installs over a wireless > link and does not have network-manager does not have any connectivity > to the internet after first boot. Long Wind solved the issue by taking > the

Bug#892190: ITP: python-user-agents -- A Python library that provides an easy way to identify devices like mobile phones, tablets and their capabilities by parsing (browser) user agent strings.

2018-03-06 Thread Andre Bianchi
Package: wnpp Severity: wishlist Owner: Andre Bianchi Control: block 745661 by -1 Control: block 796777 by -1 * Package name: python-user-agents Version : 1.1.0 Upstream Author : Selwin Ong, Loisaida Sam Sandberg * URL : https://pypi.python.org/pypi/user-agents * Licen

Bug#892182: ITP: siphashc -- siphashc is a python c-module for siphash, based on floodberry's version.

2018-03-06 Thread Andre Bianchi
Package: wnpp Severity: wishlist Owner: Andre Bianchi Control: block 745661 by -1 Control: block 796777 by -1 * Package name: siphashc Version : 1.0 Upstream Author : Eli Janssen, Carlo Pires, Michal Čihař * URL : https://github.com/WeblateOrg/siphashc/ * License

Re: A proposal for improving transparency of the FTP NEW process

2018-03-06 Thread Dominique Dumont
On Saturday, 3 March 2018 07:54:00 CET Lars Wirzenius wrote: > We have licencecheck, and if that isn't good enough, we can improve > it. That's my cue to advertise "cme update dpkg-copyright" that uses licencecheck output to provide a debian/copyright file See [1] for details (and limitations)

Re: Rant about Debian reproducibility environment

2018-03-06 Thread Paride Legovini
On 2018-03-01 18:17, Steffen Nurpmeso wrote: > > But last week Paride committed "fixes"[1] after having been > prodded by some third party, and indeed, now S-nail is > reproducible on all Debian test boxes. The fix was to set the > built-in identification for the OS build environment to all > "De

Re: [Pkg-javascript-devel] three.js_80+dfsg2-2_amd64.changes REJECTED

2018-03-06 Thread Ian Jackson
Pirate Praveen writes ("Re: [Pkg-javascript-devel] three.js_80+dfsg2-2_amd64.changes REJECTED"): > On വ്യാഴം 01 മാർച്ച് 2018 05:45 വൈകു, Ian Jackson wrote: > > For the avoidance of doubt, I don't have a problem with the specific > > decision of ftpmaster here. > > Coming back to this specific r

Bug#892157: ITP: itk4 -- [incr Tk] OOP extension version 4 for Tk

2018-03-06 Thread Sergei Golovan
Package: wnpp Severity: wishlist Owner: Sergei Golovan * Package name: itk4 Version : 4.1.0 Upstream Author : Tcl Core Team * URL : http://incrtcl.sourceforge.net/itk/index.html * License : BSD (the same as Tcl) Programming Lang: C, Tcl Description : [i

Bug#892155: ITP: itcl4 -- [incr Tcl] OOP extension for Tcl

2018-03-06 Thread Sergei Golovan
Package: wnpp Severity: wishlist Owner: Sergei Golovan * Package name: itcl4 Version : 4.1.1 Upstream Author : Tcl Core Team * URL : http://incrtcl.sourceforge.net/itcl/ * License : BSD (the same as for Tcl itself) Programming Lang: C, Tcl Description :