[Pkg-javascript-devel] node-json-parse-helpfulerror 1.0.3-1 MIGRATED to testing

[Debian testing watch]

FYI: The status of the node-json-parse-helpfulerror source package
in Debian's testing distribution has changed.

  Previous version: (not in testing)
  Current version:  1.0.3-1

-- 
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] node-estraverse 4.2.0-1 MIGRATED to testing

[Debian testing watch]

FYI: The status of the node-estraverse source package
in Debian's testing distribution has changed.

  Previous version: (not in testing)
  Current version:  4.2.0-1

-- 
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] node-esutils 2.0.2-1 MIGRATED to testing

[Debian testing watch]

FYI: The status of the node-esutils source package
in Debian's testing distribution has changed.

  Previous version: (not in testing)
  Current version:  2.0.2-1

-- 
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] node-cjson 0.4.0-1 MIGRATED to testing

[Debian testing watch]

FYI: The status of the node-cjson source package
in Debian's testing distribution has changed.

  Previous version: (not in testing)
  Current version:  0.4.0-1

-- 
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] Bug#841558: node-tap: FTBFS: help2man: can't get `--help' info from bin/tap.js

[Jérémy Lal]

2016-10-21 15:52 GMT+02:00 Lucas Nussbaum <lu...@debian.org>:

> Source: node-tap
> Version: 0.7.1-1.1
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20161021 qa-ftbfs
> Justification: FTBFS on amd64
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
>
> Relevant part (hopefully):
> >  debian/rules build
> > dh build
> >dh_testdir
> >dh_update_autotools_config
> >dh_auto_configure
> >debian/rules override_dh_auto_build
> > make[1]: Entering directory '/<>'
> > help2man -N -n "Test-Anything-Protocol module for Node.js" bin/tap.js -o
> "debian/tap.1"
> > help2man: can't get `--help' info from bin/tap.js
>

This means there was an error invoking bin/tap.js (but i can't tell which
error).

Reading
http://aws-logs.debian.net/2016/10/21/node-tap_0.7.1-1.1_unstable.log
and comparing to a local (up-to-date) sbuild in sid, this part is somewhat
missing:

dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: applying nodejs_rename.patch
dpkg-source: info: applying use_available_modules.patch
dpkg-source: info: applying sbuild_disable_tests.patch
dpkg-source: info: applying mitigate_test_segv.patch
dpkg-source: info: building node-tap using existing
./node-tap_0.7.1.orig.tar.gz
dpkg-source: info: building node-tap in node-tap_0.7.1-1.debian.tar.xz
dpkg-source: info: building node-tap in node-tap_0.7.1-1.dsc

which would explain the failure.
I'm worried that this build has somehow not applied the quilt patches ?

Maybe the mistake is mine, because i'm not 100% sure
`override_dh_auto_build: debian/tap.1`
guarantees the quilt patch to be applied when debian/tap.1 target is
invoked.
It used to work, tough.

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#841614: node-es6-promise: FTBFS: compile-modules shows help

[Lucas Nussbaum]

Source: node-es6-promise
Version: 3.2.2+ds-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>/node-es6-promise-3.2.2+ds'
> mkdir dist
> compile-modules convert -f bundle -o dist/es6-promise.js 
> lib/es6-promise.umd.js
> compile-modules [--help] [--version]  []
> 
> Commands
> 
>   convert  Converts modules from `import`/`export` to an ES5 equivalent.
>   help Display help for a given command.
> debian/rules:10: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Error 1

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   
http://aws-logs.debian.net/2016/10/21/node-es6-promise_3.2.2+ds-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

-- 
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#841587: node-livescript: FTBFS: /bin/sh: 1: /usr/bin/lsc: not found

[Lucas Nussbaum]

Source: node-livescript
Version: 1.5.0+dfsg-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build
>dh_testdir
>dh_update_autotools_config
>dh_auto_configure
>dh_auto_build
>   make -j1
> make[1]: Entering directory '/<>/node-livescript-1.5.0+dfsg'
> mkdir -p lib/
> /usr/bin/lsc --output lib --bare --compile "src/ast.ls"
> /bin/sh: 1: /usr/bin/lsc: not found
> Makefile:17: recipe for target 'lib/ast.js' failed
> make[1]: *** [lib/ast.js] Error 127

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   
http://aws-logs.debian.net/2016/10/21/node-livescript_1.5.0+dfsg-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

-- 
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-fs.realpath_1.0.0-1_amd64.changes ACCEPTED into unstable, unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 18 Oct 2016 19:20:26 +0530
Source: node-fs.realpath
Binary: node-fs.realpath
Architecture: source all
Version: 1.0.0-1
Distribution: unstable
Urgency: low
Maintainer: Debian Javascript Maintainers 

Changed-By: Sruthi Chandran 
Description:
 node-fs.realpath - Use node's fs.realpath
Closes: 841206
Changes:
 node-fs.realpath (1.0.0-1) unstable; urgency=low
 .
   * Initial release (Closes: #841206)
Checksums-Sha1:
 1bda323d11555410c50cfd0b7c12920901cb86fc 2079 node-fs.realpath_1.0.0-1.dsc
 3e63c54123eba7f91d8ba2a8fccea8586604a137 5149 
node-fs.realpath_1.0.0.orig.tar.gz
 4627aa26bb47b9ddf9f9ac972cb0b1fa2f9b7476 2292 
node-fs.realpath_1.0.0-1.debian.tar.xz
 a38c589cccbb346c6cbd9bf1a7c0dbe5da145133 5522 node-fs.realpath_1.0.0-1_all.deb
Checksums-Sha256:
 dd32807fe8d1e0df31289fba3e855aa95d5730c3551b5135acd61e5b65e8e0a6 2079 
node-fs.realpath_1.0.0-1.dsc
 6216afeb56b7098cb0717cba38028d58dbefdc157348d12fe72cd45e13d6cb9b 5149 
node-fs.realpath_1.0.0.orig.tar.gz
 44d376aa5eb4b7c821243b6f25f112c8cc74e6402b981bae4117a635b79db671 2292 
node-fs.realpath_1.0.0-1.debian.tar.xz
 65d8bc8b1896aec5fe1b9d3ca10a89b0cd5a17aff279ba0c407111f80cd3da57 5522 
node-fs.realpath_1.0.0-1_all.deb
Files:
 ffd76d803e92d7d9565122a315ddfd00 2079 web optional node-fs.realpath_1.0.0-1.dsc
 bd9643d6ce49fb9b2241deba65e134b0 5149 web optional 
node-fs.realpath_1.0.0.orig.tar.gz
 428951d1912068c47f19aa948efb6806 2292 web optional 
node-fs.realpath_1.0.0-1.debian.tar.xz
 e61727a71a4d6fc775b261730377c13f 5522 web optional 
node-fs.realpath_1.0.0-1_all.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYCFPEAAoJEM4fnGdFEsIq9JwP/iiUOatt7VoQd66wC7MoFjp/
dqhqUe5YEbYTXJerCGmDcYK8tptKlnAohyXoHtkNfGXAGSrfRrC/WAks0fsb4I4c
eoxjp4wDv53qUlf3UoXOWOG5H3bAwXty81HCilouotiOkC2L8KW/6wEUemHBNif8
VUkvS/5WyFi36F5TOZxdBlzlakxJJUeGLlrmcnjtyzRkknLEeqWR0AVUYt95pK3W
Y7lfbmct8IRIo5BNi3/4GQw74Txm+zEpyoeG6f63KaTWGw6OQvI/yGoFG2CQns96
y8CVbC97Qg3yDqvEJwYtVXuxMVoRuVJ4VMwLs0p1S9mPr6s+qipEYOZvfkVTATaB
YuRzuesSRs3jY0x9pEvltLDdhlWjsSMqmqFoS3ziV9+QlqAk7z4HllBWM9waaTSm
n9QcdAn6LTNKbW5DA/wUNazqeRNxgVR15xYDfwT5IiksGRU2EuLF70RcY8TQ0ptK
9R5JEmpWqU7qOq2QOlDLB739uKL8rVlG71rNZx1HFati4BwbU18Acz5b+6OqJyGj
I8h44vijN7IfJkUOwTqLE6G+CJjt+yo+RIMKIdn66KX11UlpCYSJimofbwMEIIFd
gU4DqSEB7+mQNp9Lt2wRsNStlgbUIMGdQ7kOarNRqj5kl4qWl65TsDem8QpaMn7V
ju6JFlWjpkZHj42ABFNv
=0gSP
-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 libuv1_1.9.1-2_amd64.changes

[Debian FTP Masters]

libuv1_1.9.1-2_amd64.changes uploaded successfully to localhost
along with the files:
  libuv1_1.9.1-2.dsc
  libuv1_1.9.1-2.debian.tar.xz
  libuv1-dbg_1.9.1-2_amd64.deb
  libuv1-dev_1.9.1-2_amd64.deb
  libuv1_1.9.1-2_amd64.deb

Greetings,

Your Debian queue daemon (running on host franck.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] My recent bugs

[Santiago Vila]

Hi. It has been pointed to me that this was already reported.

I'm going to merge the bugs so that you don't have to.

Sorry.

-- 
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] /usr/bin/nodejs vs /usr/bin/node

[Jonas Smedegaard]

Hi Daniel,

Quoting Jérémy Lal (2016-10-21 09:05:04)
> 2016-10-21 7:24 GMT+02:00 Paul Gevers :
> > On 21-10-16 06:55, Daniel Lo Nigro wrote:
> > > Given the amount of complexity stemming from Debian renaming this 
> > > binary and the fact that it breaks parts of the Node.js ecosystem, 
> > > is there any chance it will be renamed back to "node" in the 
> > > future, or for /usr/bin/node to be symlinked to /usr/bin/node 
> > > (perhaps using the update-alternatives system to allow the user to 
> > > choose whether they want to symlink nodejs or ax25-node, in case 
> > > they have both installed)?
> >
> > In Debian, we have the package nodejs-legacy which provides the 
> > symlink you request. Please read the description. Apart from text 
> > describing fact that no official Debian package may depend on it, it 
> > also contains a link to the technical committee ruling on how this 
> > came about. As the ax25-node package still exist, I see no chance at 
> > all that the current situation will change.
> >
> > As ax25-node and nodejs don't provide the same functionality, using 
> > the update-alternaives system is not appropriate.

> if you're distributing yarn in the main debian archive, i believe the 
> right way to work around this is to "Suggest" nodejs-legacy in 
> debian/control.

I disagree that above is the "right way" - here are the options you have 
as I see them:

 a) Continue to also support "nodejs" runtime
* You may suggest (but not recommend or depend on) nodejs-legacy.
* Must be usable (at least for a subset of cases) with "nodejs".

 b) Support only "node" runtime
* You should depend on or recommend nodejs-legacy
* Cannot be part of official Debian (but can be in contrib)

 c) Change ruling through the tech-ctte or a general solution vote
* Will be a tiresome and long process
* Will only become effective for next-next stable (i.e. in ~2019)
* May further tear apart our communities rather than unite

As I see it, the "right way from the POV of Debian is a), while from the 
POV of the Node.js community it is c).


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: 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

Re: [Pkg-javascript-devel] /usr/bin/nodejs vs /usr/bin/node

[Jérémy Lal]

2016-10-21 7:24 GMT+02:00 Paul Gevers :

> Hi Daniel,
>
> On 21-10-16 06:55, Daniel Lo Nigro wrote:
> > Given the amount of complexity stemming from Debian renaming this binary
> > and the fact that it breaks parts of the Node.js ecosystem, is there any
> > chance it will be renamed back to "node" in the future, or for
> > /usr/bin/node to be symlinked to /usr/bin/node (perhaps using the
> > update-alternatives system to allow the user to choose whether they want
> > to symlink nodejs or ax25-node, in case they have both installed)?
>
> In Debian, we have the package nodejs-legacy which provides the symlink
> you request. Please read the description. Apart from text describing
> fact that no official Debian package may depend on it, it also contains
> a link to the technical committee ruling on how this came about. As the
> ax25-node package still exist, I see no chance at all that the current
> situation will change.
>
> As ax25-node and nodejs don't provide the same functionality, using the
> update-alternaives system is not appropriate.
>
>
Hello,

if you're distributing yarn in the main debian archive, i believe the right
way to
work around this is to "Suggest" nodejs-legacy in debian/control.
We're probably going to do the same with npm (but i clearly lack the time to
take care of npm).

if you're distributing it outside of debian archives, then "Recommend" is
good too.
Avoid "Depend", because it would risk breaking for users installing "nodejs"
debian package from upstream.

Note that the original package name conflict disappeared: there is no longer
a "node" binary distributed by ax25-node at all, but the "too generic a
name"
issue remains.

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