Re: Worthless descriptions for almost all of the recent node-* ITPs

2017-01-09 Thread Geert Stappers
On Sat, Jan 07, 2017 at 09:44:54PM +0530, Pirate Praveen wrote: > On ? 07 ?? 2017 09:30 , Philip Hands > wrote: > > I'm tempted to respond to each of these people's first ITP with some > > suggestions, but you are much better placed to pass on advice to them, >

Bug#850672: ITP: gnome-shell-extension-show-ip -- Shows the urrent private or public IP address in the GNOME Shell status drop-down menu

2017-01-09 Thread Kyle Robbertze
Package: wnpp Severity: wishlist Owner: Kyle Robbertze * Package name: gnome-shell-extension-show-ip Version : 4.0.1 Upstream Author : Kyle Robbertze * URL : https://gitlab.com/paddatrapper/show-ip-gnome-extension * License : GPL-3+ Programming Lang: Javascr

Re: Feedback on 3.0 source format problems

2017-01-09 Thread Mattia Rizzolo
On Sun, Jan 08, 2017 at 01:05:37PM +0100, Johannes Schauer wrote: > Mattia, please see below for a pbuilder-specific question. Thanks for CCing me; I'm not following this thread anymore (as it surpassed the threshold above which I stop to dedicate my time to it), so please CC me if you need my inp

Re: unattended-upgrades by default

2017-01-09 Thread Steve McIntyre
Lars Wirzenius wrote: > >Distro development is difficult, let's go shopping. > >Sarcasm aside, here's a summary of the situation, as I understand it. >tldr: let's not despair, we have a mostly technical problem that's >simpler to solve than choosing a default editor, we can handle this. > >We'd lik

Re: unattended-upgrades by default

2017-01-09 Thread Steve McIntyre
Holger Levsen wrote: >On Fri, Jan 06, 2017 at 02:13:58PM +0100, Julian Andres Klode wrote: >> Two months ago, Steve wrote: >> > * enable it for installation via d-i by default. At installation >> [it being unattended-upgrades] >> What's the status of this? I do not like this idea, it interacts >> p

Re: Feedback on 3.0 source format problems

2017-01-09 Thread Ian Jackson
Sean Whitton writes ("Re: Feedback on 3.0 source format problems"): > I take it that only the maintainer is meant to look at the > merging-baseline, and everyone else looks at the interchange view. Anyone wanting to look at the patch stack can look at the interchange view. git blame, and git log,

Re: Bash different behaviour in jessie versus stretch (maybe a regression?)

2017-01-09 Thread Jeff Epler
I'm no bash expert, but I did take a quick look at bash release notes. One of the differences is called out under the heading "New Features In Bash" between 4.4-beta2 and 4.4-rc2: a. Using ${a[@]} or ${a[*]} with an array without any assigned elements when the nounset option is enabled no lo

Re: Converting to dgit

2017-01-09 Thread Ian Jackson
Sean Whitton writes ("Re: Converting to dgit"): > It's not so much the number of commands, but the distraction: thinking > about a patch queue while in the middle of thinking about actual bugs. > Personally, I find that mentally significant. People who are used to trying to make patch queues are u

Re: Feedback on 3.0 source format problems

2017-01-09 Thread Ian Jackson
Johannes Schauer writes ("Re: Feedback on 3.0 source format problems"): > Sbuild could do this cleanup itself if there was a way to > automatically determine whether the user would like their tree to be > patches applied or unapplied. This would have to be some kind of (perhaps package-specific) p

Re: Accepted ncc 2.8-2.1 (source amd64) into unstable

2017-01-09 Thread Ian Jackson
Holger Levsen writes ("Re: Accepted ncc 2.8-2.1 (source amd64) into unstable"): > (truncated) from debian-deve-changes@l.d.o: > > On Sat, Jan 07, 2017 at 09:33:44PM +, John Paul Adrian Glaubitz wrote: > > Source: ncc > > Version: 2.8-2.1 > > Changes: > > ncc (2.8-2.1) UNRELEASED; urgency=medi

Re: Python 3.6 in stretch

2017-01-09 Thread Ben Finney
Andrey Rahmatullin writes: > On Sun, Jan 08, 2017 at 06:55:45PM +0100, Galbo Branbert wrote: > > Thanks for the info, didn't know that the transition freeze was actually > > the version freeze for minor versions of Python. > A minor version upgrade would be 3.5.3 -> 3.5.4. 3.5 -> 3.6 is a lot of

Re: Feedback on 3.0 source format problems

2017-01-09 Thread Sean Whitton
On Mon, Jan 09, 2017 at 01:25:44PM +, Ian Jackson wrote: > Sean Whitton writes ("Re: Feedback on 3.0 source format problems"): > > My first worry is that pseudomerges are weird. In fact, I've never > > seen them outside of weird Debian git workflows :) Someone might > > look at the interchang

Re: Feedback on 3.0 source format problems

2017-01-09 Thread Johannes Schauer
Hi, Quoting Ian Jackson (2017-01-09 18:33:51) > Johannes Schauer writes ("Re: Feedback on 3.0 source format problems"): > > Sbuild could do this cleanup itself if there was a way to > > automatically determine whether the user would like their tree to be > > patches applied or unapplied. > > This

Re: Python 3.6 in stretch

2017-01-09 Thread Adam Borowski
On Tue, Jan 10, 2017 at 05:35:34AM +1100, Ben Finney wrote: > Andrey Rahmatullin writes: > > > On Sun, Jan 08, 2017 at 06:55:45PM +0100, Galbo Branbert wrote: > > > Thanks for the info, didn't know that the transition freeze was actually > > > the version freeze for minor versions of Python. > >

Bug#850744: ITP: libsub-info-perl -- helper module for inspecting subroutines

2017-01-09 Thread gregor herrmann
Package: wnpp Owner: gregor herrmann Severity: wishlist X-Debbugs-CC: debian-devel@lists.debian.org, debian-p...@lists.debian.org * Package name: libsub-info-perl Version : 0.002 Upstream Author : Chad Granum * URL : https://metacpan.org/release/Sub-Info * License

Re: Python 3.6 in stretch

2017-01-09 Thread Russ Allbery
Adam Borowski writes: > On Tue, Jan 10, 2017 at 05:35:34AM +1100, Ben Finney wrote: >> Galbo is referring correctly to the minor version, as specified in >> https://www.python.org/dev/peps/pep-0440/> and Semantic Versioning >> http://semver.org/>. >> So, “3.5.3” → “3.5.4” is a change of patch ve

Re: dput: Call for feedback: What should change? What should stay the same?

2017-01-09 Thread Barry Warsaw
On Dec 28, 2016, at 10:25 AM, Steve Langasek wrote: >Last I looked, the dcut command in dput doesn't support the 'dm' subcommand; >this led me to switching to dput-ng when I needed it. Same here, as I recently needed to `dcut dm` allow for a maintainer of a package I had been sponsoring while he

Re: dput: Call for feedback: What should change? What should stay the same?

2017-01-09 Thread Ben Finney
Barry Warsaw writes: > Unfortunately, the documentation you find on extending upload > permissions to DMs doesn't tell you that only dput-ng supports the dm > subcommand. Likewise, I'm having no luch finding comprehensive reference documentation for commands accepted by ‘dak’. Is there a bug re

Re: Python 3.6 in stretch

2017-01-09 Thread Ben Finney
Adam Borowski writes: > On Tue, Jan 10, 2017 at 05:35:34AM +1100, Ben Finney wrote: > > Andrey Rahmatullin writes: > > > > > On Sun, Jan 08, 2017 at 06:55:45PM +0100, Galbo Branbert wrote: > > > > Thanks for the info, didn't know that the transition freeze was > > > > actually the version freez

Re: Python 3.6 in stretch

2017-01-09 Thread Michael Lustfield
On Mon, Jan 9, 2017 at 1:54 PM, Ben Finney wrote: > Adam Borowski writes: > >> On Tue, Jan 10, 2017 at 05:35:34AM +1100, Ben Finney wrote: >> > Andrey Rahmatullin writes: >> > >> > > On Sun, Jan 08, 2017 at 06:55:45PM +0100, Galbo Branbert wrote: >> > > > Thanks for the info, didn't know that th

Aw: Re: Bash different behaviour in jessie versus stretch (maybe a regression?)

2017-01-09 Thread foo fighter
Hi Jeff, thank you very much for the insights and the time you took. I am glad that it is intended and no regression. Would I only have been able to think of the right search term. I even was not aware of the "here-strings" terminology (grml) ;-) Yours Lopiuh

Re: Feedback on 3.0 source format problems

2017-01-09 Thread Russell Stuart
On Mon, 2017-01-09 at 17:33 +, Ian Jackson wrote: > All of this applying and unapplying of patches around build > operations is complete madness if you ask me - but I don't see a > better approach given the constraints.  dgit sometimes ends up doing > this (and moans about it), which is even ma

Re: Python 3.6 in stretch

2017-01-09 Thread Simon McVittie
On Mon, 09 Jan 2017 at 14:28:07 -0800, Michael Lustfield wrote: > If 3.5 to 3.6 was a typical "minor version," our expectation > would be that the update comes with security updates and bug fixes > (not feature changes). That isn't semver. Semver minor version increments add features in a backward

Re: Python 3.6 in stretch

2017-01-09 Thread Barry Warsaw
On Jan 09, 2017, at 02:28 PM, Michael Lustfield wrote: >Python uses the microversion position for this. More importantly... is this >really a point that matters? Not really. In Debian terms you might think about the first digit as an epoch, the second digit as a major version and the third digi

Re: Feedback on 3.0 source format problems

2017-01-09 Thread Adam D. Barratt
On Mon, 2017-01-09 at 21:01 +0100, Johannes Schauer wrote: > Hi, > > Quoting Ian Jackson (2017-01-09 18:33:51) > > Johannes Schauer writes ("Re: Feedback on 3.0 source format problems"): > > > Sbuild could do this cleanup itself if there was a way to > > > automatically determine whether the user

Bug#850782: ITP: python-curio -- library for concurrent I/O with coroutines

2017-01-09 Thread Ben Finney
Package: wnpp Severity: wishlist Owner: Ben Finney * Package name: python-curio Version : 0.4 Upstream Author : David Beazley * URL : https://github.com/dabeaz/curio * License : BSD 3-clause Programming Lang: Python Description : library for concurrent

Re: Feedback on 3.0 source format problems

2017-01-09 Thread Johannes Schauer
Hi Mattia, Quoting Mattia Rizzolo (2017-01-09 11:27:30) > On Sun, Jan 08, 2017 at 01:05:37PM +0100, Johannes Schauer wrote: > > Mattia, please see below for a pbuilder-specific question. > > Thanks for CCing me; I'm not following this thread anymore (as it > surpassed the threshold above which I

Re: Feedback on 3.0 source format problems

2017-01-09 Thread Andrey Rahmatullin
On Tue, Jan 10, 2017 at 08:36:13AM +1000, Russell Stuart wrote: > To state the bleeding obvious, it arises because on day 1 Debian > decided to do the builds in the original source tree, then tries to > recover the original source at the end by running "debian/rules clean". > When I moved from rpm