[Pkg-javascript-devel] Bug#800580: nodejs: CVE-2015-7384: HTTP Denial of Service Vulnerability

[Salvatore Bonaccorso]

Source: nodejs
Version: 4.1.1~dfsg-2
Severity: important
Tags: security upstream

Hi,

the following CVE was published for nodejs on [0], but details and
patches will by available on Monday the 5th of October 2015. But
accordidng to upstrema 4.1.1 is affected, so filling this bug already. 

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://groups.google.com/forum/#!topic/nodejs-sec/fSNEQiuof6I

Regards,
Salvatore

___
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] Ultimas plazas - Seminario 2015

[Yolanda Oglivie]

Este curso enseña y refuerza prácticas y técnicas contables actuales, 
enfocándose a enfatizar el significado de la información contable y su
utilización por todas las personas que forman parte o Requieren entender el 
área contable financiera.
Haga su consulta aquí ( http://form.jotform.co/form/52493634025858? ):
Expertos en capacitación | Web: www.competencias.com.pa | Tel: 388-6215 - 
388-6217 | eMail: i...@competencias.com.pa

Borrar suscripción (
http://ec2-52-22-116-246.compute-1.amazonaws.com/index.php?subid=74277=com_acymailing=user=out=32=SDHPD4gG6ki6Gz
 )



___
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-util-deprecate_1.0.1-1_amd64.changes ACCEPTED into unstable, unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 28 Sep 2015 22:06:45 +0200
Source: node-util-deprecate
Binary: node-util-deprecate
Architecture: source all
Version: 1.0.1-1
Distribution: unstable
Urgency: low
Maintainer: Debian Javascript Maintainers 

Changed-By: Ross Gammon 
Description:
 node-util-deprecate - Node.js's `util.deprecate()` function with browser 
support
Closes: 796365
Changes:
 node-util-deprecate (1.0.1-1) unstable; urgency=low
 .
   * Initial release (Closes: #796365)
Checksums-Sha1:
 f21203278a99405d579817b56b4cf3583c9a501b 2084 node-util-deprecate_1.0.1-1.dsc
 f5d07eba02b3c75e072c98ac3d43b47b6422c947 2249 
node-util-deprecate_1.0.1.orig.tar.gz
 6fe5ca414305e4a17a34da45b0de56b2aac8fcbc 2400 
node-util-deprecate_1.0.1-1.debian.tar.xz
 53b09e75a99ae4b7dc6348251cb3d3591d44c885 3724 
node-util-deprecate_1.0.1-1_all.deb
Checksums-Sha256:
 8baf341a26b29b512f6b1637dc97651fa5b4c5ad76395c0e7cad34d2c06d6864 2084 
node-util-deprecate_1.0.1-1.dsc
 bbd1504901f0224a2a558951e107b57d02832c56598d5d122f8570d631aaf3f4 2249 
node-util-deprecate_1.0.1.orig.tar.gz
 92c5cc17fd446bdf262d6a506cbe84cefee539c36b3d6b65b22ca40e7beb4459 2400 
node-util-deprecate_1.0.1-1.debian.tar.xz
 2e32ceafe833ad81abc52fa43b08dd33a6af2178c9eea0343d536b6420a0660f 3724 
node-util-deprecate_1.0.1-1_all.deb
Files:
 ab55a977c4c8a0e65de07d0499060296 2084 web optional 
node-util-deprecate_1.0.1-1.dsc
 e1f4bd7f36b20d32911eff66a2418643 2249 web optional 
node-util-deprecate_1.0.1.orig.tar.gz
 0f174558ff5e6b118cd130da1f572ee0 2400 web optional 
node-util-deprecate_1.0.1-1.debian.tar.xz
 47c1a4ecff55f6a307875388cf847c61 3724 web optional 
node-util-deprecate_1.0.1-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWCnQtAAoJEPNPCXROn13ZdBUQALINfqegNWrHcL6UScLAX4V8
OXs2fR6KeeDmhST8EJHC9t87YdcooMFQMW+4jN/uafY8NAqzVyjqsoK7uNUPj3TY
xi4kMTmCkpOTtjYtGOSMAmywoYK8Zy/1kC2JFExJRneqghkBltPb0qNIs84s4oOV
uu7ikbJsn6gPZsz6PZUKW+M+c9cRiHboX3+yfhUGBWYaU17rcwDZtvbXucPTe92e
Z2ztt1PPMEQ7i0NTUsj0LTDEFYq0h6HCkO7JYyDYJUZv9sh3olReAIez6/jJhv1N
IOu0BNa7Gl7QydwmPglUofH0HPxQZmUThfcY3lJGs9bJiVK/Cv1IxPY6paOyt2pZ
+47nJd9znsNn1C889L5chaNN4tnyXVo9GSD/PvSrJx0U+C0Gp3yABi9gZ7v+KNY8
+GjjHeixbjfqRYtE1q3fB30OokX3Bl3bRSI5t5VEYdLl5vDwBWsWXH+j4wuRi/Fu
7xaLFNkqMsqSyC6g0amnn6mnVWVz5A9h+riCH3RN49euuNaoGwCLH6kZ2AiaiHf5
Sr3tCXhLKAb1QvdT8xhwWgjQ/XVSYwnY90f6c8hsfSIj3flJ1ztKr+zO8BTVkCZ2
Kfhs8ZJa7PbDAvfgt8Pjc6eTQAu7in3P38SHW5YEf+1xi9KERSAPf8RbmO3FoDHw
Dr/LzbSQKrM1KsviwBti
=mRdm
-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] libjs-bootswatch_3.3.5+2+dfsg1-1_amd64.changes ACCEPTED into unstable, unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 03 Sep 2015 10:45:40 +0200
Source: libjs-bootswatch
Binary: libjs-bootswatch
Architecture: source all
Version: 3.3.5+2+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Thomas Goirand 
Description:
 libjs-bootswatch - themes for Twitter Bootstrap
Closes: 797875
Changes:
 libjs-bootswatch (3.3.5+2+dfsg1-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #797875)
Checksums-Sha1:
 f1e3bb292a070373f32ae07e0f245e3f017848cc 2130 
libjs-bootswatch_3.3.5+2+dfsg1-1.dsc
 b628733dc2b08511fbd51da3b525d242319f4361 511468 
libjs-bootswatch_3.3.5+2+dfsg1.orig.tar.xz
 0e861393044ea460f644a8c6fb2ae913612030bf 6028 
libjs-bootswatch_3.3.5+2+dfsg1-1.debian.tar.xz
 61754a911a8dc1af5a97a2449a6b9518d84b5c34 550550 
libjs-bootswatch_3.3.5+2+dfsg1-1_all.deb
Checksums-Sha256:
 38646ed3d226abd119278059244a89fdef3f2ca669a088b9335b8a12cb35d2ae 2130 
libjs-bootswatch_3.3.5+2+dfsg1-1.dsc
 f394f56a8e67fedc72b95320f6cee7beb226ef2fee9f0645a5f2633de55e125c 511468 
libjs-bootswatch_3.3.5+2+dfsg1.orig.tar.xz
 19cb0ecef8c5fd3f9b908ad24b32b82a9fd1c08ab1fe7e960f6409a119eeed57 6028 
libjs-bootswatch_3.3.5+2+dfsg1-1.debian.tar.xz
 6fc1a23e4f486dfc4542eb7dd4f691db59777daa65a2fa56da2ba33acd75dc5b 550550 
libjs-bootswatch_3.3.5+2+dfsg1-1_all.deb
Files:
 6569a9ec28b4675544c01769601e7c3e 2130 web extra 
libjs-bootswatch_3.3.5+2+dfsg1-1.dsc
 8925ee7eb8d0c4aa3594236dee5584c8 511468 web extra 
libjs-bootswatch_3.3.5+2+dfsg1.orig.tar.xz
 dd80a29b4803196ca521a75f17e2b059 6028 web extra 
libjs-bootswatch_3.3.5+2+dfsg1-1.debian.tar.xz
 935515ca519c1b48e582aa894175db83 550550 web extra 
libjs-bootswatch_3.3.5+2+dfsg1-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJV8CchAAoJENQWrRWsa0P+R4QP/04O0wlEqzNbTRoIPEqfYnWX
VxIZs70DDsN1/TRnXKGPo7T+TkSERtLqmT2xWoVTIYm2hSyX6oW63CUuuAIlTrLl
J9ehKkXDxnGbJcz8K6wrQwwVEg5jxjv/cyrDhhMFcVM2dF0Gu7nusWEwIpRWePQU
sn2onjgzK0jeaetvAbbhsow3r4NCLoka1orZPWgbukOclNs2qsOvHQ8z8vPH9bRZ
pa1SdJChGqmN9+ofKOphvV5qGi8GhFgxziInjoM7Rctw5Bn97X2FOZGyOoJD82Nw
X2AflYfEdOmdNYOOpWtFk7PFVcFcwS8HDt7lmin5g2e7WgckcuLtM2tpeMLfUesc
uMdg7BHvQ4PSDmOzoUCwNnr7vGozcd31hMnbxnAgHkeCe8aN0KL1LlDGlAYOfQmO
i+7rBd2MXEYV/U5z8sc3hPZXq1YNBUPeln9RmEm4WZszKdYyOu6l0tQg6vfEr9mB
tZcWOxUbk+odBVFgDkVtYk+3qDG7hxY5oA6hZIcUY6SoGot9ijKZflKN/1YXGLMz
8jHrBFX1tXm60fJC4jFTQutsvmDNkfpyDsotQfQFMicXoAP2SYYKRQMeIW1RQVfr
eL3FtGUmO87oxXUVVMaakvtvA1WH+aBMe1m8dOkfvECU8lmnsCka00e7tD+VUFW8
ldiR8gJGATGz5Gg0XGF2
=pLX3
-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] libuv1_1.7.5-1~bpo8+1_source.changes ACCEPTED into jessie-backports

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 01 Oct 2015 12:53:00 +0200
Source: libuv1
Binary: libuv1-dev libuv1 libuv1-dbg
Architecture: source
Version: 1.7.5-1~bpo8+1
Distribution: jessie-backports
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Luca Bruno 
Description:
 libuv1 - asynchronous event notification library - runtime library
 libuv1-dbg - asynchronous event notification library - debugging symbols
 libuv1-dev - asynchronous event notification library - development files
Closes: 799446
Changes:
 libuv1 (1.7.5-1~bpo8+1) jessie-backports; urgency=medium
 .
   * Rebuild for jessie-backports.
 .
 libuv1 (1.7.5-1) unstable; urgency=medium
 .
   * New upstream release
   * Updated test patch for iovec testsuite failures
 .
 libuv1 (1.7.4-2) unstable; urgency=medium
 .
   * Initial porting to kFreeBSD (Closes: #799446)
 .
 libuv1 (1.7.4-1) unstable; urgency=medium
 .
   * New upstream release
 .
 libuv1 (1.7.3-1) unstable; urgency=medium
 .
   * New upstream release
 + Bugfix for a regression in threadpool work scheduling
 .
 libuv1 (1.7.2-1) unstable; urgency=medium
 .
   * New upstream release
 .
 libuv1 (1.7.1-1) unstable; urgency=medium
 .
   * New upstream release
 + test patch for iovec test failures
   * symbols: fixes for non-linux ports
 .
 libuv1 (1.7.0-1) unstable; urgency=medium
 .
   * New upstream release
 + upstream tarballs are now signed
 + skip some tests when network is unreachable
   * shlibs: add symbols file
 .
 libuv1 (1.6.1-3) unstable; urgency=medium
 .
   * testsuite: attempt at fixing test runner on mips/mipsel
Checksums-Sha1:
 ea0523b884140496dc73dd434c7ca4c4e47258ca 2092 libuv1_1.7.5-1~bpo8+1.dsc
 65aec47e56424290d143162b5dd2966e93cd50b3 23412 
libuv1_1.7.5-1~bpo8+1.debian.tar.xz
Checksums-Sha256:
 4a4e20a1a7db05b838749c17fc008d2b7907ab729e9c8029c50fe0ab4505809d 2092 
libuv1_1.7.5-1~bpo8+1.dsc
 042b65d750fa51d239625da3fac9c985cb6e47509df291b083ac7060bf4e23bf 23412 
libuv1_1.7.5-1~bpo8+1.debian.tar.xz
Files:
 75dfad54f8ab323b2f82da8ee2c05782 2092 libs optional libuv1_1.7.5-1~bpo8+1.dsc
 49056815fe64663fc06fbba25879666f 23412 libs optional 
libuv1_1.7.5-1~bpo8+1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJWDW3jAAoJEKmDSiJSB45Oq4EQAI8FkcR38+92a/hRbrD1cXOi
yH5WNzRNBNal3T2feccE0CiguoNrDqKuUEOGZzYsjROBU2wN0yEYkglvW9T7UnHz
oqjPKM1iIg73MIDgWUaG41vGdMrKrgMqcWjnP0cQEVb2yHJFGBTtD1BkGaL2SqLo
wwKq7eeq1ybgawmVGy+YY3r645EBAyEiDHEU9L5XqlrDJ6su6nGbW0ZT98/4sDUg
wkG3CxCQiymgSNwpTFVfc3iGlNbJw60FVDFdk77SNnU1kZwDYi16sCBU+tZ1Qmpd
rx378ebABIUnFGmY+JW5ogMzioWXxf2n8Zi/LRJ4eDltEyb6rxCyL9KNz5OKBgbx
oY99UGS/XGrkY9/gDpFmE4j+KfyIwSY6f9oBpcP5utFKap/9lFxJ7iXc9NAfemvp
lBrWJoGkaS0gLfkEWC+ED9i3m31PknFfrYeyzxNVWZTCJUhT5tAM50t4W7s2IhfJ
cDmEA9h7wRmOrbPsfBAcHYm4l8mbNh/0O5nr5MQdiqvt20xacUSbIxOPp39fHzUs
yVvOsupk+sAyO9+FSG36udTqwe3UDBrKuDKMTZrUEVimlYjqXHVaMN/2kSzfnu/T
w2/G0N3yv1WqUKxEPrCt4mLnG7+6XfkkS46R0IB1XXfZCsfrKK1hbuoCIFf73L2q
oKPXG7HawuXE2Lz1UT8H
=ceNr
-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] node-merge_1.2.0-2~bpo8+1_amd64.changes is NEW

[Debian FTP Masters]

binary:libjs-merge is NEW.
binary:node-merge is NEW.
source:node-merge 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 recieve 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

___
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] rtcninjajs_0.6.2-2~bpo8+1_amd64.changes is NEW

[Debian FTP Masters]

binary:libjs-rtcninja is NEW.
binary:node-rtcninja is NEW.
source:rtcninjajs 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 recieve 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

___
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-sdp-transform_1.4.0-2~bpo8+1_amd64.changes

[Debian FTP Masters]

node-sdp-transform_1.4.0-2~bpo8+1_amd64.changes uploaded successfully to 
localhost
along with the files:
  node-sdp-transform_1.4.0-2~bpo8+1.dsc
  node-sdp-transform_1.4.0-2~bpo8+1.debian.tar.xz
  libjs-sdp-transform_1.4.0-2~bpo8+1_all.deb
  node-sdp-transform_1.4.0-2~bpo8+1_all.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] Processing of node-bowser_0.7.3-2~bpo8+1_amd64.changes

[Debian FTP Masters]

node-bowser_0.7.3-2~bpo8+1_amd64.changes uploaded successfully to localhost
along with the files:
  node-bowser_0.7.3-2~bpo8+1.dsc
  node-bowser_0.7.3-2~bpo8+1.debian.tar.xz
  libjs-bowser_0.7.3-2~bpo8+1_all.deb
  node-bowser_0.7.3-2~bpo8+1_all.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] Processing of libuv1_1.7.5-1~bpo8+1_source.changes

[Debian FTP Masters]

libuv1_1.7.5-1~bpo8+1_source.changes uploaded successfully to localhost
along with the files:
  libuv1_1.7.5-1~bpo8+1.dsc
  libuv1_1.7.5-1~bpo8+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] jssip_0.6.34-5~bpo8+1_amd64.changes is NEW

[Debian FTP Masters]

binary:libjs-jssip is NEW.
binary:libjs-jssip-bundle is NEW.
binary:node-jssip is NEW.
source:jssip 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 recieve 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

___
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 rtcninjajs_0.6.2-2~bpo8+1_amd64.changes

[Debian FTP Masters]

rtcninjajs_0.6.2-2~bpo8+1_amd64.changes uploaded successfully to localhost
along with the files:
  rtcninjajs_0.6.2-2~bpo8+1.dsc
  rtcninjajs_0.6.2-2~bpo8+1.debian.tar.xz
  libjs-rtcninja_0.6.2-2~bpo8+1_all.deb
  node-rtcninja_0.6.2-2~bpo8+1_all.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] Processing of node-merge_1.2.0-2~bpo8+1_amd64.changes

[Debian FTP Masters]

node-merge_1.2.0-2~bpo8+1_amd64.changes uploaded successfully to localhost
along with the files:
  node-merge_1.2.0-2~bpo8+1.dsc
  node-merge_1.2.0-2~bpo8+1.debian.tar.xz
  libjs-merge_1.2.0-2~bpo8+1_all.deb
  node-merge_1.2.0-2~bpo8+1_all.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] Processing of node-is-typedarray_1.0.0-2~bpo8+1_amd64.changes

[Debian FTP Masters]

node-is-typedarray_1.0.0-2~bpo8+1_amd64.changes uploaded successfully to 
localhost
along with the files:
  node-is-typedarray_1.0.0-2~bpo8+1.dsc
  node-is-typedarray_1.0.0-2~bpo8+1.debian.tar.xz
  libjs-is-typedarray_1.0.0-2~bpo8+1_all.deb
  node-is-typedarray_1.0.0-2~bpo8+1_all.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] Processing of node-events_1.0.2-2~bpo8+1_amd64.changes

[Debian FTP Masters]

node-events_1.0.2-2~bpo8+1_amd64.changes uploaded successfully to localhost
along with the files:
  node-events_1.0.2-2~bpo8+1.dsc
  node-events_1.0.2-2~bpo8+1.debian.tar.xz
  libjs-events_1.0.2-2~bpo8+1_all.deb
  node-events_1.0.2-2~bpo8+1_all.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] node-sdp-transform_1.4.0-2~bpo8+1_amd64.changes is NEW

[Debian FTP Masters]

binary:libjs-sdp-transform is NEW.
binary:node-sdp-transform is NEW.
source:node-sdp-transform 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 recieve 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

___
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-util_0.10.3-2~bpo8+1_amd64.changes is NEW

[Debian FTP Masters]

binary:libjs-util is NEW.
binary:node-util is NEW.
source:node-util 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 recieve 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

___
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-typedarray-to-buffer_3.0.3-2~bpo8+1_amd64.changes

[Debian FTP Masters]

node-typedarray-to-buffer_3.0.3-2~bpo8+1_amd64.changes uploaded successfully to 
localhost
along with the files:
  node-typedarray-to-buffer_3.0.3-2~bpo8+1.dsc
  node-typedarray-to-buffer_3.0.3-2~bpo8+1.debian.tar.xz
  libjs-typedarray-to-buffer_3.0.3-2~bpo8+1_all.deb
  node-typedarray-to-buffer_3.0.3-2~bpo8+1_all.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] node-typedarray-to-buffer_3.0.3-2~bpo8+1_amd64.changes is NEW

[Debian FTP Masters]

binary:libjs-typedarray-to-buffer is NEW.
binary:node-typedarray-to-buffer is NEW.
source:node-typedarray-to-buffer 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 recieve 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

___
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] Hello, My private email address is (mrs.chan...@gmx.us)

[mrs.chantal;]

 
Hello,   
 
Complimentof the day to you.
 
I ammrs.chantal I am sending this brief letter to solicit your 
partnershiptotransfer $10.5 million US Dollars. I shall send you more 
information and procedureswhen I receive positive response from you. please 
send me a message in my Email box Thanks , My private emailaddress is 
(mrs.chan...@gmx.us)
 
(1)YourName
(2)Yourage.
 (3)Your full residentialaddress...
promptresponse. Best regards,
Mrs.  Chantal
Email:(mrs.chan...@gmx.us)
call meif you are instrested +226 65369757
___
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] node-websocket_1.0.19-2~bpo8+1_amd64.changes REJECTED

[Rhonda D'Vine]

   Dear Daniel,

* Daniel Pocock  [2015-09-30 09:38:07 CEST]:
> On 29/09/15 20:25, Alexander Wirt wrote:
> > we (ftpmasters) expect you to update packages in bpo regulary during the
> > whole lifetime of a suite, if you are not able to do that, the package is 
> > not
> > suitable for bpo.
> 
> Some of the node-* packages change quite frequently and I don't
> personally have time to test every one of them every time they release
> and backport them too.

 "Regularly" doesn't mean every update that hits testing.  In some
development steps it might make a lot of sense to wait for a later
upload in a bigger picture, so to say.

 But if you feel like taking regular care of the packages you backport
is too much of a trouble I suggest you to please, with sugar on top, NOT
upload them in the first place.  backports is a service that is meant to
be used in addition to stable, and thus should be taken care of in a
useful and sensible way.  That is:

 -) do not upload packages that aren't in testing (there are exceptions
to this, but in general those are rather rare than the default and it
would be convenient to ask beforehand)

 -) do not upload packages that are neither in testing nor in unstable!
Sorry, but that is absolutely off.  When you want to have a certain
middle step of a package uploaded to backports, hold back the unstable
upload until it transitioned to testing before updating unstable, making
the version you backport from disappear ...

> When I update JSCommunicator, as upstream developer, I test with a set
> of dependencies, including JsSIP and its dependencies, and everything
> that I've tested and validated is then uploaded to Debian (both unstable
> and eventually backports).  This involves testing standalone
> JSCommunicator, testing DruCall, testing on rtc.debian.org and testing
> each major browser on Linux and Android.  It is not feasible for me to
> repeat all of that every time a node-* package changes though.

 Backports is not your test field.  You are pushing the testing towards
users of an expected stable system which isn't acceptable, no matter how
feasible you consider it.

> I've uploaded a 1.0.19-1~bpo8+1 build corresponding to the version in
> testing, 1.0.19-1, this will work with the other packages that have
> already been accepted into jessie-backports yesterday.

 Thanks.  And if you want to stay in the ACL file, whenever you try to
do something out of the line, speak to us beforehand, don't let us
stumble upon it like this because that doesn't help us to be convinced
that you should be able to upload to backports directly without anyone
else involved.  You can find us in #debian-backports on irc which I know
you do use at least at times.

 So long,
Rhonda
-- 
Fühlst du dich mutlos, fass endlich Mut, los  |
Fühlst du dich hilflos, geh raus und hilf, los| Wir sind Helden
Fühlst du dich machtlos, geh raus und mach, los   | 23.55: Alles auf Anfang
Fühlst du dich haltlos, such Halt und lass los|

___
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] nodejs / LTS

[Jérémy Lal]

Hi Security Team and pkg-javascript-devel team,

may i have your opinion on this discussion about having a shared v8 package
maintained by nodejs LTS support ?

Please CC all.

2015-10-01 10:25 GMT+02:00 Moritz Mühlenhoff :

> Hi,
>
> yes i'm in favor of getting latest nodejs LTS into next debian release (be
> it 4.1 or 4.2,
>>
>> but certainly not 5.0).
>>
>
>
> 4.1.1 is the next LTS: https://github.com/nodejs/LTS/
>

I'm not reading anything on that page regarding version 4.1.1 ? The
documentation there
is a bit outdated and doesn't reflect current choices - they mention
versions and dates as
mere examples to explain their plans.

The next LTS might not be released in time for stretch:
> https://wiki.debian.org/DebianStretch
>
> Do you plan to stick with one version for the nodejs packages or to make
> them co-installable?
>

One version.
If there is a new nodejs LTS several months before Stretch transition
freeze,
then considering an update is reasonable. Future transitions are likely to
be less painful
than the nodejs 0.10 -> 4 one:
- pure js modules are mostly forward-compatible
- c++ addons API compatibility is getting better with node-nan 2.x - most
of the time
  updating node-nan and rebuilding addons will be fine.

I'm thinking of updating v8 debian package and linking against it in nodejs
>> 4 - as you know
>> that wasn't a good idea for libv8-3.14 / nodejs 0.10 as it required too
>> much work.
>> It could be more successful and maintainable if we directly use the
>> nodejs v8 bundled copy,
>> thus taking advantage of nodejs LTS security patches and enlightened
>> choices.
>>
>
> Currently nodejs is the only rdep of libv8-3.14-dev (chromium uses the
> bundled version as well).
> Given that libv8 is an unmaintainable mess I'm personally in favour of
> abandoning the packaged
> libv8 in favour of nodejs using the bundled version (since currently
> nodejs is essentially
> security-unmaintained in jessie)
>

But nodejs isn't actually the only rdep, you should check libv8-dev rdeps
as well:
weechat, uwsgi, mongodb, osmium, plv8.
The mess came from lack of v8 LTS and version ABI support.
Now that nodejs LTS is just doing that work, a shared v8 would benefit from
it.

But I can't/won't decide on this on my own, please contact
> t...@security.debian.org for a broader
>
discussion.
>

CC-ing


> PS: could we bring this discussion to pkg-javascript-devel for their
>> information ?
>>
>
> Sure, please CC me, I'm not CCed.
>

CC-ing

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] node-websocket_1.0.19-2~bpo8+1_amd64.changes REJECTED

[Daniel Pocock]

On 01/10/15 10:27, Rhonda D'Vine wrote:
>Dear Daniel,
> 
> * Daniel Pocock  [2015-09-30 09:38:07 CEST]:
>> On 29/09/15 20:25, Alexander Wirt wrote:
>>> we (ftpmasters) expect you to update packages in bpo regulary during the
>>> whole lifetime of a suite, if you are not able to do that, the package is 
>>> not
>>> suitable for bpo.
>>
>> Some of the node-* packages change quite frequently and I don't
>> personally have time to test every one of them every time they release
>> and backport them too.
> 
>  "Regularly" doesn't mean every update that hits testing.  In some
> development steps it might make a lot of sense to wait for a later
> upload in a bigger picture, so to say.
> 
>  But if you feel like taking regular care of the packages you backport
> is too much of a trouble I suggest you to please, with sugar on top, NOT
> upload them in the first place.  backports is a service that is meant to
> be used in addition to stable, and thus should be taken care of in a
> useful and sensible way.  That is:
> 
>  -) do not upload packages that aren't in testing (there are exceptions
> to this, but in general those are rather rare than the default and it
> would be convenient to ask beforehand)
> 
>  -) do not upload packages that are neither in testing nor in unstable!
> Sorry, but that is absolutely off.  When you want to have a certain
> middle step of a package uploaded to backports, hold back the unstable
> upload until it transitioned to testing before updating unstable, making
> the version you backport from disappear ...
> 

That was just an oversight with one package, it wasn't something
deliberate.  I had built the package for unstable but forgot to run dput.

>> When I update JSCommunicator, as upstream developer, I test with a set
>> of dependencies, including JsSIP and its dependencies, and everything
>> that I've tested and validated is then uploaded to Debian (both unstable
>> and eventually backports).  This involves testing standalone
>> JSCommunicator, testing DruCall, testing on rtc.debian.org and testing
>> each major browser on Linux and Android.  It is not feasible for me to
>> repeat all of that every time a node-* package changes though.
> 
>  Backports is not your test field.  You are pushing the testing towards
> users of an expected stable system which isn't acceptable, no matter how
> feasible you consider it.
> 

That is not what I said: my statement was qualified "as upstream
developer", which means this was a statement about what I do before an
upstream tag.  So the workflow is:

- upstream testing, as described above
- upstream tag/release
- unstable upload
- finally, backport


>> I've uploaded a 1.0.19-1~bpo8+1 build corresponding to the version in
>> testing, 1.0.19-1, this will work with the other packages that have
>> already been accepted into jessie-backports yesterday.
> 
>  Thanks.  And if you want to stay in the ACL file, whenever you try to
> do something out of the line, speak to us beforehand, don't let us
> stumble upon it like this because that doesn't help us to be convinced
> that you should be able to upload to backports directly without anyone
> else involved.  You can find us in #debian-backports on irc which I know
> you do use at least at times.
> 

Thanks for the feedback

Can you clarify one other thing: if a newer version of node-websocket
propagates from unstable to testing while the node-websocket backport is
in NEW, does that mean it will be rejected again?  Or will it be
accepted into backports because it had been in testing, at least at the
moment I uploaded it?

Regards,

Daniel

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