[Pkg-javascript-devel] node-readable-stream_2.2.11-1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 12 Jun 2017 23:01:45 +0200 Source: node-readable-stream Binary: node-readable-stream Architecture: source Version: 2.2.11-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed

[Pkg-javascript-devel] Processing of node-readable-stream_2.2.11-1_source.changes

node-readable-stream_2.2.11-1_source.changes uploaded successfully to localhost along with the files: node-readable-stream_2.2.11-1.dsc node-readable-stream_2.2.11.orig.tar.gz node-readable-stream_2.2.11-1.debian.tar.xz node-readable-stream_2.2.11-1_source.buildinfo Greetings, You

[Pkg-javascript-devel] node-stream-http_2.7.1+dfsg-1_amd64.changes is NEW

binary:node-stream-http is NEW. binary:node-stream-http is NEW. source:node-stream-http 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 ple

[Pkg-javascript-devel] Processing of node-stream-http_2.7.1+dfsg-1_amd64.changes

node-stream-http_2.7.1+dfsg-1_amd64.changes uploaded successfully to localhost along with the files: node-stream-http_2.7.1+dfsg-1.dsc node-stream-http_2.7.1+dfsg.orig.tar.xz node-stream-http_2.7.1+dfsg-1.debian.tar.xz node-stream-http_2.7.1+dfsg-1_all.deb node-stream-http_2.7.1+dfsg-1_am

[Pkg-javascript-devel] node-grunt-known-options_1.1.0-1~bpo8+1_amd64.changes is NEW

binary:node-grunt-known-options is NEW. binary:node-grunt-known-options is NEW. source:node-grunt-known-options 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 h

[Pkg-javascript-devel] Processing of node-grunt-known-options_1.1.0-1~bpo8+1_amd64.changes

node-grunt-known-options_1.1.0-1~bpo8+1_amd64.changes uploaded successfully to localhost along with the files: node-grunt-known-options_1.1.0-1~bpo8+1.dsc node-grunt-known-options_1.1.0.orig.tar.gz node-grunt-known-options_1.1.0-1~bpo8+1.debian.tar.xz node-grunt-known-options_1.1.0-1~bpo8+

Re: [Pkg-javascript-devel] node-readable-stream_2.2.9-1_amd64.changes ACCEPTED into unstable, unstable

I looked at packaging readable-stream a while back. It seemed to provide "stream" fixed at a particular version. If the packages work with stream in our nodejs package, why bother to change? It is probably easier to use the node-readable-stream package now that it exists for new packages (instead

[Pkg-javascript-devel] node-stream-browserify_2.0.1-1_amd64.changes is NEW

binary:node-stream-browserify is NEW. binary:node-stream-browserify is NEW. source:node-stream-browserify 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

[Pkg-javascript-devel] Processing of node-stream-browserify_2.0.1-1_amd64.changes

node-stream-browserify_2.0.1-1_amd64.changes uploaded successfully to localhost along with the files: node-stream-browserify_2.0.1-1.dsc node-stream-browserify_2.0.1.orig.tar.gz node-stream-browserify_2.0.1-1.debian.tar.xz node-stream-browserify_2.0.1-1_all.deb node-stream-browserify_2.0.

[Pkg-javascript-devel] Bug#864605: marked as done (new upstream version (6.11))

Your message dated Mon, 12 Jun 2017 09:18:41 + with message-id and subject line Bug#864605: fixed in nodejs 6.11.0~dfsg-1 has caused the Debian Bug report #864605, regarding new upstream version (6.11) to be marked as done. This means that you claim that the problem has been dealt with. If th

[Pkg-javascript-devel] Bug#855018: marked as done (nodejs: autopkgtests always fail since 2016-11-02)

Your message dated Mon, 12 Jun 2017 09:18:41 + with message-id and subject line Bug#855018: fixed in nodejs 6.11.0~dfsg-1 has caused the Debian Bug report #855018, regarding nodejs: autopkgtests always fail since 2016-11-02 to be marked as done. This means that you claim that the problem has

[Pkg-javascript-devel] nodejs_6.11.0~dfsg-1_source.changes ACCEPTED into experimental

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 12 Jun 2017 10:07:10 +0200 Source: nodejs Binary: nodejs-dev nodejs nodejs-dbg nodejs-legacy Architecture: source Version: 6.11.0~dfsg-1 Distribution: experimental Urgency: medium Maintainer: Debian Javascript Main

[Pkg-javascript-devel] Processing of nodejs_6.11.0~dfsg-1_source.changes

nodejs_6.11.0~dfsg-1_source.changes uploaded successfully to localhost along with the files: nodejs_6.11.0~dfsg-1.dsc nodejs_6.11.0~dfsg.orig.tar.gz nodejs_6.11.0~dfsg-1.debian.tar.xz nodejs_6.11.0~dfsg-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.

Re: [Pkg-javascript-devel] node-readable-stream_2.2.9-1_amd64.changes ACCEPTED into unstable, unstable

Il 12/06/2017 10:00, Debian FTP Masters ha scritto: > Accepted: > > Format: 1.8 > Date: Sat, 27 May 2017 23:15:41 +0200 > Source: node-readable-stream > Binary: node-readable-stream > Architecture: source all > Version: 2.2.9-1 > Distribution: unstable > Urgency: low > Maintainer: Debian Javascrip

[Pkg-javascript-devel] node-readable-stream_2.2.9-1_amd64.changes ACCEPTED into unstable, unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 27 May 2017 23:15:41 +0200 Source: node-readable-stream Binary: node-readable-stream Architecture: source all Version: 2.2.9-1 Distribution: unstable Urgency: low Maintainer: Debian Javascript Maintainers Changed

[Pkg-javascript-devel] node-xterm_2.7.0+ds1-1_amd64.changes ACCEPTED into unstable, unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 06 Jun 2017 19:22:40 +0100 Source: node-xterm Binary: node-xterm libjs-xterm Architecture: source all Version: 2.7.0+ds1-1 Distribution: unstable Urgency: low Maintainer: Debian Javascript Maintainers Changed-By: