[Pkg-javascript-devel] node-array-uniq_1.0.3-1_amd64.changes is NEW

binary:node-array-uniq is NEW. source:node-array-uniq 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 signature and file hashes are valid), so please be patient. Packages are

[Pkg-javascript-devel] Processing of node-object.omit_2.0.1-1_amd64.changes

node-object.omit_2.0.1-1_amd64.changes uploaded successfully to localhost along with the files: node-object.omit_2.0.1-1.dsc node-object.omit_2.0.1.orig.tar.gz node-object.omit_2.0.1-1.debian.tar.xz node-object.omit_2.0.1-1_all.deb Greetings, Your Debian queue daemon (running on

[Pkg-javascript-devel] node-object.omit_2.0.1-1_amd64.changes is NEW

binary:node-object.omit is NEW. source:node-object.omit 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 signature and file hashes are valid), so please be patient. Packages are

[Pkg-javascript-devel] node-resolve-dir_1.0.0-1_amd64.changes is NEW

binary:node-resolve-dir is NEW. source:node-resolve-dir 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 signature and file hashes are valid), so please be patient. Packages are

[Pkg-javascript-devel] node-detect-file_0.1.0-1_amd64.changes is NEW

binary:node-detect-file is NEW. source:node-detect-file 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 signature and file hashes are valid), so please be patient. Packages are

[Pkg-javascript-devel] Processing of node-detect-file_0.1.0-1_amd64.changes

node-detect-file_0.1.0-1_amd64.changes uploaded successfully to localhost along with the files: node-detect-file_0.1.0-1.dsc node-detect-file_0.1.0.orig.tar.gz node-detect-file_0.1.0-1.debian.tar.xz node-detect-file_0.1.0-1_all.deb Greetings, Your Debian queue daemon (running on

[Pkg-javascript-devel] node-detect-file_0.1.0-1_amd64.changes ACCEPTED into unstable, unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 01 Nov 2016 10:59:54 +0530 Source: node-detect-file Binary: node-detect-file Architecture: source all Version: 0.1.0-1 Distribution: unstable Urgency: low Maintainer: Debian Javascript Maintainers

[Pkg-javascript-devel] Processing of node-array-uniq_1.0.3-1_amd64.changes

node-array-uniq_1.0.3-1_amd64.changes uploaded successfully to localhost along with the files: node-array-uniq_1.0.3-1.dsc node-array-uniq_1.0.3.orig.tar.gz node-array-uniq_1.0.3-1.debian.tar.xz node-array-uniq_1.0.3-1_all.deb Greetings, Your Debian queue daemon (running on host

[Pkg-javascript-devel] Processing of node-resolve-dir_1.0.0-1_amd64.changes

node-resolve-dir_1.0.0-1_amd64.changes uploaded successfully to localhost along with the files: node-resolve-dir_1.0.0-1.dsc node-resolve-dir_1.0.0.orig.tar.gz node-resolve-dir_1.0.0-1.debian.tar.xz node-resolve-dir_1.0.0-1_all.deb Greetings, Your Debian queue daemon (running on

[Pkg-javascript-devel] node-object.omit_2.0.1-1_amd64.changes ACCEPTED into unstable, unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 01 Nov 2016 12:15:28 +0530 Source: node-object.omit Binary: node-object.omit Architecture: source all Version: 2.0.1-1 Distribution: unstable Urgency: low Maintainer: Debian Javascript Maintainers

[Pkg-javascript-devel] node-array-uniq_1.0.3-1_amd64.changes ACCEPTED into unstable, unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 31 Oct 2016 17:53:05 + Source: node-array-uniq Binary: node-array-uniq Architecture: source all Version: 1.0.3-1 Distribution: unstable Urgency: low Maintainer: Debian Javascript Maintainers

Re: [Pkg-javascript-devel] 2 NMUs for node-findup-sync

That's a very helpful overview, and it makes it clear that it's quite a lot of work. Going through the latest news and the WNPP queue I can see that: - node-detect-file has been ACCEPTED into unstable this morning - node-cache-base has been ACCEPTED into unstable yesterday - node-os-homedir has

[Pkg-javascript-devel] Processing of node-base_0.11.1-1_amd64.changes

node-base_0.11.1-1_amd64.changes uploaded successfully to localhost along with the files: node-base_0.11.1-1.dsc node-base_0.11.1.orig.tar.gz node-base_0.11.1-1.debian.tar.xz node-base_0.11.1-1_all.deb Greetings, Your Debian queue daemon (running on host usper.debian.org) --

Re: [Pkg-javascript-devel] 2 NMUs for node-findup-sync

On Tue, Nov 01, 2016 at 10:47:05AM +0100, Paolo Greppi wrote: > On 30/10/2016 11:40, Mattia Rizzolo wrote: > > ok, but I find weird that you bumped std-ver 3.9.5 → 3.9.6 then… > > You could have gone all the way to 3.9.8, since no changes are needed > > for this package anyway. > >

Re: [Pkg-javascript-devel] 2 NMUs for node-findup-sync

On 30/10/2016 11:40, Mattia Rizzolo wrote: > also Vcs-Git please. OK >>> * debhelper compat 10 >>> * bump std-ver >> >> These I'd keep on hold until we do 0.4.3-1. > > ok, but I find weird that you bumped std-ver 3.9.5 → 3.9.6 then… > You could have gone all the way to 3.9.8, since no changes

Re: [Pkg-javascript-devel] 2 NMUs for node-findup-sync

On Tuesday 01 November 2016 03:09 PM, Paolo Greppi wrote: > That's a very helpful overview, and it makes it clear that it's quite a > lot of work. Yup, we have been doing it for some time as part of igg.me/at/debian-browserify campaign. > - node-os-homedir has an ITP bug

[Pkg-javascript-devel] node-base_0.11.1-1_amd64.changes is NEW

binary:node-base is NEW. source:node-base 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 signature and file hashes are valid), so please be patient. Packages are routinely

[Pkg-javascript-devel] Processing of node-require-relative_0.8.7-1_amd64.changes

node-require-relative_0.8.7-1_amd64.changes uploaded successfully to localhost along with the files: node-require-relative_0.8.7-1.dsc node-require-relative_0.8.7.orig.tar.gz node-require-relative_0.8.7-1.debian.tar.xz node-require-relative_0.8.7-1_all.deb Greetings, Your Debian

[Pkg-javascript-devel] Bug#842828: RFP: bootstrap4 -- HTML, CSS, and JS framework

Package: wnpp Severity: wishlist * Package name: bootstrap4 Version : 4.0.0-alpha5 Upstream Author : Mark Otto and Jacob Thornton * URL : https://v4-alpha.getbootstrap.com/ * License : MIT Programming Lang: HTML, CSS, Javascript Description : HTML, CSS,

[Pkg-javascript-devel] Bug#842824: [node-normalize-package-data] Please update to 2.3.2

Package: node-normalize-package-data Version: 0.2.2-1 Severity: wishlist --- Please enter the report below this line. --- Please update normalize-package-data to 2.3.2 as it is required by read-pkg which is required for Grunt. --- System information. --- Architecture: amd64 Kernel: Linux

[Pkg-javascript-devel] Processed: limit source to node-normalize-package-data, tagging 842824

Processing commands for cont...@bugs.debian.org: > limit source node-normalize-package-data Limiting to bugs with field 'source' containing at least one of 'node-normalize-package-data' Limit currently set to 'source':'node-normalize-package-data' > tags 842824 + pending Bug #842824

[Pkg-javascript-devel] node-require-relative_0.8.7-1_amd64.changes is NEW

binary:node-require-relative is NEW. source:node-require-relative 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 signature and file hashes are valid), so please be patient.

[Pkg-javascript-devel] Bug#842824: marked as done ([node-normalize-package-data] Please update to 2.3.2)

Your message dated Tue, 01 Nov 2016 15:51:57 + with message-id and subject line Bug#842824: fixed in node-normalize-package-data 2.3.5-1 has caused the Debian Bug report #842824, regarding [node-normalize-package-data] Please update to 2.3.2 to be marked

[Pkg-javascript-devel] Bug#841614: marked as done (node-es6-promise: FTBFS: compile-modules shows help)

Your message dated Tue, 1 Nov 2016 16:43:03 +0100 with message-id <20161101154303.dans6xuxa7nf5...@xanadu.blop.info> and subject line Re: node-es6-promise: FTBFS: compile-modules shows help has caused the Debian Bug report #841614, regarding node-es6-promise: FTBFS: compile-modules shows help to

[Pkg-javascript-devel] node-fs.realpath 1.0.0-1 MIGRATED to testing

FYI: The status of the node-fs.realpath source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 1.0.0-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a

[Pkg-javascript-devel] Processing of node-normalize-package-data_2.3.5-1_amd64.changes

node-normalize-package-data_2.3.5-1_amd64.changes uploaded successfully to localhost along with the files: node-normalize-package-data_2.3.5-1.dsc node-normalize-package-data_2.3.5.orig.tar.gz node-normalize-package-data_2.3.5-1.debian.tar.xz node-normalize-package-data_2.3.5-1_all.deb

[Pkg-javascript-devel] node-normalize-package-data_2.3.5-1_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 01 Nov 2016 16:29:04 +0100 Source: node-normalize-package-data Binary: node-normalize-package-data Architecture: source all Version: 2.3.5-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript

[Pkg-javascript-devel] node-jsonfile_2.4.0-1_amd64.changes ACCEPTED into unstable, unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 16 Oct 2016 19:49:08 +0200 Source: node-jsonfile Binary: node-jsonfile Architecture: source all Version: 2.4.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers

[Pkg-javascript-devel] node-everything.js_1.0.3-1_amd64.changes is NEW

binary:node-everything.js is NEW. source:node-everything.js 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 signature and file hashes are valid), so please be patient. Packages

[Pkg-javascript-devel] dependencies for complex Node.js modules: findup-sync

Starting a separate thread from https://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2016-November/014868.html ... On 01/11/2016 10:56, Pirate Praveen wrote: > On Tuesday 01 November 2016 03:09 PM, Paolo Greppi wrote: >> ... >> It would be helpful to (programmatically) cross-link the

[Pkg-javascript-devel] dependencies for complex Node.js modules: findup-sync

Starting a separate thread from https://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2016-November/014868.html ... On 01/11/2016 10:56, Pirate Praveen wrote: > On Tuesday 01 November 2016 03:09 PM, Paolo Greppi wrote: >> ... >> It would be helpful to (programmatically) cross-link the

[Pkg-javascript-devel] how to address node-lodash 841698

Hi I would like to contribute to this bug. The current package version in unstable is 2.4.1+dfsg-3. If I understand correctly https://wiki.debian.org/DebianMentorsFaq#What_does_.2BIBw-dfsg.2BIB0_in_the_version_string_mean.3F, we would issue the 2.4.1+dfsg-4 version. I have cloned the repo

[Pkg-javascript-devel] Processing of node-everything.js_1.0.3-1_amd64.changes

node-everything.js_1.0.3-1_amd64.changes uploaded successfully to localhost along with the files: node-everything.js_1.0.3-1.dsc node-everything.js_1.0.3.orig.tar.gz node-everything.js_1.0.3-1.debian.tar.xz node-everything.js_1.0.3-1_all.deb Greetings, Your Debian queue daemon