[Pkg-javascript-devel] node-sprintf-js 1.1.1+ds1-2 MIGRATED to testing

[Debian testing watch]

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

  Previous version: 1.0.3-2
  Current version:  1.1.1+ds1-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] node-punycode 2.1.0-3 MIGRATED to testing

[Debian testing watch]

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

  Previous version: 2.0.1-1
  Current version:  2.1.0-3

-- 
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-jsonparse 1.3.1-2 MIGRATED to testing

[Debian testing watch]

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

  Previous version: 1.2.0-1
  Current version:  1.3.1-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] libjs-sifter.js 0.5.2+dfsg-1 MIGRATED to testing

[Debian testing watch]

FYI: The status of the libjs-sifter.js source package
in Debian's testing distribution has changed.

  Previous version: 0.5.1+dfsg-2
  Current version:  0.5.2+dfsg-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

Re: [Pkg-javascript-devel] CTTE decision on nodejs (bug #862051)

[Ross Gammon]

On 16/08/17 15:06, Jérémy Lal wrote:
>
>
> 2017-08-16 14:30 GMT+02:00 Ross Gammon  >:
>
>
>
> On 16/08/17 10:22, Jérémy Lal wrote:
>>
>>
>> 2017-08-16 9:08 GMT+02:00 Ross Gammon > >:
>>
>> On 08/01/2017 09:14 AM, Jérémy Lal wrote:
>>>
>>>
>>> 2017-08-01 7:59 GMT+02:00 Ross Gammon
>>> >> >:
>>>
>>> On 07/31/2017 08:05 PM, Jérémy Lal wrote:
 Hi team,

 2017-07-31 19:17 GMT+02:00 Tollef Fog Heen
 >:


 The technical committee was asked in bug #862051 to
 revisit the decision in
 bug #614907 (conflict between the ax25-node package
 and the nodejs package).

 === Resolution ===

 The Technical Committee recognises that
 circumstances change in ways
 that make previous resolutions no longer
 appropriate.  In 2012, it was
 resolved that the nodejs package should not provide
 /usr/bin/node due to
 the historical conflict with the ax25-node
 package.  Node.js is still
 quite popular and the ax25-node package is no
 longer in stable, testing
 or unstable so the requirement for nodejs to not
 provide /usr/bin/node
 no longer applies.

 The Committee therefore resolves that:

 1. The CTTE decision from 2012-07-12 in bug #614907
 is repealed.

 This means Debian's normal policies and practices
 take over and the
 nodejs package is free to provide /usr/bin/node. 
 The migration should
 be managed according to Debian's usual
 backwards-compatibility
 arrangements.

 === End Resolution ===

 Please see http://bugs.debian.org/862051 for
 discussion of this bug.


 Next time i'll upload nodejs, it will be with
 /usr/bin/node and /usr/bin/nodejs.
 After that, please stop patching modules shebangs.
 I suspect it is a bad idea to keep /usr/bin/nodejs
 forever, so hopefully it will
 be possible to remove it before buster.

 Regards,
 Jérémy.



>>>
>>> Once that is done, I will tweak
>>> https://wiki.debian.org/Javascript/Nodejs/Manual
>>>  and
>>> https://wiki.debian.org/Javascript/Nodejs
>>>  for new team
>>> members if you like.
>>>
>>> Should we eventually add something to the buster release
>>> notes to warn those users/developers that might have
>>> been unaware of nodejs-legacy, and developed their own
>>> stuff using /usr/bin/nodejs? Or is that likely to be a
>>> rare situation?
>>>
>>>
>>> I suppose it's important enough to, yes.
>>>
>>> Jérémy
>>
>>
>> What's "done" exactly ? The wiki changes ?
>
> Sorry - yes, just the wiki changes.
>
>> Done - please double check someone!
>>
>> Where are we with npm2deb. Should I submit a bug, or has it
>> already been fixed? Sorry - I am suck on Stretch on my laptop
>> (waiting for more time), so I do lots of manual fixing when
>> working on a new package ATM.
>>
>> Was npm2deb rewriting shebang ?
>
> No. But maybe I went too far with the wiki update, as I also
> renamed the library install paths (as well as the binary path),
> and npm2deb would also need to update the paths in the
> debian/install files. I can drop that part of the change. In any
> case  I think npm2deb would need to adjust the path to the binary
> in debian/dirs and debian/install (and/or links?).
>
>> There is no particular urge in dropping /usr/bin/nodejs, though
>> it would be nice to get there for Buster.
>>
>> Backports - It struck me when doing the updates to the wiki
>> that we might need a versioned depends on nodejs
>> [Build-Depends: nodejs (>= 4.8.3~dfsg-1~) to make it clear
>> for people (like Andreas Tille) that might want to start
>> backporting node stuff to stretch. Otherwise they will need
>> to 

Re: [Pkg-javascript-devel] CTTE decision on nodejs (bug #862051)

[Jérémy Lal]

2017-08-16 9:08 GMT+02:00 Ross Gammon :

> On 08/01/2017 09:14 AM, Jérémy Lal wrote:
>
>
>
> 2017-08-01 7:59 GMT+02:00 Ross Gammon :
>
>> On 07/31/2017 08:05 PM, Jérémy Lal wrote:
>>
>> Hi team,
>>
>> 2017-07-31 19:17 GMT+02:00 Tollef Fog Heen :
>>
>>>
>>> The technical committee was asked in bug #862051 to revisit the decision
>>> in
>>> bug #614907 (conflict between the ax25-node package and the nodejs
>>> package).
>>>
>>> === Resolution ===
>>>
>>> The Technical Committee recognises that circumstances change in ways
>>> that make previous resolutions no longer appropriate.  In 2012, it was
>>> resolved that the nodejs package should not provide /usr/bin/node due to
>>> the historical conflict with the ax25-node package.  Node.js is still
>>> quite popular and the ax25-node package is no longer in stable, testing
>>> or unstable so the requirement for nodejs to not provide /usr/bin/node
>>> no longer applies.
>>>
>>> The Committee therefore resolves that:
>>>
>>> 1. The CTTE decision from 2012-07-12 in bug #614907 is repealed.
>>>
>>> This means Debian's normal policies and practices take over and the
>>> nodejs package is free to provide /usr/bin/node.  The migration should
>>> be managed according to Debian's usual backwards-compatibility
>>> arrangements.
>>>
>>> === End Resolution ===
>>>
>>> Please see http://bugs.debian.org/862051 for discussion of this bug.
>>>
>>
>> Next time i'll upload nodejs, it will be with /usr/bin/node and
>> /usr/bin/nodejs.
>> After that, please stop patching modules shebangs.
>> I suspect it is a bad idea to keep /usr/bin/nodejs forever, so hopefully
>> it will
>> be possible to remove it before buster.
>>
>> Regards,
>> Jérémy.
>>
>>
>>
>>
>> Once that is done, I will tweak https://wiki.debian.org/Javasc
>> ript/Nodejs/Manual and https://wiki.debian.org/Javascript/Nodejs for new
>> team members if you like.
>>
>> Should we eventually add something to the buster release notes to warn
>> those users/developers that might have been unaware of nodejs-legacy, and
>> developed their own stuff using /usr/bin/nodejs? Or is that likely to be a
>> rare situation?
>>
>
> I suppose it's important enough to, yes.
>
> Jérémy
>
>
What's "done" exactly ? The wiki changes ?

> Done - please double check someone!
>
> Where are we with npm2deb. Should I submit a bug, or has it already been
> fixed? Sorry - I am suck on Stretch on my laptop (waiting for more time),
> so I do lots of manual fixing when working on a new package ATM.
>
Was npm2deb rewriting shebang ?
There is no particular urge in dropping /usr/bin/nodejs, though it would be
nice to get there for Buster.

> Backports - It struck me when doing the updates to the wiki that we might
> need a versioned depends on nodejs [Build-Depends: nodejs (>= 4.8.3~dfsg-1~)
> to make it clear for people (like Andreas Tille) that might want to start
> backporting node stuff to stretch. Otherwise they will need to add back the
> patches to make things work.
>
Right now, to my knowledge, it's only version 6.11.2~dfsg-2 in unstable
that installs /usr/bin/node.

> Also I note on the wiki that the "nodejs-abi" might become a mandatory
> goal for Stretch! Where did we get with that? Should we make it mandatory
> for Buster?
>
This should be mandatory for nodejs c++ addons, though there are not plenty
of them and it's really easy to fix using the dh helper.
Other pure javascript libraries should not be concerned.

> Ross
>
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

Re: [Pkg-javascript-devel] parallel installation

[Ross Gammon]

Hi,

On 08/15/2017 09:20 PM, Paul Gevers wrote:
> Hi,
>
> On 14-08-17 20:38, Hubert Chathi wrote:
>> At the BoF at DebConf, we were talking about parallel installation of
>> different versions of JS libraries.  In order to do parallel
>> installation, we'd need differently named packages for different
>> versions, and it seems like the obvious way to do that is to have
>> packages called something like libjs-fooVER and node-fooVER, where VER
>> some sort of the API version, similar to the way that C/C++ library
>> packages are named after the library SONAME.  If upstream follows semver
>> properly, then VER would be the major version number.
> This sounds like a reasonable approach, but what I am missing is a
> recommendation on what to do to keep the number of packages limited. I
> think it is not such a great idea to replace one problem (not the right
> version) with another one (too many packages to support).
>
> One approach could be for example the following. Try to have only two
> versions per release, but really limit the number to a maximum of 3.
>
>> For libjs-fooVER, the JavaScript files would probably go in
>> /usr/share/javascript/fooVER/ rather than /usr/share/javascript/foo.
>> Obviously everything that previously pointed to the old place would have
>> to now point to the new place, but we could create a libjs-foo
>> transitional package libjs-foo that symlinks /usr/share/javascript/foo
>> to /usr/share/javascript/fooVER so that existing packages don't break.

For libjs stuff, this is generally aligned with how things are managed
upstream. I have seen many apps looking for a particular version of js
stuff on an online CDN anyway.

>> For node-fooVER, the logical analogue would be to put the files in
>> /usr/lib/nodejs/fooVER.  However, anything that uses the library does
>> "require("foo")", and so would not be able to find it there.  There are
>> a couple possible options for fixing that I can think of.  The first is
>> to change all "require("foo")" to "require("fooVER")", but that sounds
>> painful to do.  The second option is to add a symlink from
>> node_modules/foo to /usr/lib/nodejs/fooVER in the root directory of the
>> thing that requires foo.  I think the second option is the best,
>> especially since Node upstream seems to prefer searching for things in
>> node_modules rather than in /usr/lib/nodejs.  And again, we may want to
>> create a transitional package node-foo that symlinks /usr/lib/nodejs/foo
>> to /usr/lib/nodejs/fooVER.
>>
>> What are peoples' thoughts on this?
> For packages that are somewhat forgiving and/or want to migrate when
> required, it may make sense to not think about the *-foo packages as
> transitional packages, but as the default, which will always point to
> the latest version. Honestly, I rather depend on such a package and fix
> bugs as they come than having to keep an eye out for updates and update
> the dependency to the latest version.
>
> Paul
>
>
>

For node-* stuff however, upstream handle this by bundling a particular
version of a module in node_modules. If it is "really difficult" to
patch a node module/app to use the Debian version of a library (because
the versions have changed too much), then shouldn't we bundle the
node_module and install it as upstream do it (avoiding all the relative
path issues)? It could be followed up with a bug (severity
wishlist/normal?) to remove the bundled module once Debian and upstream
are more aligned.

Cheers,

Ross
-- 
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#857398: marked as done (node-acorn: broken symlink: /usr/lib/nodejs/acorn/acorn_csp.js -> acorn.js)

[Debian Bug Tracking System]

Your message dated Wed, 16 Aug 2017 07:19:00 +
with message-id 
and subject line Bug#857398: fixed in acorn 5.0.3-1
has caused the Debian Bug report #857398,
regarding node-acorn: broken symlink: /usr/lib/nodejs/acorn/acorn_csp.js -> 
acorn.js
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
857398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857398
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-acorn
Version: 4.0.4-2
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

0m58.4s ERROR: FAIL: Broken symlinks:
  /usr/lib/nodejs/acorn/acorn_csp.js -> acorn.js

The package ships acorn.js at a different location:
/usr/lib/nodejs/acorn/src/bin/acorn.js
  ^^^

cheers,

Andreas


node-acorn_4.0.4-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: acorn
Source-Version: 5.0.3-1

We believe that the bug you reported is fixed in the latest version of
acorn, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 857...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Julien Puydt  (supplier of updated acorn package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 16 Aug 2017 08:58:07 +0200
Source: acorn
Binary: node-acorn
Architecture: source all
Version: 5.0.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Julien Puydt 
Description:
 node-acorn - ECMAScript parser for Node.js
Closes: 857398
Changes:
 acorn (5.0.3-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #857398).
   * Bump standards-version to 4.0.0.
   * Remove build-dep on docbook-xml since it's not used anymore.
   * Don't parse the changelog : use dpkg's variables.
Checksums-Sha1:
 cda2dcf9fa898147ba2fe626cecf9a15675ad081 2054 acorn_5.0.3-1.dsc
 34dd11f6f7cd9da3ff6e5ea00240524cfbd34540 427038 acorn_5.0.3.orig.tar.gz
 2305745406f25b319bb924f8dd93204b699a790a 6752 acorn_5.0.3-1.debian.tar.xz
 54518df5cb2b642145ee4a2f3b5c941a6564f793 7228 acorn_5.0.3-1_amd64.buildinfo
 1128d95d295b3b8463ccb8c551691af55d170f43 60842 node-acorn_5.0.3-1_all.deb
Checksums-Sha256:
 00405b0e774ee6e8bf51abd336cc412226549992869bdab211b85dc186d4a91f 2054 
acorn_5.0.3-1.dsc
 eea06f371a0613df5336b3372193c964cdeab37a559735e12b070c6b70551318 427038 
acorn_5.0.3.orig.tar.gz
 9c692bd8572a576243b69f828c61902f5fb0bac21ffbf6ab049f7688e40cfbfa 6752 
acorn_5.0.3-1.debian.tar.xz
 322577744fc9b100690b6e9ab67ef0b87eadab7afc946d016764478516f0ce1a 7228 
acorn_5.0.3-1_amd64.buildinfo
 68bb4df38e294a90c76d752e4e0200f9bb3b002f74ad8c7df4abf509cbd1d349 60842 
node-acorn_5.0.3-1_all.deb
Files:
 173619d4afb26948c806daed0d6f1b93 2054 web extra acorn_5.0.3-1.dsc
 fd438f9e0eaf44aa6cf3969397f90a5b 427038 web extra acorn_5.0.3.orig.tar.gz
 c405e4a34ab5967361b310fee7a322a1 6752 web extra acorn_5.0.3-1.debian.tar.xz
 ab41c91d7e974986a938599322109ddd 7228 web extra acorn_5.0.3-1_amd64.buildinfo
 4f946a3d7884d9c31ca1702d9ed80b7b 60842 web extra node-acorn_5.0.3-1_all.deb

-BEGIN PGP SIGNATURE-

iQJNBAEBCgA3FiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAlmT73UZHGp1bGllbi5w
dXlkdEBsYXBvc3RlLm5ldAAKCRAExTvX/gMFUbe8D/9g508k6oeuNYxzMjSfRNzs
Jzu2yFV/ILGxTZZcppcn3f1ClmmPCU8hFNMTXnpbjz7RkVHHFNjqOWdNu3cphcfS
s1BGno/oK4MQwSOdm2uxu6JgwBXRnSuzTjAF3DC6L3+IEeVZvFZDo7FuzDFf6ZG4
Zg8TZwkmhRLegmzs2aV6kMrAzrvKMQko3HrULX962UJy820RPXqLPDumDFjHKUnK
mp36H8F681oenFgupOczCS6DkBKdvTyh7/2uxfqi+aiHmgwh/qmkmmhWpg7Av1t0
9Hf9j/kyGEM6oW2fX+ZPlAJO381uwEGr/MjOKHN2r/rYIRkEKg/n9yg6GfmrCuGw
gy+wge/Rx5rxB6Cbs1FQCuDyi5YDiRnH/71vFPkR7h0NzsSV6xo/l+1pD0bqviyM
BAeI3gBrY+3YvGVjDJAssiJ4TttrlmhopsrtlXe4quZ44TUeAXQRsi2EcFnM+MPc
Utm/KQh2Ot2e6Z/Y6BFug0x8f7vzQhQoukX0W1+Tu+OmcI8Wh8Kz45ar8qMv94ik
0mIcu7gQ1BWfn+cKjzsraoRUYBID6BGM8jJKMVgy7gpvW7J+wKInrqeEGbcHYpHT
9pHBydipYeQM9n/bK1IAxtKYYZQ1KTLcYk5JRd5l5njkp50LHLC9x68wtDdZlREs

[Pkg-javascript-devel] acorn_5.0.3-1_amd64.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 16 Aug 2017 08:58:07 +0200
Source: acorn
Binary: node-acorn
Architecture: source all
Version: 5.0.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Julien Puydt 
Description:
 node-acorn - ECMAScript parser for Node.js
Closes: 857398
Changes:
 acorn (5.0.3-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #857398).
   * Bump standards-version to 4.0.0.
   * Remove build-dep on docbook-xml since it's not used anymore.
   * Don't parse the changelog : use dpkg's variables.
Checksums-Sha1:
 cda2dcf9fa898147ba2fe626cecf9a15675ad081 2054 acorn_5.0.3-1.dsc
 34dd11f6f7cd9da3ff6e5ea00240524cfbd34540 427038 acorn_5.0.3.orig.tar.gz
 2305745406f25b319bb924f8dd93204b699a790a 6752 acorn_5.0.3-1.debian.tar.xz
 54518df5cb2b642145ee4a2f3b5c941a6564f793 7228 acorn_5.0.3-1_amd64.buildinfo
 1128d95d295b3b8463ccb8c551691af55d170f43 60842 node-acorn_5.0.3-1_all.deb
Checksums-Sha256:
 00405b0e774ee6e8bf51abd336cc412226549992869bdab211b85dc186d4a91f 2054 
acorn_5.0.3-1.dsc
 eea06f371a0613df5336b3372193c964cdeab37a559735e12b070c6b70551318 427038 
acorn_5.0.3.orig.tar.gz
 9c692bd8572a576243b69f828c61902f5fb0bac21ffbf6ab049f7688e40cfbfa 6752 
acorn_5.0.3-1.debian.tar.xz
 322577744fc9b100690b6e9ab67ef0b87eadab7afc946d016764478516f0ce1a 7228 
acorn_5.0.3-1_amd64.buildinfo
 68bb4df38e294a90c76d752e4e0200f9bb3b002f74ad8c7df4abf509cbd1d349 60842 
node-acorn_5.0.3-1_all.deb
Files:
 173619d4afb26948c806daed0d6f1b93 2054 web extra acorn_5.0.3-1.dsc
 fd438f9e0eaf44aa6cf3969397f90a5b 427038 web extra acorn_5.0.3.orig.tar.gz
 c405e4a34ab5967361b310fee7a322a1 6752 web extra acorn_5.0.3-1.debian.tar.xz
 ab41c91d7e974986a938599322109ddd 7228 web extra acorn_5.0.3-1_amd64.buildinfo
 4f946a3d7884d9c31ca1702d9ed80b7b 60842 web extra node-acorn_5.0.3-1_all.deb

-BEGIN PGP SIGNATURE-

iQJNBAEBCgA3FiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAlmT73UZHGp1bGllbi5w
dXlkdEBsYXBvc3RlLm5ldAAKCRAExTvX/gMFUbe8D/9g508k6oeuNYxzMjSfRNzs
Jzu2yFV/ILGxTZZcppcn3f1ClmmPCU8hFNMTXnpbjz7RkVHHFNjqOWdNu3cphcfS
s1BGno/oK4MQwSOdm2uxu6JgwBXRnSuzTjAF3DC6L3+IEeVZvFZDo7FuzDFf6ZG4
Zg8TZwkmhRLegmzs2aV6kMrAzrvKMQko3HrULX962UJy820RPXqLPDumDFjHKUnK
mp36H8F681oenFgupOczCS6DkBKdvTyh7/2uxfqi+aiHmgwh/qmkmmhWpg7Av1t0
9Hf9j/kyGEM6oW2fX+ZPlAJO381uwEGr/MjOKHN2r/rYIRkEKg/n9yg6GfmrCuGw
gy+wge/Rx5rxB6Cbs1FQCuDyi5YDiRnH/71vFPkR7h0NzsSV6xo/l+1pD0bqviyM
BAeI3gBrY+3YvGVjDJAssiJ4TttrlmhopsrtlXe4quZ44TUeAXQRsi2EcFnM+MPc
Utm/KQh2Ot2e6Z/Y6BFug0x8f7vzQhQoukX0W1+Tu+OmcI8Wh8Kz45ar8qMv94ik
0mIcu7gQ1BWfn+cKjzsraoRUYBID6BGM8jJKMVgy7gpvW7J+wKInrqeEGbcHYpHT
9pHBydipYeQM9n/bK1IAxtKYYZQ1KTLcYk5JRd5l5njkp50LHLC9x68wtDdZlREs
D/ZIs71kAB9phj+6MXHcrA==
=xPje
-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

Re: [Pkg-javascript-devel] CTTE decision on nodejs (bug #862051)

[Ross Gammon]

On 08/01/2017 09:14 AM, Jérémy Lal wrote:
>
>
> 2017-08-01 7:59 GMT+02:00 Ross Gammon  >:
>
> On 07/31/2017 08:05 PM, Jérémy Lal wrote:
>> Hi team,
>>
>> 2017-07-31 19:17 GMT+02:00 Tollef Fog Heen > >:
>>
>>
>> The technical committee was asked in bug #862051 to revisit
>> the decision in
>> bug #614907 (conflict between the ax25-node package and the
>> nodejs package).
>>
>> === Resolution ===
>>
>> The Technical Committee recognises that circumstances change
>> in ways
>> that make previous resolutions no longer appropriate.  In
>> 2012, it was
>> resolved that the nodejs package should not provide
>> /usr/bin/node due to
>> the historical conflict with the ax25-node package.  Node.js
>> is still
>> quite popular and the ax25-node package is no longer in
>> stable, testing
>> or unstable so the requirement for nodejs to not provide
>> /usr/bin/node
>> no longer applies.
>>
>> The Committee therefore resolves that:
>>
>> 1. The CTTE decision from 2012-07-12 in bug #614907 is repealed.
>>
>> This means Debian's normal policies and practices take over
>> and the
>> nodejs package is free to provide /usr/bin/node.  The
>> migration should
>> be managed according to Debian's usual backwards-compatibility
>> arrangements.
>>
>> === End Resolution ===
>>
>> Please see http://bugs.debian.org/862051 for discussion of
>> this bug.
>>
>>
>> Next time i'll upload nodejs, it will be with /usr/bin/node and
>> /usr/bin/nodejs.
>> After that, please stop patching modules shebangs.
>> I suspect it is a bad idea to keep /usr/bin/nodejs forever, so
>> hopefully it will
>> be possible to remove it before buster.
>>
>> Regards,
>> Jérémy.
>>
>>
>>
>
> Once that is done, I will tweak
> https://wiki.debian.org/Javascript/Nodejs/Manual
>  and
> https://wiki.debian.org/Javascript/Nodejs
>  for new team members
> if you like.
>
> Should we eventually add something to the buster release notes to
> warn those users/developers that might have been unaware of
> nodejs-legacy, and developed their own stuff using
> /usr/bin/nodejs? Or is that likely to be a rare situation?
>
>
> I suppose it's important enough to, yes.
>
> Jérémy

Done - please double check someone!

Where are we with npm2deb. Should I submit a bug, or has it already been
fixed? Sorry - I am suck on Stretch on my laptop (waiting for more
time), so I do lots of manual fixing when working on a new package ATM.

Backports - It struck me when doing the updates to the wiki that we
might need a versioned depends on nodejs [Build-Depends: nodejs (>=
4.8.3~dfsg-1~) to make it clear for people (like Andreas Tille) that
might want to start backporting node stuff to stretch. Otherwise they
will need to add back the patches to make things work.

Also I note on the wiki that the "nodejs-abi" might become a mandatory
goal for Stretch! Where did we get with that? Should we make it
mandatory for Buster?

Cheers,

Ross

-- 
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-tablesorter_2.28.15+dfsg1-1~bpo9+1_amd64.changes ACCEPTED into stretch-backports, stretch-backports

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 13 Aug 2017 20:15:09 +0200
Source: jquery-tablesorter
Binary: libjs-jquery-tablesorter
Architecture: source all
Version: 1:2.28.15+dfsg1-1~bpo9+1
Distribution: stretch-backports
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Paul Gevers 
Description:
 libjs-jquery-tablesorter - jQuery flexible client-side table sorting plugin
Closes: 731095
Changes:
 jquery-tablesorter (1:2.28.15+dfsg1-1~bpo9+1) stretch-backports; urgency=medium
 .
   * Rebuild for stretch-backports.
 .
 jquery-tablesorter (1:2.28.15+dfsg1-1) unstable; urgency=medium
 .
   * New upstream release
   * Add backward compatibility softlinks until all Debian packages have
 switched
 .
 jquery-tablesorter (1:2.28.9+dfsg1-1) experimental; urgency=medium
 .
   * Split off from jquery-goodies; rewrite from scratch
   * Use maintained fork instead of original upstream (Closes: #731095)
Checksums-Sha1:
 56883c478b560fba3f4d0e12dc1b98f14188ad57 1924 
jquery-tablesorter_2.28.15+dfsg1-1~bpo9+1.dsc
 060d0cc28f10226738f0c2428ed409f8ce70e50b 4264 
jquery-tablesorter_2.28.15+dfsg1-1~bpo9+1.debian.tar.xz
 6a6c5b340731be223cbb094c1766bdb0510adbcc 11877 
jquery-tablesorter_2.28.15+dfsg1-1~bpo9+1_amd64.buildinfo
 4a55492664f2343406aa7fa5b9132d06ded6c022 163560 
libjs-jquery-tablesorter_2.28.15+dfsg1-1~bpo9+1_all.deb
Checksums-Sha256:
 cf64f9c7c8f6f27de2db656070baf437e739de61b46ea779a72cbafc56dabac3 1924 
jquery-tablesorter_2.28.15+dfsg1-1~bpo9+1.dsc
 a4b315b4325b0a027680acb30f4ec133864c97ccc10efee945fbb8508f227b31 4264 
jquery-tablesorter_2.28.15+dfsg1-1~bpo9+1.debian.tar.xz
 3d05dfb1e07cfa16c2f5f433d9dfd958a0a3b8c22c1168d65eb9185f6579071f 11877 
jquery-tablesorter_2.28.15+dfsg1-1~bpo9+1_amd64.buildinfo
 39aa96c2ddcb7fcdbfbbc349d25c07bff5f1613c5fe2b7c21cd68b6aead33d1d 163560 
libjs-jquery-tablesorter_2.28.15+dfsg1-1~bpo9+1_all.deb
Files:
 25ada1a7e6f5e334b7c323256d7b2042 1924 web optional 
jquery-tablesorter_2.28.15+dfsg1-1~bpo9+1.dsc
 2b0554cb7ea534163477e909f6de7ae6 4264 web optional 
jquery-tablesorter_2.28.15+dfsg1-1~bpo9+1.debian.tar.xz
 d474300be2db214465577a9a9c03f8fa 11877 web optional 
jquery-tablesorter_2.28.15+dfsg1-1~bpo9+1_amd64.buildinfo
 d9f34c27a7c6194c9e78c60f9c3920ce 163560 web optional 
libjs-jquery-tablesorter_2.28.15+dfsg1-1~bpo9+1_all.deb

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlmTWkwACgkQnFyZ6wW9
dQrb7QgAgYnsllt1qcY2UUVpmgj5Z6kgEyrz85XV0tsdn9SXoyJ48iGwlQT083UK
UwDXKE6ft6T16+QMTt0uPbG0CkgY97isFjsIjUNNCNesI4M7C29kxxbqc7+tis9Z
0Xg2NRScFrT/SmuaemEXsgI1qONOnPHv865T2yPfBlje5kxOslWcdsR9e3Uka6M0
6hWjENgeQihD5wCRhfFsZ1YDE6Z+pt2+SGkygl9X2WYu5srOTJvI7bzLRtoYwBwk
FxNePQyn+HlBpdMVaEJXjRpd1TSq5taeTJAjmXNEd/N2xe8MlJpjl9y+Is2Dbco7
VUooApkNBS6Ju7VvLFcf9KrXRjsA/g==
=TA8O
-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