[Pkg-javascript-devel] node-temp is marked for autoremoval from testing

[Debian testing autoremoval watch]

node-temp 0.8.1-1 is marked for autoremoval from testing on 2016-09-18

It is affected by these RC bugs:
834915: node-temp: FTBFS too much often (AssertionError: temp.createWriteStream 
did not create a file)


-- 
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] roadmap of jquery (and helpers)

[Paul Gevers]

Hi all,

On 09/14/16 21:46, Jonas Smedegaard wrote:

Quoting Paul Gevers (2016-09-14 20:53:40)
The Javascript team is only loosely coordinated: Not all of us nurse all
of the packages in the team.


So how many are there approximately? And how many are involved in the 
jquery stuff? I am considering joining the team, but I don't want to be 
the only one to care for jquery and its related packages (no offense 
intended Antonio).



As I recall, maintenance of jquery in particular has lagged behind a lot
in the past.  So any and all help would be much appreciated.


So a statement on the current strategy would be nice, such that I can 
evaluate if it makes sense to join the team. What I care for is that a 
modern version is available (maybe for the time being next to an older 
API? How are other JavaScript chains handling the lack of automatic API 
tracking? Are there tools in the team to check for breakage? One of the 
stupid but powerful things that I do for the cacti package (a web-app) 
is to just recursively crawl all web-pages, I guess it must be possible 
to also check JavaScript execution.


Paul

PS: until I join the team, please keep CC-ing me.

--
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-nan 2.4.0-1 MIGRATED to testing

[Debian testing watch]

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

  Previous version: 2.3.5-1
  Current version:  2.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] node-moment_2.15.0+ds-1_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 16 Sep 2016 08:59:50 +0200
Source: node-moment
Binary: node-moment libjs-moment
Architecture: source
Version: 2.15.0+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Julien Puydt 
Description:
 libjs-moment - Work with dates in JavaScript (library)
 node-moment - Work with dates in JavaScript (Node.js module)
Changes:
 node-moment (2.15.0+ds-1) unstable; urgency=medium
 .
   * New upstream release.
   * Marked libjs-moment as Multi-Arch: foreign.
Checksums-Sha1:
 2ad66d379738986f1ed36012177c355164c9c502 2076 node-moment_2.15.0+ds-1.dsc
 dca82e58a547baa6bab3ae07852ebfdc80897661 765827 
node-moment_2.15.0+ds.orig.tar.gz
 f3712f24472c33e46b08f756912b2b59ef2351ed 2676 
node-moment_2.15.0+ds-1.debian.tar.xz
Checksums-Sha256:
 4399ddebe27a7a925cd91008b9cce211c475387ef31b3cfb381b37fcef43684f 2076 
node-moment_2.15.0+ds-1.dsc
 c976b5b2016c7b59a96eb0a789804dfdd140314b078a98eddb169c36e8aff489 765827 
node-moment_2.15.0+ds.orig.tar.gz
 37eadacccf8d548985bf382f2729f782de526939ba631d2c1e6102dcfd052112 2676 
node-moment_2.15.0+ds-1.debian.tar.xz
Files:
 c7073053a28187541459a92ecfd9bc05 2076 web optional node-moment_2.15.0+ds-1.dsc
 7abbf73f01e8fd594b239e3f30b08ee7 765827 web optional 
node-moment_2.15.0+ds.orig.tar.gz
 6ce396a5a9d454616c6fb024c9584943 2676 web optional 
node-moment_2.15.0+ds-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJX2+/cAAoJEEsEP825REVAd24P/RzjZrWyeK13aioyZoXbFHoZ
ycvSqeLd5brVvu7x7XClCWNwjzxAGrWMVXDWFVIZPL1NAiNCqTpwGEi9QwVVbIeF
EI5RAdkoy2URjEdKQBU2Mdeq83ffzqcvz/xxIRIVFT+4rHdjwciOBC6+jg2dIGs9
gDmhjNCx3sb9bdSjhdVYPeb5j0EW+tp6ZTYB6hmaNjgy6NlhAwdya3DT0Qb2z3hB
7JVf61ZKF/syhsTtQl1JmQXh3x8O9N8gUmryTGrT7aHl9oRy6oxJyd9nCDmxm7G9
42ze2dkpKZggD0WuYcC3WRTS6WxuTBc6Nr/JHc+0BdH4h06r1EmI6t8W560jPnGI
yyBPY4BNZVRrpAmmO3PeO2jRPdnueMSRIWYta2kYen83xVNtzpH9OVSZFopIN5rw
9TV5clqpw4ayUSb7DBgA6t5/ciSnePc9YDG/C92A0AwKLdMvOqflRf8KXsWJU8qH
WuShfDN1iJ3g99dB3bmVMvcpr8NOoxtOjsTRqt7SyGzgINzMGd18429YHg9IWt4G
40jOYQCwW0KbGJfgCJijY8EhqWivQeRWFMu0AsqeNo9oIzc4IGkpSXCnO/GJ5nKY
mWK8/8khwhXa3X7STr7ASn6T3dpJFGVXDwm/rrFQeqZT3kuKJrYbFg0N8I84jHh1
0KMGYDKArrmSXcgcLMRb
=niXl
-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 node-moment_2.15.0+ds-1_source.changes

[Debian FTP Masters]

node-moment_2.15.0+ds-1_source.changes uploaded successfully to localhost
along with the files:
  node-moment_2.15.0+ds-1.dsc
  node-moment_2.15.0+ds.orig.tar.gz
  node-moment_2.15.0+ds-1.debian.tar.xz

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] Bug#837929: npm: Should suggest nodejs-legacy

[Jonas Smedegaard]

[drop old archived bug from cc]

Quoting Matijs van Zuijlen (2016-09-16 10:39:05)
> On 16/09/16 10:24, Jérémy Lal wrote:
> > 2016-09-16 10:22 GMT+02:00 Jonas Smedegaard  > >:
> > Quoting Matijs van Zuijlen (2016-09-16 09:57:52)
> > > I read through bug 614907, and I think the very best solution 
> > > would be for npm to ensure the correct node executable is 
> > > referenced in each package's executable. I don't know how feasible 
> > > that would be.
> >
> > Arguably the "very best" would be to drop npm from Debian ;-)
> >
> > More to the point, however: Do npm work at all without 
> > nodejs-legacy? If not, then npm itself should be moved to contrib!
> > 
> > Actually i believe most modules just work without nodejs-legacy, and 
> > npm itself has some uses without installing it either.
> 
> Yes, it seems it's mainly the modules that provide an executable 
> script that need nodejs-legacy (In my case, coffeelint).

Agreed.

I mentioned it only for completeness.

 - 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

[Pkg-javascript-devel] Bug#837929: npm: Should suggest nodejs-legacy

[Matijs van Zuijlen]

On 16/09/16 10:24, Jérémy Lal wrote:
> 
> 
> 2016-09-16 10:22 GMT+02:00 Jonas Smedegaard  >:
> 
> Quoting Matijs van Zuijlen (2016-09-16 09:57:52)
> > I read through bug 614907, and I think the very best solution would be
> > for npm to ensure the correct node executable is referenced in each
> > package's executable. I don't know how feasible that would be.
> 
> Arguably the "very best" would be to drop npm from Debian ;-)
> 
> More to the point, however: Do npm work at all without nodejs-legacy?
> If not, then npm itself should be moved to contrib!
> 
> 
> Actually i believe most modules just work without nodejs-legacy, and npm
> itself
> has some uses without installing it either.

Yes, it seems it's mainly the modules that provide an executable script
that need nodejs-legacy (In my case, coffeelint).

Regards,
Matijs



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#837929: npm: Should suggest nodejs-legacy

[Jérémy Lal]

2016-09-16 10:22 GMT+02:00 Jonas Smedegaard :

> Quoting Matijs van Zuijlen (2016-09-16 09:57:52)
> > I read through bug 614907, and I think the very best solution would be
> > for npm to ensure the correct node executable is referenced in each
> > package's executable. I don't know how feasible that would be.
>
> Arguably the "very best" would be to drop npm from Debian ;-)
>
> More to the point, however: Do npm work at all without nodejs-legacy?
> If not, then npm itself should be moved to contrib!


Actually i believe most modules just work without nodejs-legacy, and npm
itself
has some uses without installing it either.

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#837929: npm: Should suggest nodejs-legacy

[Jonas Smedegaard]

Quoting Matijs van Zuijlen (2016-09-16 09:57:52)
> I read through bug 614907, and I think the very best solution would be 
> for npm to ensure the correct node executable is referenced in each 
> package's executable. I don't know how feasible that would be.

Arguably the "very best" would be to drop npm from Debian ;-)

More to the point, however: Do npm work at all without nodejs-legacy?
If not, then npm itself should be moved to contrib!

 - 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

[Pkg-javascript-devel] Bug#837929: npm: Should suggest nodejs-legacy

[Jérémy Lal]

(reordered your reply to the bottom)

On 15/09/16 19:22, Jonas Smedegaard wrote:
> > Quoting Jérémy Lal (2016-09-15 17:21:30)
> >> 2016-09-15 17:12 GMT+02:00 Matijs van Zuijlen :
> >>
> >>> Package: npm
> >>> Version: 1.4.21+ds-2
> >>> Severity: wishlist
> >>>
> >>> Executables installed with npm need the /usr/bin/node executable, which
> >>> is provided in the nodejs-legacy package. This information is currently
> >>> only in the README.Debian file. I think it would be really helpful to
> >>> add nodejs-legacy to the npm package's Suggests:, or even Recommends:.
> >>>
> >>>
> >> Well, re-reading
> >> https://lists.debian.org/debian-devel-announce/2012/07/msg2.html
> >> paragraph 2 says
> >>
> >>> No package in the archive may depend on or recommend
> >>> the nodejs-legacy package, which is provided solely for upstream
> >> compatibility.
> >>
> >> Taken literally, it doesn't forbid Suggest. Does it ?
> >
> > I agree we are not forbidden from suggesting: Seems to me the choice of
> > words by the Technical Committee was deliberate, as that matches how
> > packages outside of Debian (i.e. non-free stuff) is allowed to be
> > suggested only.
>

2016-09-16 9:57 GMT+02:00 Matijs van Zuijlen :

> I read through bug 614907, and I think the very best solution would be
> for npm to ensure the correct node executable is referenced in each
> package's executable. I don't know how feasible that would be.
>

While it looks pleasant, the executable name is referenced in js code, in
makefiles,
bash files, json files, and possibly in very hidden ways.
It wouldn't be the best solution, it would be the riskiest one.

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#837929: Bug#837929: npm: Should suggest nodejs-legacy

[Sebastiaan Couwenberg]

On 09/16/2016 09:57 AM, Matijs van Zuijlen wrote:
> I read through bug 614907, and I think the very best solution would be
> for npm to ensure the correct node executable is referenced in each
> package's executable. I don't know how feasible that would be.

That's unfeasible in my opinion. The best you can get expect is for npm
to suggest nodejs-legacy to help remind you that you need that package
for /usr/bin/node. All Node.js users on Debian should already be
familiar which that situation and install nodejs-legacy when they need it.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



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#837929: npm: Should suggest nodejs-legacy

[Matijs van Zuijlen]

I read through bug 614907, and I think the very best solution would be
for npm to ensure the correct node executable is referenced in each
package's executable. I don't know how feasible that would be.

Regards,
Matijs

On 15/09/16 19:22, Jonas Smedegaard wrote:
> Quoting Jérémy Lal (2016-09-15 17:21:30)
>> 2016-09-15 17:12 GMT+02:00 Matijs van Zuijlen :
>>
>>> Package: npm
>>> Version: 1.4.21+ds-2
>>> Severity: wishlist
>>>
>>> Executables installed with npm need the /usr/bin/node executable, which
>>> is provided in the nodejs-legacy package. This information is currently
>>> only in the README.Debian file. I think it would be really helpful to
>>> add nodejs-legacy to the npm package's Suggests:, or even Recommends:.
>>>
>>>
>> Well, re-reading
>> https://lists.debian.org/debian-devel-announce/2012/07/msg2.html
>> paragraph 2 says
>>
>>> No package in the archive may depend on or recommend
>>> the nodejs-legacy package, which is provided solely for upstream
>> compatibility.
>>
>> Taken literally, it doesn't forbid Suggest. Does it ?
> 
> I agree we are not forbidden from suggesting: Seems to me the choice of 
> words by the Technical Committee was deliberate, as that matches how 
> packages outside of Debian (i.e. non-free stuff) is allowed to be 
> suggested only.
> 
> 
>  - Jonas
> 



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] node-text-encoding_0.6.1-1_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 15 Sep 2016 16:55:13 +0200
Source: node-text-encoding
Binary: node-text-encoding libjs-text-encoding
Architecture: source
Version: 0.6.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Julien Puydt 
Description:
 libjs-text-encoding - Polyfill for the Encoding Living Standard's API 
(JavaScript lib)
 node-text-encoding - Polyfill for the Encoding Living Standard's API (Node.js 
module)
Changes:
 node-text-encoding (0.6.1-1) unstable; urgency=medium
 .
   * New upstream release.
Checksums-Sha1:
 35bf81f5d16a83d8e8769c05134fad2d5abd5877 2144 node-text-encoding_0.6.1-1.dsc
 b804c5eba613d42f96e8bef3b2e7b7b815ee31de 542311 
node-text-encoding_0.6.1.orig.tar.gz
 a7f5aafb0805d15abb5caa85103898227e032db6 2680 
node-text-encoding_0.6.1-1.debian.tar.xz
Checksums-Sha256:
 216c251d286dfb46175c01ebf62fa6979bac88f52f3b4e699a310f6348122393 2144 
node-text-encoding_0.6.1-1.dsc
 b35e4a88ef4c5aabfa01d6f684689a56f3a649e25f98a86188bb007407556a5f 542311 
node-text-encoding_0.6.1.orig.tar.gz
 3adedbd7518ffc39110adb41828c73dff4f6f0a979aae05eb097685fc75e53b3 2680 
node-text-encoding_0.6.1-1.debian.tar.xz
Files:
 c413ac2d1310ab285fb89c508838b199 2144 web optional 
node-text-encoding_0.6.1-1.dsc
 ecb6a55e2d2e2495f4ca99c01f4c52d6 542311 web optional 
node-text-encoding_0.6.1.orig.tar.gz
 ddb53e631083db8dc74286ad3bd48ed6 2680 web optional 
node-text-encoding_0.6.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJX25BsAAoJEEsEP825REVAP3MP/jkuLPIc+7u3w5z6ojWuo57z
ezegRO+V0rFwOvSQrp0omQdfurzzsVpJSSaGHzGsXxnjj4u7n/XjfN23TLUPGcXH
E8jMmhmkfyYxKWDbzl2qWQDJ7S2QASmim3Dtz2th5ijDE0gLhGJuot2+akqBn2Cj
uFWIkNfIrJiYwhqD4GKFao0LDsLy17UyeIIlmMqOTVu1b7T798cke7aR4EdRZ1ek
Z2isC5b10SWCPH2oUFagrNuj1Y1n0yjjCsk76yXmOVmB6Zyylh0LkcRqEBT+Iabq
bJGp87h8R6EhJ/DP00j5pAIAgfCFpENriw1uxLVzSS/sQvHjP/seImzDEk39IeyU
DeR0hebw9SaIq/X09++qaVvuDsy67ur0B89gISKvpfCM2YoIbhwAtqBXblDGJumV
py8Uv87vAZAoHGMc1Um9mkwthgUXj5dBxT84YDNueSxdRzDjDZSpWiaKKWORFf0f
jZLE6JkF1rNW+ufpg0PQK5HqqGhY/pnQ7sgZfBqjevOdFIZmnPM0vuq7XitlmTmj
y1VdNUsxCyS3CbXOk2hLWhXakYdF4lmaokQyNS6HDmhHeYKJI5lFqOxGaWVqYARh
MWNirH6SLaoNge4AFrWcXJw6A51CT4QtQeIhVSlxzGx4A5P3mkiefPjJ2RJugeHT
9V8N9iQMNeWuup1YNzee
=nHjH
-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 node-text-encoding_0.6.1-1_source.changes

[Debian FTP Masters]

node-text-encoding_0.6.1-1_source.changes uploaded successfully to localhost
along with the files:
  node-text-encoding_0.6.1-1.dsc
  node-text-encoding_0.6.1.orig.tar.gz
  node-text-encoding_0.6.1-1.debian.tar.xz

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