Re: [Pkg-javascript-devel] help with node-babel-runtime

On ബുധന്‍ 30 ആഗസ്റ്റ് 2017 11:20 വൈകു, Pirate Praveen wrote: > Hi, > > Can someone look at the autopkgtest failure on node-babel? require test > for babel-runtime is failing. Seems even npm installed babel-runtime fails this test as confirmed by Shanavas. So disabled the require test for

[Pkg-javascript-devel] node-color-name_1.1.3-1_amd64.changes is NEW

binary:node-color-name is NEW. binary:node-color-name is NEW. source:node-color-name 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

[Pkg-javascript-devel] Bug#754462: Bug#862051: nodejs (6.11.2~dfsg-1) experimental; urgency=medium

Philip Hands writes ("Bug#862051: nodejs (6.11.2~dfsg-1) experimental; urgency=medium"): > I guess that one could do something like moving the symlink into another > -legasy style package, and recomend that from the main package for one > release to keep upgrades happy. Then drop the

[Pkg-javascript-devel] Bug#873801: node-babel FTBFS without network access

Source: node-babel Version: 6.25.0+dfsg-1 Severity: serious Hi Maintainer Node-babel fails to build on a machine without external network access: ... npm install npm ERR! Linux 4.4.0-92-generic npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" npm ERR! node v6.11.2 npm ERR! npm v3.5.2

[Pkg-javascript-devel] Bug#873800: node-babylon FTBFS without network access

Source: node-babylon Version: 6.14.1-1 Severity: serious Hi Maintainer Node-babylon has a build dependency on nodejs-legacy which is no longer in the archive. With this dependency removed, the build fails on a machine without external network access: ... HOME=/tmp npm install babel-cli

[Pkg-javascript-devel] Processing of node-color-name_1.1.3-1_amd64.changes

node-color-name_1.1.3-1_amd64.changes uploaded successfully to localhost along with the files: node-color-name_1.1.3-1.dsc node-color-name_1.1.3.orig.tar.gz node-color-name_1.1.3-1.debian.tar.xz node-color-name_1.1.3-1_all.deb node-color-name_1.1.3-1_amd64.buildinfo Greetings,

[Pkg-javascript-devel] Processing of uglifyjs_2.8.29-3_amd64.changes

uglifyjs_2.8.29-3_amd64.changes uploaded successfully to localhost along with the files: uglifyjs_2.8.29-3.dsc uglifyjs_2.8.29-3.debian.tar.xz libjs-uglify_2.8.29-3_all.deb node-uglify_2.8.29-3_all.deb uglifyjs_2.8.29-3_amd64.buildinfo Greetings, Your Debian queue daemon

[Pkg-javascript-devel] uglifyjs_2.8.29-3_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 31 Aug 2017 12:58:17 +0200 Source: uglifyjs Binary: node-uglify libjs-uglify Architecture: source all Version: 2.8.29-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers

[Pkg-javascript-devel] Bug#754462: Bug#862051: nodejs (6.11.2~dfsg-1) experimental; urgency=medium

2017-08-31 13:25 GMT+02:00 Ian Jackson : > Philip Hands writes ("Bug#862051: nodejs (6.11.2~dfsg-1) experimental; > urgency=medium"): > > I guess that one could do something like moving the symlink into another > > -legasy style package, and recomend that from the

[Pkg-javascript-devel] Bug#754462: Bug#754462: Bug#862051: nodejs (6.11.2~dfsg-1) experimental; urgency=medium

Hi, Le 31/08/2017 à 13:52, Jérémy Lal a écrit : > How about printing a "nice" warning explaining it would be a good idea to > move to /usr/bin/node ? Then in next next release drop the nodejs symlink. May I suggest to have /usr/bin/nodejs print a nice deprecation warning to use /usr/bin/node,

[Pkg-javascript-devel] Bug#754462: Bug#862051: nodejs (6.11.2~dfsg-1) experimental; urgency=medium

On Thu, 31 Aug 2017, Jérémy Lal wrote: > How about printing a "nice" warning explaining it would be a good idea to > move to /usr/bin/node ? That will break scripts that do: x=$(nodejs somescript) Or even ./somescript when that has a #!/usr/bin/env nodejs shebang. > Then in next next release

[Pkg-javascript-devel] Bug#754462: Bug#862051: nodejs (6.11.2~dfsg-1) experimental; urgency=medium

Le jeudi, 31 août 2017, 12.25:50 h CEST Ian Jackson a écrit : > Philip Hands writes ("Bug#862051: nodejs (6.11.2~dfsg-1) experimental; urgency=medium"): > > I guess that one could do something like moving the symlink into another > > -legacy style package, and recomend that from the main package

[Pkg-javascript-devel] Bug#754462: Bug#862051: nodejs (6.11.2~dfsg-1) experimental; urgency=medium

Le jeudi, 31 août 2017, 13.58:23 h CEST Thorsten Glaser a écrit : > Do not drop it before *after* the next release, so people have, > at the very least, one full release of time to switch their > scripts in a way that works with both the old and new names > *first*, gradually. They have Stretch

[Pkg-javascript-devel] Bug#754462: Bug#754462: Bug#862051: nodejs (6.11.2~dfsg-1) experimental; urgency=medium

On Thu, 31 Aug 2017, Julien Puydt wrote: > May I suggest to have /usr/bin/nodejs print a nice deprecation warning > to use /usr/bin/node, and just *never* remove it? On Thu, 31 Aug 2017, Didier 'OdyX' Raboud wrote: > Le jeudi, 31 août 2017, 13.52:00 h CEST Jérémy Lal a écrit : > > How about

Re: [Pkg-javascript-devel] Bug#873801: node-babel FTBFS without network access

Control: severity -1 important On വ്യാഴം 31 ആഗസ്റ്റ് 2017 03:37 വൈകു, Graham Inggs wrote: > Node-babel fails to build on a machine without external network access: This requires packages outside debian to build and hence it is added to contrib and not main. This is a temporary step until we

[Pkg-javascript-devel] Processing of node-exports-loader_0.6.4-1_amd64.changes

node-exports-loader_0.6.4-1_amd64.changes uploaded successfully to localhost along with the files: node-exports-loader_0.6.4-1.dsc node-exports-loader_0.6.4.orig.tar.gz node-exports-loader_0.6.4-1.debian.tar.xz node-exports-loader_0.6.4-1_all.deb

[Pkg-javascript-devel] Bug#754462: Bug#862051: nodejs (6.11.2~dfsg-1) experimental; urgency=medium

On Thursday, 31 August 2017 13:58:23 CEST Thorsten Glaser wrote: > > How about printing a "nice" warning explaining it would be a good idea to > > move to /usr/bin/node ? > > That will break scripts that do: > > x=$(nodejs somescript) This kind of script won't break if the deprecation warning is

[Pkg-javascript-devel] Bug#754462: Bug#862051: Bug#754462: Bug#862051: nodejs (6.11.2~dfsg-1) experimental; urgency=medium

> "Julien" == Julien Puydt writes: Julien> Hi, Le 31/08/2017 à 13:52, Jérémy Lal a écrit : >> How about printing a "nice" warning explaining it would be a good >> idea to move to /usr/bin/node ? Then in next next release drop >> the nodejs symlink.

[Pkg-javascript-devel] Bug#754462: Bug#862051: nodejs (6.11.2~dfsg-1) experimental; urgency=medium

> "Dominique" == Dominique Dumont writes: Dominique> On Thursday, 31 August 2017 13:58:23 CEST Thorsten Glaser wrote: >> > How about printing a "nice" warning explaining it would be a >> good idea to > move to /usr/bin/node ? >> >> That will break

[Pkg-javascript-devel] [bts-link] source package node-shell-quote

# # bts-link upstream status pull for source package node-shell-quote # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #873148 (http://bugs.debian.org/873148) # Bug title: Fails to properly

[Pkg-javascript-devel] Processed: Re: node-babel FTBFS without network access

Processing control commands: > severity -1 normal Bug #873801 [src:node-babel] node-babel FTBFS without network access Severity set to 'normal' from 'serious' -- 873801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873801 Debian Bug Tracking System Contact ow...@bugs.debian.org with

[Pkg-javascript-devel] Bug#873801: node-babel FTBFS without network access

Control: severity -1 normal On Thu, 31 Aug 2017 12:07:37 +0200 Graham Inggs wrote: > Node-babel fails to build on a machine without external network access: This package is in contrib and not main. "The contrib archive area contains supplemental packages intended to work

[Pkg-javascript-devel] jquery-minicolors 2.2.6+dfsg-2 MIGRATED to testing

FYI: The status of the jquery-minicolors source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 2.2.6+dfsg-2 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple

[Pkg-javascript-devel] node-color-name_1.1.3-1_source.changes REJECTED

Source-only uploads to NEW are not allowed. binary:node-color-name is NEW. source:node-color-name is NEW. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns. -- Pkg-javascript-devel

[Pkg-javascript-devel] Processing of node-color-name_1.1.3-1_source.changes

node-color-name_1.1.3-1_source.changes uploaded successfully to localhost along with the files: node-color-name_1.1.3-1.dsc node-color-name_1.1.3.orig.tar.gz node-color-name_1.1.3-1.debian.tar.xz node-color-name_1.1.3-1_source.buildinfo Greetings, Your Debian queue daemon

[Pkg-javascript-devel] Processing of node-p-locate_2.0.0-1_amd64.changes

node-p-locate_2.0.0-1_amd64.changes uploaded successfully to localhost along with the files: node-p-locate_2.0.0-1.dsc node-p-locate_2.0.0.orig.tar.gz node-p-locate_2.0.0-1.debian.tar.xz node-p-locate_2.0.0-1_all.deb node-p-locate_2.0.0-1_amd64.buildinfo Greetings, Your Debian