Bug#841158: ITP: node-is-arrayish -- Determines if an object can be used as an array

Package: wnpp Severity: wishlist Owner: Shanavas M X-Debbugs-CC: debian-devel@lists.debian.org * Package name : node-is-arrayish Version : 0.3.0 Upstream Author: Qix (http://github.com/qix-) * URL : https://github.com/qix-/node-is-arrayish#readm

Bug#841159: ITP: node-filename-regex -- Regular expression for matching file names, with or without extension

Package: wnpp Severity: wishlist Owner: Sruthi Chandran X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-filename-regex Version : 2.0.0 Upstream Author : Jon Schlinkert (https://github.com/jonschlinkert) * URL : https://github.com/regexps/filename-regex

Re: When should we https our mirrors?

On 10/17/2016 08:48 PM, Cyril Brulebois wrote: > Philipp Kern (2016-10-17): >> On 10/17/2016 05:39 PM, Cyril Brulebois wrote: >>> AFAICT from a recent https deployment, apt will perform a TLS handshake >>> for each and every file it downloads from the mirror; including indices, >>> translations, p

Re: Package name conflict question

Hi Adam, Thanks for your reply. Although these packages are not API-compatible, they are using the same installation path and file name; therefore, I think "Conflict:" section is needed. -- Sun-Ze Lin (林上智) 2016-10-17 2:27 GMT+08:00 Adam Borowski : > On Sun, Oct 16, 2016 at 10:36:31AM +0200

kurze downtime der jenkins server um 12:00

Hi folks, zur RAM Erweiterung gibt es heute um 12:00 eine kurze Downtime der Jenkins Server invde8i001 mbrjenkins01 nvode7i001 semde7i001 sprjenkins01 Regards Harri

Re: Package name conflict question

On Tue, Oct 18, 2016 at 03:36:56PM +0800, SZ Lin (林上智) wrote: > Although these packages are not API-compatible, they are using the > same installation path and file name; therefore, I think "Conflict:" > section is needed. The problem with this is that this prevents our users from having both of t

Re: Package name conflict question

"SZ Lin (林上智)" writes: > Although these packages are not API-compatible, they are using the > same installation path and file name; therefore, I think "Conflict:" > section is needed. Note that Policy explicitly forbids using "Conflicts" in this case, see the first paragraph in [1]. [1]

Re: Bug#841099: ITP: node-has-values -- Returns true if any values exist, false if empty

❦ 18 octobre 2016 09:08 +0800, Paul Wise  : >> These are distinct packages, with distinct version numbers, and packages >> will need to declare (potentially versioned) dependencies on them. > > Has anyone involved in the node ecosystem tried to talk the respective > upstreams into creating a stan

Re: Package name conflict question

Hi Ansgar, Thanks for your reply. I think this situation meets the condition. The case of two programs having the same functionality but different > implementations is handled via "alternatives" or the "Conflicts" mechanism. These two programs having the same functionality - implementation of

Bug#841167: ITP: node-normalize-path -- Normalize file path slashes to be unix-like forward slashes

Package: wnpp Severity: wishlist Owner: Sruthi Chandran X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-normalize-path Version : 2.0.1 Upstream Author : Jon Schlinkert (https://github.com/jonschlinkert) * URL : https://github.com/jonschlinkert/normaliz

Re: Debian and the node-js eco system

On 2016-10-17 21:25, Geert Stappers wrote: > Thing I would like to see, is that all those "node js package" get > their own component. ( 'main', 'contrib' and 'non-free' are components ) I personally dislike the Node.js nano-packaging approach, but there is no fundamental reason why this dislike o

Re: Package name conflict question

On 2016-10-18 9:52, SZ Lin wrote: I think this situation meets the condition. The case of two programs having the same functionality but different implementations is handled via "alternatives" or the "Conflicts" mechanism. These two programs having the same functionality - implementation of R

Bug#841170: ITP: tendermint-go-logger -- Tendermint Go logging library

Package: wnpp Severity: wishlist Owner: Alessio Treglia * Package name: tendermint-go-logger Version : Git snapshot Upstream Author : Tendermint project * URL : http://www.tendermint.com/ * License : Apache-2.0 Programming Lang: Golang Description : Ten

Bug#841172: ITP: node-glob-parent -- Strips glob magic from a string to provide the parent path

Package: wnpp Severity: wishlist Owner: Sruthi Chandran X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-glob-parent Version : 3.0.0 Upstream Author : Elan Shanker * URL : https://github.com/es128/glob-parent * License : ISC Programming Lang:

Bug#841175: ITP: python-dirq -- Python Directory Based Queue.

Package: wnpp Severity: wishlist Owner: Alvaro Lopez Garcia * Package name: python-dirq Version : 1.7.1 Upstream Author : Konstantin Skaburskas * URL : https://github.com/cern-mig/python-dirq * License : Apache2 Programming Lang: Python Description : P

Bug#841176: ITP: node-inflight -- Add callbacks to requests in flight to avoid async duplication

Package: wnpp Severity: wishlist Owner: Pirate Praveen X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-inflight Version : 1.0.6 Upstream Author : Isaac Z. Schlueter (http://blog.izs.me/) * URL : https://github.com/isaacs/inflight * License : I

Bug#841177: ITP: node-is-dotfile -- Return true if a file path is (or has) a dotfile

Package: wnpp Severity: wishlist Owner: Sruthi Chandran X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-is-dotfile Version : 1.0.2 Upstream Author : Jon Schlinkert (https://github.com/jonschlinkert) * URL : https://github.com/jonschlinkert/is-dotfile *

Bug#841178: ITP: nutsqlite -- dietary nutrition analysis software

Package: wnpp Severity: wishlist Owner: "Iain R. Learmonth" * Package name: nutsqlite Version : 1.9.9.2 Upstream Author : Jim Jozwiak * URL : http://nut.sourceforge.net/ * License : GPL-2 Programming Lang: Tcl/Tk Description : Dietary nutrition analysis

Bug#820036: No bug mentioning a Debian KEK and booting use it.

Peter Dolding writes ("Bug#820036: No bug mentioning a Debian KEK and booting use it."): > Yes it one thing to get shim signed by Microsoft. Do remember > Microsoft is free to push out updates to the The Forbidden Signatures > Database(dbx). > > [etc.] I'm afraid I can't make sense of this. Y

Re: [pkg-gnupg-maint] Bug#840669: Bug#840669: Beware of leftover gpg-agent processes

Daniel Kahn Gillmor writes ("Re: [pkg-gnupg-maint] Bug#840669: Bug#840669: Beware of leftover gpg-agent processes"): > On Sat 2016-10-15 11:21:29 -0400, Ian Jackson wrote: > > 1. gnupg1-compatible authorisation lifetime: > > I believe this is a deliberate change in semantics from the upstream > G

Re: Package name conflict question

Lars Wirzenius writes ("Re: Package name conflict question"): > I don't have a solution for this. The ideal solution would be for one > or both upstream developers to rename their library. However, that's > only ideal in the long run, since it requires every program that uses > the libraries to be

Re: Bug#820036: No bug mentioning a Debian KEK and booting use it.

On Tue, Oct 18, 2016 at 7:36 PM, Ian Jackson wrote: > I'm afraid I can't make sense of this. You have posted it to > debian-devel, but without any kind of sensible explanation of the > context. It was posted to bug #820036, which is tracking Debian support for secure boot. Peter was advocating q

Re: kurze downtime der jenkins server um 12:00

Sorry for the noise, that was a bad To: address. Regards Harri On 10/18/2016 09:14 AM, Harald Dunkel wrote: > Hi folks, > > zur RAM Erweiterung gibt es heute um 12:00 eine kurze Downtime > der Jenkins Server > > invde8i001 > mbrjenkins01 > nvode7i001 > semde7i001 >

Re: Is missing SysV-init support a bug?

On 2016-10-17 at 17:53, Bart Schouten wrote: > Nikolaus Rath schreef op 17-10-2016 18:26: > >> On Oct 17 2016, Bart Schouten wrote: >> >>> (And I write SystemD with caps because that makes it easier to >>> read, people invented capitals for a reason). >> >> What would you think some people con

Re: dput: Call for testers: replacing ‘/usr/bin/gpg’ with GPGME

Ben Finney writes: > I am preparing a new version of ‘dput’ that stops using ‘/usr/bin/gpg’, > and instead uses the GPGME library for GnuPG operations. > […] > If your packaging workflow has unusual signing practices, or an unusual > GnuPG configuration, your help will be especially valuable to

Bug#841196: ITP: node-os-homedir -- Node.js 4 `os.homedir()` ponyfill

Package: wnpp Severity: wishlist Owner: Pirate Praveen X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-os-homedir Version : 1.0.2 Upstream Author : Sindre Sorhus (sindresorhus.com) * URL : https://github.com/sindresorhus/os-homedir#readme * License

Bug#841200: ITP: node-is-primitive -- Returns `true` if the value is a primitive

Package: wnpp Severity: wishlist Owner: Sruthi Chandran X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-is-primitive Version : 2.0.0 Upstream Author : Jon Schlinkert (https://github.com/jonschlinkert) * URL : https://github.com/jonschlinkert/is-primiti

Bug#841202: ITP: node-pify -- Promisify a callback-style function

Package: wnpp Severity: wishlist Owner: Pirate Praveen X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-pify Version : 2.3.0 Upstream Author : Sindre Sorhus (sindresorhus.com) * URL : https://github.com/sindresorhus/pify * License : Expat Pro

Bug#841206: ITP: node-fs.realpath -- Use node's fs.realpath

Package: wnpp Severity: wishlist Owner: Sruthi Chandran X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-fs.realpath Version : 1.0.0 Upstream Author : Isaac Z. Schlueter (http://blog.izs.me/) * URL : https://github.com/isaacs/fs.realpath#readme * Licen

Re: Bug#841196: ITP: node-os-homedir -- Node.js 4 `os.homedir()` ponyfill

Pirate Praveen wrote: >-=-=-=-=-=- > >Package: wnpp >Severity: wishlist >Owner: Pirate Praveen >X-Debbugs-CC: debian-devel@lists.debian.org > >* Package name: node-os-homedir > Version : 1.0.2 > Upstream Author : Sindre Sorhus >(sindresorhus.com) >* URL : https://github.

Bug#841212: ITP: node-signal-exit -- when you want to fire an event no matter how a process exits

Package: wnpp Severity: wishlist Owner: Sruthi Chandran X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-signal-exit Version : 3.0.1 Upstream Author : Ben Coe * URL : https://github.com/tapjs/signal-exit * License : ISC Programming Lang: Java

Re: Bug#841196: ITP: node-os-homedir -- Node.js 4 `os.homedir()` ponyfill

On Tue, Oct 18, 2016 at 03:27:46PM +0100, Steve McIntyre wrote: > The code, well... > > if (process.platform === 'linux') { > return home || (process.getuid() === 0 ? '/root' : (user ? > '/home/' + user : null)); > } > > Things are more complicated than that. What exact

Re: Bug#841196: ITP: node-os-homedir -- Node.js 4 `os.homedir()` ponyfill

On Tuesday 18 October 2016 07:57 PM, Steve McIntyre wrote: > /me args at YA tiny JS lump. It's tiny, and wrong. Probably. But it's > difficult to tell with such a small "Description". Please add some > useful text. This is packaged because its a dependency for grunt. > The code, well... > >

Re: Bug#841196: ITP: node-os-homedir -- Node.js 4 `os.homedir()` ponyfill

On Tue, Oct 18, 2016 at 08:40:49PM +0530, Pirate Praveen wrote: >On Tuesday 18 October 2016 07:57 PM, Steve McIntyre wrote: >> /me args at YA tiny JS lump. It's tiny, and wrong. Probably. But it's >> difficult to tell with such a small "Description". Please add some >> useful text. > >This is packa

Re: Bug#841196: ITP: node-os-homedir -- Node.js 4 `os.homedir()` ponyfill

On Tuesday 18 October 2016 08:27 PM, Lars Wirzenius wrote: > On Tue, Oct 18, 2016 at 03:27:46PM +0100, Steve McIntyre wrote: >> The code, well... >> >> if (process.platform === 'linux') { >> return home || (process.getuid() === 0 ? '/root' : (user ? >> '/home/' + user : null)); >

Re: Bug#841196: ITP: node-os-homedir -- Node.js 4 `os.homedir()` ponyfill

On Tuesday 18 October 2016 08:45 PM, Steve McIntyre wrote: > That doesn't fix (or excuse) poor packaging, though. Are you saying this is RC? We have different level for bugs, this would be wishlist. I don't mind someone writing a better description. > Life's too short to go and fix all the crap i

Re: Bug#841196: ITP: node-os-homedir -- Node.js 4 `os.homedir()` ponyfill

On Tuesday 18 October 2016 08:27 PM, Lars Wirzenius wrote: > This is so wrong, I would like to ask that this package not be allowed > into Debian until it's fixed. I agree this could be marked RC and stopped from going to a stable release. But do we stop accepting new packages in unstable because

Re: Bug#841196: ITP: node-os-homedir -- Node.js 4 `os.homedir()` ponyfill

On Tue, Oct 18, 2016 at 08:49:27PM +0530, Pirate Praveen wrote: > On Tuesday 18 October 2016 08:27 PM, Lars Wirzenius wrote: > > This is so wrong, I would like to ask that this package not be allowed > > into Debian until it's fixed. > > This is already reported upstream > https://github.com/sindr

Re: Bug#841196: ITP: node-os-homedir -- Node.js 4 `os.homedir()` ponyfill

❦ 18 octobre 2016 17:57 +0300, Lars Wirzenius  : >> The code, well... >> >> if (process.platform === 'linux') { >> return home || (process.getuid() === 0 ? '/root' : (user ? >> '/home/' + user : null)); >> } >> >> Things are more complicated than that. What exactly is th

Re: Bug#841196: ITP: node-os-homedir -- Node.js 4 `os.homedir()` ponyfill

On Tue, Oct 18, 2016 at 08:59:20PM +0530, Pirate Praveen wrote: > On Tuesday 18 October 2016 08:27 PM, Lars Wirzenius wrote: > > This is so wrong, I would like to ask that this package not be allowed > > into Debian until it's fixed. > > I agree this could be marked RC and stopped from going to a

Re: Bug#841196: ITP: node-os-homedir -- Node.js 4 `os.homedir()` ponyfill

On Tue, Oct 18, 2016 at 08:40:49PM +0530, Pirate Praveen wrote: > I don't particularly enjoy doing this either. Please direct your anger > at the nodejs developers. I'm doing this only because the packages I > care (diaspora and gitlab won't be accepted in main, unless I build > libjs-handlebars an

Re: Bug#841196: ITP: node-os-homedir -- Node.js 4 `os.homedir()` ponyfill

On Tue, Oct 18, 2016 at 04:15:50PM +0100, Steve McIntyre wrote: >... > Life's too short to go and fix all the crap in the world personally, > but we can keep certain minimum standards for what we as a group allow > into Debian. :-( What policies and processes should ensure these minimum standards?

Re: Bug#841196: ITP: node-os-homedir -- Node.js 4 `os.homedir()` ponyfill

* Lars Wirzenius , 2016-10-18, 17:57: if (process.platform === 'linux') { return home || (process.getuid() === 0 ? '/root' : (user ? '/home/' + user : null)); } Things are more complicated than that. What exactly is this code meant to be used for? This is so w

Re: Bug#841196: ITP: node-os-homedir -- Node.js 4 `os.homedir()` ponyfill

Pirate Praveen wrote: >-=-=-=-=-=- > >On Tuesday 18 October 2016 08:45 PM, Steve McIntyre wrote: >> That doesn't fix (or excuse) poor packaging, though. > >Are you saying this is RC? We have different level for bugs, this would >be wishlist. I don't mind someone writing a better description. I'd b

Re: Bug#841196: ITP: node-os-homedir -- Node.js 4 `os.homedir()` ponyfill

On Wed, Oct 19, 2016 at 12:03 AM, Jakub Wilk wrote: > it's only used as a fallback for nodejs < 4. Debian currently has 4.6.0. Does this mean the ITP can be closed? -- bye, pabs https://wiki.debian.org/PaulWise

Re: Bug#841196: ITP: node-os-homedir -- Node.js 4 `os.homedir()` ponyfill

On Tue, Oct 18, 2016 at 06:03:28PM +0200, Jakub Wilk wrote: > The WTFness of this code is certainly way above what we're normally used to, > but (AIUI) it's only used as a fallback for nodejs < 4. Debian currently has > 4.6.0. In that case, perhaps this package isn't needed in Debian at all? > >

Re: Bug#820036: No bug mentioning a Debian KEK and booting use it.

Paul Wise writes ("Re: Bug#820036: No bug mentioning a Debian KEK and booting use it."): > On Tue, Oct 18, 2016 at 7:36 PM, Ian Jackson wrote: > > I'm afraid I can't make sense of this. You have posted it to > > debian-devel, but without any kind of sensible explanation of the > > context. > > I

Re: Bug#841196: ITP: node-os-homedir -- Node.js 4 `os.homedir()` ponyfill

Quoting Lars Wirzenius (2016-10-18 17:44:50) > On Tue, Oct 18, 2016 at 08:59:20PM +0530, Pirate Praveen wrote: > > On Tuesday 18 October 2016 08:27 PM, Lars Wirzenius wrote: > > > This is so wrong, I would like to ask that this package not be allowed > > > into Debian until it's fixed. > > > > I a

Re: Bug#841196: ITP: node-os-homedir -- Node.js 4 `os.homedir()` ponyfill

* Lars Wirzenius , 2016-10-18, 19:14: The WTFness of this code is certainly way above what we're normally used to, but (AIUI) it's only used as a fallback for nodejs < 4. Debian currently has 4.6.0. In that case, perhaps this package isn't needed in Debian at all? You would have to patch the

Re: Bug#841196: ITP: node-os-homedir -- Node.js 4 `os.homedir()` ponyfill

Quoting Lars Wirzenius : Even though I object to this one package (until it's fixed upstream), I don't want to discourage you from working on this. It's important work (because diaspora and gitlab are important pieces of free software). It's unfortunate you get to be the focal point of a lot of n

Bug#841225: ITP: node-hosted-git-info -- Provides metadata and conversions from repository urls for Github, Bitbucket and Gitlab

Package: wnpp Severity: wishlist Owner: Sruthi Chandran X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-hosted-git-info Version : 2.1.5 Upstream Author : Rebecca Turner (http://re-becca.org) * URL : https://github.com/npm/hosted-git-info * License

Re: Bug#841196: ITP: node-os-homedir -- Node.js 4 `os.homedir()` ponyfill

On 10/18/2016 05:29 PM, Pirate Praveen wrote: > On Tuesday 18 October 2016 08:27 PM, Lars Wirzenius wrote: >> This is so wrong, I would like to ask that this package not be allowed >> into Debian until it's fixed. > > I agree this could be marked RC and stopped from going to a stable > release. Bu

Re: Bug#841196: ITP: node-os-homedir -- Node.js 4 `os.homedir()` ponyfill

On 10/18/2016 06:28 PM, Jakub Wilk wrote: > * Lars Wirzenius , 2016-10-18, 19:14: >>> The WTFness of this code is certainly way above what we're normally >>> used to, but (AIUI) it's only used as a fallback for nodejs < 4. >>> Debian currently has 4.6.0. >> In that case, perhaps this package isn't

Re: Bug#841196: ITP: node-os-homedir -- Node.js 4 `os.homedir()` ponyfill

On Tuesday 18 October 2016 10:03 PM, Christian Seiler wrote: > If the package so clearly fails to achieve its _only_ goal as in > this case, I think it's a good idea to delay accepting it into the > archive until it's fixed. > > That said, I don't want to discourage you, and to provide something >

Re: node-os-homedir_1.0.2-1_amd64.changes is NEW

On Tuesday 18 October 2016 11:00 PM, Debian FTP Masters wrote: > binary:node-os-homedir is NEW. > source:node-os-homedir is NEW. > > Your package has been put into the NEW queue, which requires manual action > from the ftpteam to process. The upload was otherwise valid (it had a good > OpenPGP sig

Re: Is missing SysV-init support a bug?

Not subscribed so this will break threading. On 2016-10-17 at 17:53, Bart Schouten wrote: I would consider that bigotry as SystemD is short pretty much for System Daemon. While this is a reasonable point, it doesn't invalidate Nikolas' point: that the people behind the systemd project A: d

Re: When should we https our mirrors?

Tollef Fog Heen wrote: > ]] Paul Tagliamonte > > > So, when are we going to push this? If not now, what criteria need to > > be met? Why can't we https-ify the default CDN mirror today? > > The usual crypto answer: because key handling is hard. > > Doing this for the per-country mirrors means t

Re: Is missing SysV-init support a bug?

On Tue, Oct 18, 2016 at 07:34:28PM +0200, Xen wrote: > If that is the case then they have enbedded hostility into their name simply > becaus eit offends normal grammar roles. I don't that's it at all. The reason many people react to the SystemD spelling is becuase, for some years now, trolls use

Re: When should we https our mirrors?

On Oct 17, Ian Campbell wrote: > Have we gotten to the point where we consider deb.d.o suitable for > production use? The web page still says Experimental (so I would assume I do not think that it is appropriate for general use, since at least one of the CDNs backing it lacks nodes in many (most

Re: [pkg-gnupg-maint] Bug#840669: Bug#840669: Beware of leftover gpg-agent processes

On Tue 2016-10-18 07:44:43 -0400, Ian Jackson wrote: > Daniel Kahn Gillmor writes ("Re: [pkg-gnupg-maint] Bug#840669: Bug#840669: > Beware of leftover gpg-agent processes"): >> On Sat 2016-10-15 11:21:29 -0400, Ian Jackson wrote: >> > 1. gnupg1-compatible authorisation lifetime: >> >> I believe t

Re: [Pkg-dns-devel] Bug#833309: "Browserified" stuff (knot-resolver-module-http: please package embedded epoch.js separately)

>> On 14458 March 1977, W. Martin Borgert wrote: >> > If I package a compiler and put y.tab.c in the package, drop >> > grammar.y in d/m-s/, would it be OK or not? >> If you come up with a good reason for it, yes. But I doubt you would >> find one here. > Let's say I need a special tool to compile

Re: Is missing SysV-init support a bug?

On Tue, Oct 18, 2016 at 11:23 AM, Lars Wirzenius wrote: > On Tue, Oct 18, 2016 at 07:34:28PM +0200, Xen wrote: >> If that is the case then they have enbedded hostility into their name simply >> becaus eit offends normal grammar roles. > > I don't that's it at all. > > The reason many people react

Re: Is missing SysV-init support a bug?

On Oct 18 2016, Cameron Norman wrote: > On Tue, Oct 18, 2016 at 11:23 AM, Lars Wirzenius wrote: >> On Tue, Oct 18, 2016 at 07:34:28PM +0200, Xen wrote: >>> If that is the case then they have enbedded hostility into their name simply >>> becaus eit offends normal grammar roles. >> >> I don't that'

Re: Is missing SysV-init support a bug?

Cameron Norman writes: > Those reading so much into such a small and understandable > capitalization mistake (SystemV -> SystemD) should learn to take > themselves less seriously and view things from different perspectives. You will find that when you point out the correct spelling to those who

Re: Is missing SysV-init support a bug?

On Tue, Oct 18, 2016 at 08:11:21PM -0700, Russ Allbery wrote: > You will find that when you point out the correct spelling to those who > use this one, the response is not "oh, whoops," like it would be for a > mistake. Rather, it's usually a rant of surprising vitriol, a bunch of > bizarrely cons