[Pkg-javascript-devel] Processing of node-stream-to-observable_0.2.0-1_amd64.changes
node-stream-to-observable_0.2.0-1_amd64.changes uploaded successfully to localhost along with the files: node-stream-to-observable_0.2.0-1.dsc node-stream-to-observable_0.2.0.orig.tar.gz node-stream-to-observable_0.2.0-1.debian.tar.xz node-stream-to-observable_0.2.0-1_all.deb node-stream-to-observable_0.2.0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] node-stream-to-observable_0.2.0-1_amd64.changes is NEW
binary:node-stream-to-observable is NEW. binary:node-stream-to-observable is NEW. source:node-stream-to-observable is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#877212: Bug#877212: node-d3-color: B-D npm not available in testing
On 09/30/2017 08:09 AM, Pirate Praveen wrote: > On വെള്ളി 29 സെപ്റ്റംബര് 2017 10:54 വൈകു, Andreas Beckmann wrote: >> Hi, >> >> with npm not available in testing (and according to #857986 this will >> not change in the near future), these node-* packages must be kept >> out of testing, since they cannot be rebuilt in testing (regardless of >> any external resources they might need additionally). > > I don't think this interpretation of policy is correct. Packages in > contrib can require packages outside archive for building or during > execution. Unstable is not outside the archive. TTBOMK, there is only one package requiring non-redistributable software outside the archive (since it is not even suitable for non-free) for building: libdbd-oracle-perl (in contrib). It has B-D: oracle-instantclient12.1-basic, oracle-instantclient12.1-devel Anyway, I'm happy to see some of the problematic node-* packages in NEW for moving to main! Andreas -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Bug#877212: node-d3-color: B-D npm not available in testing
Le 29 septembre 2017 19:34:24 GMT+02:00, "Jérémy Lal" a écrit : >2017-09-29 19:24 GMT+02:00 Andreas Beckmann : > >> Package: node-d3-color >> Version: 1.0.3-1 >> Severity: serious >> Justification: Build-Depends not satisfiable in testing >> Control: block -1 with 857986 >> Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 >> Control: reassign -2 node-d3-format 1.2.0-1 >> Control: retitle -2 node-d3-format: B-D npm not available in testing >> Control: block -2 with 857986 >> Control: reassign -3 node-d3-queue 3.0.7-1 >> Control: retitle -3 node-d3-queue: B-D npm not available in testing >> Control: block -3 with 857986 >> Control: reassign -4 node-d3-selection 1.1.0-1 >> Control: retitle -4 node-d3-selection: B-D npm not available in >testing >> Control: block -4 with 857986 >> Control: reassign -5 d3-timer 1.0.7-1 >> Control: retitle -5 d3-timer: B-D npm not available in testing >> Control: block -5 with 857986 >> Control: reassign -6 node-filesize 3.5.10+dfsg-1 >> Control: retitle -6 node-filesize: B-D npm not available in testing >> Control: block -6 with 857986 >> Control: reassign -7 node-gulp-babel 7.0.0-1 >> Control: retitle -7 node-gulp-babel: B-D npm not available in testing >> Control: block -7 with 857986 >> Control: reassign -8 node-babel-plugin-transform-define 1.3.0-1 >> Control: retitle -8 node-babel-plugin-transform-define: B-D npm not >> available in testing >> Control: block -8 with 857986 >> Control: reassign -9 node-babel 6.25.0+dfsg-8 >> Control: retitle -9 node-babel: B-D npm not available in testing >> Control: block -9 with 857986 >> Control: reassign -10 node-babylon 6.18.0-1 >> Control: retitle -10 node-babylon: B-D npm not available in testing >> Control: block -10 with 857986 >> >> >> Hi, >> >> with npm not available in testing (and according to #857986 this will >> not change in the near future), these node-* packages must be kept >> out of testing, since they cannot be rebuilt in testing (regardless >of >> any external resources they might need additionally). >> > >Build-Depending on npm is a sign something very wrong, policy-breaking, >is happening, like downloading a npm module during build. > >An example of how wrong the problem is: >``` >override_dh_auto_build: > npm install rollup >``` > >ouch > >I cc-ed everyone to make sure this doesn't happen again. Please fill a lintian bug > >Jérémy -- Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté. -- 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-has-to-string-tag-x_1.4.1+dfsg-1_amd64.changes
node-has-to-string-tag-x_1.4.1+dfsg-1_amd64.changes uploaded successfully to localhost along with the files: node-has-to-string-tag-x_1.4.1+dfsg-1.dsc node-has-to-string-tag-x_1.4.1+dfsg.orig.tar.xz node-has-to-string-tag-x_1.4.1+dfsg-1.debian.tar.xz node-has-to-string-tag-x_1.4.1+dfsg-1_all.deb node-has-to-string-tag-x_1.4.1+dfsg-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] node-has-to-string-tag-x_1.4.1+dfsg-1_amd64.changes is NEW
binary:node-has-to-string-tag-x is NEW. binary:node-has-to-string-tag-x is NEW. source:node-has-to-string-tag-x is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processing of node-is-retry-allowed_1.1.0-1_amd64.changes
node-is-retry-allowed_1.1.0-1_amd64.changes uploaded successfully to localhost along with the files: node-is-retry-allowed_1.1.0-1.dsc node-is-retry-allowed_1.1.0.orig.tar.gz node-is-retry-allowed_1.1.0-1.debian.tar.xz node-is-retry-allowed_1.1.0-1_all.deb node-is-retry-allowed_1.1.0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processing of node-commander_2.9.0-1_source.changes
node-commander_2.9.0-1_source.changes uploaded successfully to localhost along with the files: node-commander_2.9.0-1.dsc node-commander_2.9.0.orig.tar.gz node-commander_2.9.0-1.debian.tar.xz node-commander_2.9.0-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] RFS: node-commander 2.9.0
On 09/21/2017 02:21 PM, Paolo Greppi wrote: > Hi > > I have prepared a team upload to update node-commander from 2.4 to 2.9. I think we can upload to unstable directly as this is only a minor update. We need to go through experimental in case it is a major update. Else we can't really manage the large number of packages we have. > Please some DD sponsor this upload Uploaded, thanks! 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-commander_2.9.0-1_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 21 Sep 2017 08:39:30 +0200 Source: node-commander Binary: node-commander Architecture: source Version: 2.9.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Paolo Greppi Description: node-commander - Complete solution for Node.js command-line interfaces Changes: node-commander (2.9.0-1) unstable; urgency=medium . * Team upload. * Imported Upstream version 2.9.0 * Bump Standard-Version 4.1.1 * Bump debhelper compat 9 * Add build-dependency on node-graceful-readlink * Run supplied tests during build as well * Do not rename node to nodejs because of #862051 Checksums-Sha1: 1891725afcc44de2b15522863a28aff61265d94b 2099 node-commander_2.9.0-1.dsc fcccb09605588e21e314e0cea5d259323eb20a6d 20399 node-commander_2.9.0.orig.tar.gz ee192ae61ab07460015e83d568640562724e4c91 2920 node-commander_2.9.0-1.debian.tar.xz bc8878f4c4d941d4b877b9a696361121d9970aec 6229 node-commander_2.9.0-1_source.buildinfo Checksums-Sha256: adbcba322f35bafffd4e6ee465e45f2e046cde4f1fe2fb794044267f33af9a3a 2099 node-commander_2.9.0-1.dsc 1cd5b48c22ae4f82b9e00ac11f7972bf8c7ea7fe5047cdb37949e672324fa3f3 20399 node-commander_2.9.0.orig.tar.gz 4516c45e1d82ade1a9ca1e441515f9f41b86cc6ce37edae5b09522e4a12d8950 2920 node-commander_2.9.0-1.debian.tar.xz 6b40e832b291ba68111a469eeb2968ddf091cd3274ec19cac538aed75fc4 6229 node-commander_2.9.0-1_source.buildinfo Files: db960dfcff737b629878184375bb0477 2099 javascript extra node-commander_2.9.0-1.dsc 0888b72c9138d2f283e4b8c972e2b167 20399 javascript extra node-commander_2.9.0.orig.tar.gz 1275d3a5a1128bf97203cfc68e371848 2920 javascript extra node-commander_2.9.0-1.debian.tar.xz e5f21b00748466959f6630ea6c65b12f 6229 javascript extra node-commander_2.9.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEKnl0ri/BUtd4Z9pKzh+cZ0USwioFAlnPsBMACgkQzh+cZ0US wipKDxAAlv1Nd9D8qqkg+nKiHLFMBEKF4QvSe2jDJd30dqOHDgdPkX9w3PT8Gajy 5W9D9s/cZD4tNoEDIBB8jyQn3SSyx93YLkN8vMKSt5t0Qgqtz6aZBdTL/eqbFY2Z F+tKZyZ3I6T3u+v1mftxDRDfp5pIPicONQNHGqGYnRbLukKAn7GC/m+6BHZ639jX uFY5t7l1yaOMau9rRiN4grvd+o7sqSqepgJVzMvHB/ox2oYkay58Vxy/vvOgf/yr BUsCruRnBvq9bSuQhn5z24IRh8O0c/z7sJh4/Q+AQawBDKZwEyPUbKxSi15vgsrf 7i/qJNKXF36PiW+NfbgXDauj0BPDu+GRieryCK0xFecweuiEvIVcpaJkNSo0zO4t JEqCNm55jsYIk6rsh4Cp5+Lq0aU9lCU7ddzLveYk4osPHVgbU+QmS/nOT52doH11 anMGmcwBRESWxcuuwRZMTBEPVLks+s/FIkpZtnzkFxdCTDlBOOKgkpG6N8YM4bTm JEnXX9TlkHrw3zKJRfpfbyWOv6YULMtg54UWsPjKDPL//vdSnHnhf801XK93r4L9 ODfE1FxwM6Xr0KXfXAizcQJg/+GGVyDgR6DUQ9RDCh8C6WX4PXWxWV0bxyCQqWTK vyfYcxwXYQ51ghI4lmnG2b8ap+QS6/duxrTPesKCm+TRBXSY/gc= =vo6k -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-is-retry-allowed_1.1.0-1_amd64.changes is NEW
binary:node-is-retry-allowed is NEW. binary:node-is-retry-allowed is NEW. source:node-is-retry-allowed is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#877212: Bug#877212: node-d3-color: B-D npm not available in testing
Hello Pirate, On Sat, Sep 30 2017, Pirate Praveen wrote: > On വെള്ളി 29 സെപ്റ്റംബര് 2017 11:04 വൈകു, Jérémy Lal wrote: >> >> Build-Depending on npm is a sign something very wrong, >> policy-breaking, is happening, like downloading a npm module during >> build. > > Hence this is in contrib and not main (hence complying with policy), > and this is a temporary step until we get rollup in main. To my mind, this complies with the letter of Policy but not its spirit. Could you explain why it is so urgent to have node-d3-color in Debian that it can't wait on rollup arriving in main? -- Sean Whitton signature.asc Description: PGP 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#877212: Bug#877212: node-d3-color: B-D npm not available in testing
On 09/30/2017 01:30 PM, Andreas Beckmann wrote: > Unstable is not outside the archive. But that dos not seem logical. Does it mean these packages can stay in testing if we remove npm from unstable? 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
Re: [Pkg-javascript-devel] Bug#877212: node-d3-color: B-D npm not available in testing
On 09/30/2017 09:26 PM, Sean Whitton wrote: > To my mind, this complies with the letter of Policy but not its spirit. The whole purpose of having contrib and non-free is to host packages that can't be in main, either permanently or temporarily. I fail to see how it is against the spirit. > Could you explain why it is so urgent to have node-d3-color in Debian > that it can't wait on rollup arriving in main? > This is in dependency chain of gitlab https://wiki.debian.org/Javascript/Nodejs/Tasks/gitlab Packaging of rollup is stuck [1] and I can make progress with gitlab package with node-d3-color in contrib. Quite a lot of work can happen even with gitlab in contrib, like making sure everything is configured correctly, making sure update from previous version is working, people can test and report bugs while we are working on getting all dependencies in main etc. If I simply wait for rollup to arrive in main, I can't do any of those. It is much easier to move a package from contrib to main than start packaging from scratch after rollup is in main. I have been able to move many packages to main, which needed babel, using this same strategy. [1] It needs someone to port acorn-object-spread to acorn 5 https://github.com/UXtemple/acorn-object-spread/issues/5 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#877212: Bug#877212: node-d3-color: B-D npm not available in testing
2017-09-30 20:37 GMT+02:00 Pirate Praveen : > On 09/30/2017 09:26 PM, Sean Whitton wrote: > > To my mind, this complies with the letter of Policy but not its spirit. > > The whole purpose of having contrib and non-free is to host packages > that can't be in main, either permanently or temporarily. I fail to see > how it is against the spirit. > > > Could you explain why it is so urgent to have node-d3-color in Debian > > that it can't wait on rollup arriving in main? > > > > This is in dependency chain of gitlab > https://wiki.debian.org/Javascript/Nodejs/Tasks/gitlab > > Packaging of rollup is stuck [1] and I can make progress with gitlab > package with node-d3-color in contrib. Quite a lot of work can happen > even with gitlab in contrib, like making sure everything is configured > correctly, making sure update from previous version is working, people > can test and report bugs while we are working on getting all > dependencies in main etc. If I simply wait for rollup to arrive in main, > I can't do any of those. > > It is much easier to move a package from contrib to main than start > packaging from scratch after rollup is in main. I have been able to move > many packages to main, which needed babel, using this same strategy. > > [1] It needs someone to port acorn-object-spread to acorn 5 > https://github.com/UXtemple/acorn-object-spread/issues/5 > > I did a quick check on acorn and rollup and i fail to see how acorn-object-spread is related to these modules. Even the github issue is not really explicit. Can you explain please ? 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#877212: Bug#877212: node-d3-color: B-D npm not available in testing
Hello Pirate, On Sun, Oct 01 2017, Pirate Praveen wrote: > On 09/30/2017 09:26 PM, Sean Whitton wrote: >> To my mind, this complies with the letter of Policy but not its >> spirit. > > The whole purpose of having contrib and non-free is to host packages > that can't be in main, either permanently or temporarily. I fail to > see how it is against the spirit. To my mind, at least, the purpose of contrib and non-free is for packages that can't be in main for DFSG reasons /alone/. Social Contract item 5: We acknowledge that some of our users require the use of works that do not conform to the Debian Free Software Guidelines. We have created "contrib" and "non-free" areas in our archive for these works. > This is in dependency chain of gitlab > https://wiki.debian.org/Javascript/Nodejs/Tasks/gitlab > > Packaging of rollup is stuck [1] and I can make progress with gitlab > package with node-d3-color in contrib. Quite a lot of work can happen > even with gitlab in contrib, like making sure everything is configured > correctly, making sure update from previous version is working, people > can test and report bugs while we are working on getting all > dependencies in main etc. If I simply wait for rollup to arrive in > main, I can't do any of those. Okay, I see how this would be useful -- thanks for the explanation. I am still very uneasy about serving our users -- even our users of Debian unstable -- with packages that are built using material pulled from the net. I think that people who add 'contrib' to their sources.list do not expect this kind of thing. -- Sean Whitton signature.asc Description: PGP 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] Bug#877212: node-d3-color: B-D npm not available in testing
On 09/30/2017 09:10 PM, Sean Whitton wrote: > On Sun, Oct 01 2017, Pirate Praveen wrote: >> Packaging of rollup is stuck [1] and I can make progress with gitlab >> package with node-d3-color in contrib. Quite a lot of work can happen >> even with gitlab in contrib, like making sure everything is configured >> correctly, making sure update from previous version is working, people >> can test and report bugs while we are working on getting all >> dependencies in main etc. If I simply wait for rollup to arrive in >> main, I can't do any of those. > > Okay, I see how this would be useful -- thanks for the explanation. > > I am still very uneasy about serving our users -- even our users of > Debian unstable -- with packages that are built using material pulled > from the net. I think that people who add 'contrib' to their > sources.list do not expect this kind of thing. Ack. Wouldn't it be preferable to just include a copy of the prebuilt node-d3-color "binary" alongside its actual source tarball and have debian/rules just copy the prebuilt "binary" for now? That would fulfill one of the widely accepted use cases for contrib (needs something currently not in Debian to build, but is otherwise free software - see e.g. the VirtualBox BIOS requiring a non-free compiler) much closer than downloading stuff from the network. I think that requiring network access during build is a big no-no in general, regardless of where the software is sorted into. For example it fails the dissident test. And it ensures that that what's in the Debian source package is that what you actually get in the end, not subject to the whim of server operators outside of Debian during build time (which may be at any point as there are binNMUs). Regards, Christian -- 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#877212: Bug#877212: node-d3-color: B-D npm not available in testing
Hello, On Sat, Sep 30 2017, Christian Seiler wrote: > Ack. Wouldn't it be preferable to just include a copy of the prebuilt > node-d3-color "binary" alongside its actual source tarball and have > debian/rules just copy the prebuilt "binary" for now? That would > fulfill one of the widely accepted use cases for contrib (needs > something currently not in Debian to build, but is otherwise free > software - see e.g. the VirtualBox BIOS requiring a non-free compiler) > much closer than downloading stuff from the network. This does seem preferable to the current situation. -- Sean Whitton signature.asc Description: PGP 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#877212: Bug#877212: Bug#877212: node-d3-color: B-D npm not available in testing
Hi, Le 30/09/2017 à 21:06, Jérémy Lal a écrit : > > I did a quick check on acorn and rollup and i fail to see how > acorn-object-spread > is related to these modules. Even the github issue is not really explicit. > Can you explain please ? The dep thread is the following: rollup needs rollup-plugin-buble, which needs buble, which needs acorn-object-spread ; and acorn-object-spread is written for an older version of acorn than what we have in Debian. Snark on #debian-js -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] science.js is marked for autoremoval from testing
science.js 1.9.3-1 is marked for autoremoval from testing on 2017-10-23 It is affected by these RC bugs: 876618: science.js: science.js build-depends on removed nodejs-legacy -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
