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

[Pirate Praveen]

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 with the Debian distribution, but which require software outside of
the distribution to either build or function."

https://www.debian.org/doc/debian-policy/ch-archive.html#s-contrib

It requires packages from npmjs.com to build.

But this is a temporary arrangement to bootstrap as it has a circular
dependency on node-babylon.



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Debian Bug Tracking System]

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 problems

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Debian testing watch]

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 times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[bts-link-upstream]

#
# 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 escape the ;, {, }, <, and > characters
#  * https://github.com/substack/node-shell-quote/issues/31
#  * remote status changed: (?) -> open
usertags 873148 + status-open

thanks

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Sam Hartman]

> "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 scripts that do:
>> 
>> x=$(nodejs somescript)

Dominique> This kind of script won't break if the deprecation
Dominique> warning is sent to STDERR


Sigh.
I wish I had seen your message before your earlier reply.
This breaks too in more complex situations involving ssh, things like
expect scripts and the like.
There are cases where people mix stderr and stdout.  There are cases
where people treat any unexpected output on stderr as a failure in
automated scripts.

The next level you can look at is considering whether /dev/stdin in a
tty and printing the warning to either stderr or /dev/tty only in that
case.
And that will reduce the breakage but not remove it.
And yes, when you actually have something it's important to deprecate,
accepting some level of breakage and adopting one of those strategies is
the right thing.

It's just not worth it in this case.
People who use more than Debian are very quickly going to learn that
/usr/bin/node is preferred to /usr/bin/nodejs.
As several people have already pointed out we've far exceeded the amount
of effort in considering whether to deprecate or remove the link that
will be spent maintaining the link until the end of time.
In one sense we've already lost:-)

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Sam Hartman]

> "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.

Julien> May I suggest to have /usr/bin/nodejs print a nice
Julien> deprecation warning to use /usr/bin/node, and just *never*
Julien> remove it?

Having it print a deprecation warning will break pipes or other
situations where stdout and stderr are captured.
I'd just use a symlink.
We have release notes and debian/news for warnings if we believe that's
the right approach.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Dominique Dumont]

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 sent to STDERR

All the best

-- 
 https://github.com/dod38fr/   -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/  -o-   irc: dod at irc.debian.org

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Debian FTP Masters]

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
  node-exports-loader_0.6.4-1_amd64.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Pirate Praveen]

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 have all dependencies packaged in debian.



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Julien Puydt]

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, and just *never* remove it?

After all, that will be a very small file, won't step on anybody's toe :
it's more trouble to drop it than to just leave it...

Snark on #debian-js

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Thorsten Glaser]

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 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.
>
> This seems like a very good plan to me: let /u/b/nodejs spit out a deprecation
> warning to stderr / syslog but pass all arguments to /u/b/node in Buster;


This *will* break scripts. There’s also:

x=$(nodejs progname --version 2>&1 >/dev/null | head -n 1)

Yes, I saw this break in other programs that suddenly decided
to add extra messages to either stdout and stderr, multiple times.

bye,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

*

**Besuchen Sie uns auf der dmexco!**
13. und 14. September 2017, Messe Köln,** Halle 7.1, Stand E042**
Digital Marketing Exposition & Conference
[www.tarent.de/dmexco](http://www.tarent.de/dmexco)

Wir empfehlen unseren Vortrag
"Wettbewerbsanalyse im Handel: Preisvergleich online und offline"
am 13. September, 18:00 Uhr im Speaker's Forum / Broadway

*

**Visit us at dmexco!**
September 13th and 14th, 2017, Messe Köln,** Hall 7.1, Booth E042**
Digital Marketing Exposition & Conference
[www.tarent.de/dmexco](http://www.tarent.de/dmexco)

We recommend our presentation
"Competitor analysis in retail: price comparison online and offline"
on September 13th, at 6 pm at the Speaker's Corner / Broadway

*

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Didier 'OdyX' Raboud]

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 for one
> > release to keep upgrades happy. Then drop the recomendation, and wait
> > for popcon to show that people are not installing the package any more.
> > Then remove the package in testing early in a cycle and see if anyone
> > reports bugs about it.
> 
> Even that would be quite unfriendly, because third party scripts might
> easily be deployed onto new Debian installs as well as existing ones.
> 
> Also, it is imposing an administrative burden on all Debian users (the
> metadata for the -legacy package, spurious search hits, etc.).  That
> burden might be small but would be completely unjustified.

This exact argument stands against not allowing NodeJS to use /usr/bin/node in 
the first place, really. We accepted to enforce that change for the /usr/bin/ 
namespace "first-come-first-served" reason. We imposed a quite heavy 
administrative burden of either targetting /u/b/nodejs additionally or (finding 
out and) installing nodejs-legacy for anyone wanting to use NodeJS on Debian.

Now, there are two categories of scripts affected by this discussion:
* All scripts which support /u/b/nodejs *in addition* to /u/b/node. These do 
so _because_ of a Debian-specific change, and removing the /u/b/nodejs symlink 
is not going to break those.
* All scripts which support /u/b/nodejs *exclusively*. These do so _because_ 
of a Debian-specific change, and don't support *any* non-Debian-derivative 
target (checked Fedora's nodejs RPMs: no /u/b/nodejs). Maintainers of those 
scripts have at one point decided to support only Debian{, and derivatives}.

There are _plenty_ of changes that one needs to care about in a stable 
upgrade: things like mandatory postfixing of Apache configuration files, 
removal 
of specific Python3 versions, removal of upstart, etc. Having to change a 
shebang isn't a big deal given the amount of things one has to check accross a 
stable release upgrade.

All that to say that despite the very small cost of keeping the symlink 
around, I do see value in closing the Debian-specific /u/b/nodejs chapter *at 
some point*. We should not clutter our future releases indefinitely with 
convenience symlinks for historical reasons, especially not when these were 
created _by_ Debian and have only been _in_ Debian.

Le jeudi, 31 août 2017, 13.52:00 h CEST 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.

This seems like a very good plan to me: let /u/b/nodejs spit out a deprecation 
warning to stderr / syslog but pass all arguments to /u/b/node in Buster; 
remove it entirely in Bullseye & get proper release note entries for both 
Buster and Bullseye.

Cheers.
OdyX

signature.asc
Description: This is a digitally signed message part.
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Didier 'OdyX' Raboud]

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 for that; it has both /usr/bin/nodejs and /usr/bin/node (in 
nodejs-legacy).

Cheers,
OdyX

signature.asc
Description: This is a digitally signed message part.
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Thorsten Glaser]

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 drop the nodejs symlink.

Again, “no, period”.

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.

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

*

**Besuchen Sie uns auf der dmexco!**
13. und 14. September 2017, Messe Köln,** Halle 7.1, Stand E042**
Digital Marketing Exposition & Conference
[www.tarent.de/dmexco](http://www.tarent.de/dmexco)

Wir empfehlen unseren Vortrag
"Wettbewerbsanalyse im Handel: Preisvergleich online und offline"
am 13. September, 18:00 Uhr im Speaker's Forum / Broadway

*

**Visit us at dmexco!**
September 13th and 14th, 2017, Messe Köln,** Hall 7.1, Booth E042**
Digital Marketing Exposition & Conference
[www.tarent.de/dmexco](http://www.tarent.de/dmexco)

We recommend our presentation
"Competitor analysis in retail: price comparison online and offline"
on September 13th, at 6 pm at the Speaker's Corner / Broadway

*

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Jérémy Lal]

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 main package for one
> > release to keep upgrades happy. Then drop the recomendation, and wait
> > for popcon to show that people are not installing the package any more.
> > Then remove the package in testing early in a cycle and see if anyone
> > reports bugs about it.
>
> Even that would be quite unfriendly, because third party scripts might
> easily be deployed onto new Debian installs as well as existing ones.
>
> Also, it is imposing an administrative burden on all Debian users (the
> metadata for the -legacy package, spurious search hits, etc.).  That
> burden might be small but would be completely unjustified.
>

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.

Jérémy
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[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 main package for one
> release to keep upgrades happy. Then drop the recomendation, and wait
> for popcon to show that people are not installing the package any more.
> Then remove the package in testing early in a cycle and see if anyone
> reports bugs about it.

Even that would be quite unfriendly, because third party scripts might
easily be deployed onto new Debian installs as well as existing ones.

Also, it is imposing an administrative burden on all Debian users (the
metadata for the -legacy package, spurious search hits, etc.).  That
burden might be small but would be completely unjustified.

Ian.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Debian FTP Masters]

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 

Changed-By: Jonas Smedegaard 
Description:
 libjs-uglify - UglifyJS in library form
 node-uglify - JavaScript parser, mangler/compressor and beautifier toolkit
Changes:
 uglifyjs (2.8.29-3) unstable; urgency=medium
 .
   [ Antonio Terceiro ]
   * Drop myself from Uploaders: I have no intention of working on this
 package anymore.
 .
   [ Jonas Smedegaard ]
   * Update copyright info: Use https protocol in file format URL.
   * Tighten lintian overrides regarding License-Reference.
   * Tighten and extend lintian overrides regarding false positives.
   * Use package section jacascript (not web).
   * Declare compliance with Debian Policy 4.1.0.
Checksums-Sha1:
 1a08dd7c0ab72ae92221182b9c0868886285626e 2147 uglifyjs_2.8.29-3.dsc
 8710c507f9d894f5de93a17ff2cc17afa213d4b7 10512 uglifyjs_2.8.29-3.debian.tar.xz
 e345990200ac3263ae8a38ab26d37f000b943469 71984 libjs-uglify_2.8.29-3_all.deb
 3c7af766ce836e60eb18a2f4cb16f9288ba3a341 121938 node-uglify_2.8.29-3_all.deb
 84c18ac3a474fdd02013a204e8b87f92330be525 9205 uglifyjs_2.8.29-3_amd64.buildinfo
Checksums-Sha256:
 6a1c85e63cbc70e7f46a83e927871f275d1c2a916390733c582d2673c70faa73 2147 
uglifyjs_2.8.29-3.dsc
 10d5f38fd8e97b9814558c6157b7c8b91ad9884d0b3c025e69f2fc5e0e2b4e5d 10512 
uglifyjs_2.8.29-3.debian.tar.xz
 cd4e66033dc3e62584cda26d147087f90f743e1027ed57192c28800e8a7040af 71984 
libjs-uglify_2.8.29-3_all.deb
 4e73975ba2ec923ef777d7e4dccdcb1e8bc7f3d405f1046d429a2f32c16700e4 121938 
node-uglify_2.8.29-3_all.deb
 40f6a46779da016f1017f27c54ac464007d5d92c5a01bf1bda26977eed6bf91b 9205 
uglifyjs_2.8.29-3_amd64.buildinfo
Files:
 4dfc2f07e381a6ccd9dea419c96492e5 2147 javascript optional uglifyjs_2.8.29-3.dsc
 08fb85060807c47d4574057ba5eddb13 10512 javascript optional 
uglifyjs_2.8.29-3.debian.tar.xz
 e3fc41b0f84464ead4e56feec2363c85 71984 javascript optional 
libjs-uglify_2.8.29-3_all.deb
 0f6951c8c97e350b71d55b54cb1d415a 121938 javascript optional 
node-uglify_2.8.29-3_all.deb
 eaad4c51093d50530980f2fb291f6724 9205 javascript optional 
uglifyjs_2.8.29-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlmn7EIACgkQLHwxRsGg
ASGIkQ//SDnyIP7GzMyHJ3MVx/utLk+MBrqIc2Y0OTPCy4rprrNL4X0YhOq7/tOP
3UcVB3Alpglxjvt/bWF91ZIBMEcaz2FuLMNUCAeNho4u7cKxSjDE7vhiOIBpT+5O
xnkcNlTtJrYyakg3bSgZ6IvlTtDoMiWsXh1xcKWgooJ4gz1UQN6eVqV+W4r1ih4L
bo8IuapDN69rOHwL+QO2b7UQ7PaXM2Ld1AaKp6geZkMnily5/8W7rw3mgMtXzvjU
TnupHMDdBvgyMqsDJ/pfzIy8lr0DfRqetobYcoMIE+NBUgeRwHlcqLpCESbrJrw5
hjNXrxn6TayBUH8FkfoPMlNZt7wp04OQHx3H/kUqr+ZTTDfBBmOKjyO9KRaeNxvw
/kRjpvYpZdKSmnXQehnA8KrJZhB1ceeoWetL6gU3/4P8Q3RlPsSKvrga66w9sCo2
I7IRaJQ15LLkhPKhMqZZ7Uptb40P2B7fpkKag9gt1Er79e/0JEz5GO31jjoMotJz
ocLy6Yt35FBlUCyvuqDx0+IuWpuxAcaCOTLmDptOJmBAwtUMR57kKaMDM4ZLNMp3
nSr98f1Zg/AXk5h/9t0Gw9buhCyQ54paXsoM1K6IGxqHwpLKVgX0KuU965JFEpOT
Bl/q3A0N0xCtsXtzRiQNIjvT2NhOWkvJLfPm6ziAf1iyZ0/LxdY=
=4Usz
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Debian FTP Masters]

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 (running on host usper.debian.org)

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Graham Inggs]

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
npm ERR! code ENOTFOUND
npm ERR! errno ENOTFOUND
npm ERR! syscall getaddrinfo

npm ERR! network getaddrinfo ENOTFOUND registry.npmjs.org 
registry.npmjs.org:443

npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad 
network settings.

npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'

npm ERR! Please include the following file with any support request:
npm ERR! /<>/node-babel-6.25.0+dfsg/npm-debug.log
Makefile:70: recipe for target 'bootstrap' failed
make[2]: *** [bootstrap] Error 1
make[2]: Leaving directory '/<>/node-babel-6.25.0+dfsg'
debian/rules:13: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>/node-babel-6.25.0+dfsg'
debian/rules:10: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

Regards
Graham

--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Graham Inggs]

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 rollup rollup-plugin-babel \
rollup-plugin-node-resolve babel-plugin-transform-flow-strip-types \
babel-preset-es2015 babel-preset-stage-0
npm ERR! Linux 4.4.0-92-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "babel-cli" 
"rollup" "rollup-plugin-babel" "rollup-plugin-node-resolve" 
"babel-plugin-transform-flow-strip-types" "babel-preset-es2015" 
"babel-preset-stage-0"

npm ERR! node v6.11.2
npm ERR! npm  v3.5.2
npm ERR! code ENOTFOUND
npm ERR! errno ENOTFOUND
npm ERR! syscall getaddrinfo

npm ERR! network getaddrinfo ENOTFOUND registry.npmjs.org 
registry.npmjs.org:443

npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad 
network settings.

npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'

npm ERR! Please include the following file with any support request:
npm ERR! /<>/npm-debug.log
debian/rules:11: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

Regards
Graham

--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Debian FTP Masters]

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 please be patient.

Packages are routinely processed through to the archive, and do feel
free to browse the NEW queue[1].

If there is an issue with the upload, you will receive an email from a
member of the ftpteam.

If you have any questions, you may reply to this email.

[1]: https://ftp-master.debian.org/new.html
 or https://ftp-master.debian.org/backports-new.html for *-backports

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Debian FTP Masters]

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,

Your Debian queue daemon (running on host usper.debian.org)

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Pirate Praveen]

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 babel-runtime.



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Debian FTP Masters]

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 queue daemon (running on host usper.debian.org)

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Debian FTP Masters]

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 mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Debian FTP Masters]

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 (running on host usper.debian.org)

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel