[Pkg-javascript-devel] Bug#707503: node-postgres: FTBFS: xargs: node: No such file or directory
Source: node-postgres Version: 0.7.1-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: debian/rules build test -x debian/rules mkdir -p . Scanning upstream source for new/changed copyright notices... licensecheck -c '.*' -r --copyright -i '^debian/(changelog|copyright(|_hints|_newhints))' -l '9' * | /usr/lib/cdbs/licensecheck2dep5 debian/copyright_newhints 4 combinations of copyright and licensing found. WARNING: The following (and possibly more) new or changed notices discovered: License: Expat FIXME Files: debian/rules Copyright: 2011-2012, Jonas Smedegaard d...@jones.dk License: GPL-2+ To fix the situation please do the following: 1) Fully compare debian/copyright_hints with debian/copyright_newhints 2) Update debian/copyright as needed 3) Replace debian/copyright_hints with debian/copyright_newhints touch debian/stamp-copyright-check touch debian/stamp-upstream-cruft CFLAGS=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall CXXFLAGS=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall CPPFLAGS=-D_FORTIFY_SOURCE=2 LINKFLAGS=-Wl,-z,relro NOCOLOR=1 NODE_PATH=/«PKGBUILDDIR»/debian/node-pg/usr/lib/nodejs/pg/native node-waf -v configure Checking for program g++ or c++ : /usr/bin/g++ Checking for program cpp : /usr/bin/cpp Checking for program ar : /usr/bin/ar Checking for program ranlib : /usr/bin/ranlib Checking for g++ : ok Checking for node path : not found Checking for node prefix : ok /usr Checking for program pg_config : /usr/bin/pg_config 'configure' finished successfully (0.056s) touch debian/stamp-node-waf-configure NOCOLOR=1 NODE_PATH=/«PKGBUILDDIR»/debian/node-pg/usr/lib/nodejs/pg/native node-waf -v build Waf: Entering directory `/«PKGBUILDDIR»/build' [1/2] cxx: src/binding.cc - build/Release/src/binding_1.o 16:39:45 runner system command - ['/usr/bin/g++', '-g', '-O2', '-fstack-protector', '--param=ssp-buffer-size=4', '-Wformat', '-Werror=format-security', '-Wall', '-g', '-D_LARGEFILE_SOURCE', '-fPIC', '-DPIC', '-D_LARGEFILE_SOURCE', '-D_FILE_OFFSET_BITS=64', '-D_FORTIFY_SOURCE=2', '-D_GNU_SOURCE', '-I/usr/include/postgresql', '-I/usr/include/nodejs', '../src/binding.cc', '-c', '-o', 'Release/src/binding_1.o'] ../src/binding.cc: In static member function 'static v8::Handlev8::Value Connection::DispatchParameterizedQuery(const v8::Arguments, bool)': ../src/binding.cc:196:19: warning: variable 'params' set but not used [-Wunused-but-set-variable] ../src/binding.cc: In constructor 'Connection::Connection()': ../src/binding.cc:247:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] ../src/binding.cc:247:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] ../src/binding.cc:247:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] ../src/binding.cc:249:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] ../src/binding.cc:249:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] ../src/binding.cc:249:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] [2/2] cxx_link: build/Release/src/binding_1.o - build/Release/binding.node 16:39:46 runner system command - ['/usr/bin/g++', 'Release/src/binding_1.o', '-o', '/«PKGBUILDDIR»/build/Release/binding.node', '-Wl,-z,relro', '-shared', '-L/usr/lib', '-Wl,-Bdynamic', '-lpq'] Waf: Leaving directory `/«PKGBUILDDIR»/build' 'build' finished successfully (1.168s) make test make[1]: Entering directory `/«PKGBUILDDIR»' xargs: node: No such file or directory make[1]: *** [test-unit] Error 127 The full build log is available from: http://people.debian.org/~lucas/logs/2013/05/09/node-postgres_0.7.1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#707510: node-expat: FTBFS: /bin/sh: 1: node: not found
Source: node-expat Version: 1.6.0-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: debian/rules build test -x debian/rules mkdir -p . WARNING: copyright-check disabled - licensecheck (from devscripts package) is missing. touch debian/stamp-copyright-check touch debian/stamp-upstream-cruft CFLAGS=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall CXXFLAGS=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall CPPFLAGS=-D_FORTIFY_SOURCE=2 LINKFLAGS=-Wl,-z,relro NOCOLOR=1 NODE_PATH=/«PKGBUILDDIR»/debian/node-node-expat/usr/lib/nodejs node-waf -v configure Checking for program g++ or c++ : /usr/bin/g++ Checking for program cpp : /usr/bin/cpp Checking for program ar : /usr/bin/ar Checking for program ranlib : /usr/bin/ranlib Checking for g++ : ok Checking for node path : not found Checking for node prefix : ok /usr Checking for header expat.h : 16:40:01 runner system command - ['/usr/bin/g++', '-g', '-O2', '-fstack-protector', '--param=ssp-buffer-size=4', '-Wformat', '-Werror=format-security', '-Wall', '-g', '-D_FORTIFY_SOURCE=2', '-I/usr/local/include', '-I/usr/include', '../test.cpp', '-c', '-o', 'Release/test_1.o'] 16:40:01 runner system command - ['/usr/bin/g++', 'Release/test_1.o', '-o', '/«PKGBUILDDIR»/build/.conf_check_0/testbuild/Release/testprog', '-Wl,-z,relro'] yes 'configure' finished successfully (0.207s) touch debian/stamp-node-waf-configure NOCOLOR=1 NODE_PATH=/«PKGBUILDDIR»/debian/node-node-expat/usr/lib/nodejs node-waf -v build Waf: Entering directory `/«PKGBUILDDIR»/build' [1/2] cxx: node-expat.cc - build/Release/node-expat_1.o 16:40:01 runner system command - ['/usr/bin/g++', '-g', '-O2', '-fstack-protector', '--param=ssp-buffer-size=4', '-Wformat', '-Werror=format-security', '-Wall', '-g', '-fPIC', '-DPIC', '-D_LARGEFILE_SOURCE', '-D_FILE_OFFSET_BITS=64', '-D_FORTIFY_SOURCE=2', '-D_GNU_SOURCE', '-I/usr/local/include', '-I/usr/include', '-I/usr/include/nodejs', '../node-expat.cc', '-c', '-o', 'Release/node-expat_1.o'] [2/2] cxx_link: build/Release/node-expat_1.o - build/Release/node_expat.node 16:40:02 runner system command - ['/usr/bin/g++', 'Release/node-expat_1.o', '-o', '/«PKGBUILDDIR»/build/Release/node_expat.node', '-Wl,-z,relro', '-shared', '-L/usr/lib', '-L/usr/lib64', '-L/usr/local/lib', '-L/usr/local/lib64', '-Wl,-Bdynamic', '-lexpat'] Waf: Leaving directory `/«PKGBUILDDIR»/build' 'build' finished successfully (0.939s) NODE_DISABLE_COLORS=1 node test.js /bin/sh: 1: node: not found make: *** [debian/stamp-node-waf-build] Error 127 The full build log is available from: http://people.debian.org/~lucas/logs/2013/05/09/node-expat_1.6.0-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processing of ejs.js_0.8.4-1_amd64.changes
ejs.js_0.8.4-1_amd64.changes uploaded successfully to localhost along with the files: ejs.js_0.8.4-1.dsc ejs.js_0.8.4.orig.tar.gz ejs.js_0.8.4-1.debian.tar.gz node-ejs_0.8.4-1_all.deb libjs-ejs_0.8.4-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] ejs.js_0.8.4-1_amd64.changes is NEW
Mapping sid to unstable. binary:libjs-ejs is NEW. binary:node-ejs is NEW. source:ejs.js is NEW. Your package contains new components which requires manual editing of the override file. It is ok otherwise, so please be patient. New packages are usually added to the override file about once a week. ___ 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-keypress_0.1.0-1_amd64.changes
node-keypress_0.1.0-1_amd64.changes uploaded successfully to localhost along with the files: node-keypress_0.1.0-1.dsc node-keypress_0.1.0.orig.tar.gz node-keypress_0.1.0-1.debian.tar.gz node-keypress_0.1.0-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-keypress_0.1.0-1_amd64.changes is NEW
Mapping sid to unstable. binary:node-keypress is NEW. source:node-keypress is NEW. Your package contains new components which requires manual editing of the override file. It is ok otherwise, so please be patient. New packages are usually added to the override file about once a week. ___ 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#707559: ITP: node-commander -- The complete solution for Node.js command-line interfaces
Package: wnpp Severity: wishlist Owner: Mike Gabriel mike.gabr...@das-netzwerkteam.de * Package name: node-commander Version : 1.1.1 Upstream Author : TJ Holowaychuk t...@vision-media.ca * URL : https://github.com/visionmedia/commander.js * License : MIT Programming Lang: Javascript Description : The complete solution for Node.js command-line interfaces Commander is a light-weight, expressive, and powerful command-line framework for Node.js. . Inspired by Ruby's commander, this Node.js module provides command line option parsing, automated/customizable help texts, command line prompting password query, and many more features. ___ 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_1.1.1-1_amd64.changes
node-commander_1.1.1-1_amd64.changes uploaded successfully to localhost along with the files: node-commander_1.1.1-1.dsc node-commander_1.1.1.orig.tar.gz node-commander_1.1.1-1.debian.tar.gz node-commander_1.1.1-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-commander_1.1.1-1_amd64.changes is NEW
Mapping sid to unstable. binary:node-commander is NEW. source:node-commander is NEW. Your package contains new components which requires manual editing of the override file. It is ok otherwise, so please be patient. New packages are usually added to the override file about once a week. ___ 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#707571: ITP: node-channels -- Event channels in Node.js
Package: wnpp Severity: wishlist Owner: Mike Gabriel mike.gabr...@das-netzwerkteam.de * Package name: node-channels Version : 0.0.5 Upstream Author : Peter 'Pita' Martischka petermartisc...@googlemail.com * URL : https://github.com/Pita/channels * License : Apache-2.0 Programming Lang: Javascript Description : Event channels in Node.js Channels keeps your messages in order for different endpoints (channels) of your Node.js application. . In Etherpad Channels is used to ensure changes for specific pads have their own channel (gateway) and changesets (planes) are assigned to specific channels (gateways). . Channels is useful if you need to have lots of different I/O operations on different endpoints that you need to keep in order. ___ 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-channels_0.0.5-1_amd64.changes
node-channels_0.0.5-1_amd64.changes uploaded successfully to localhost along with the files: node-channels_0.0.5-1.dsc node-channels_0.0.5.orig.tar.gz node-channels_0.0.5-1.debian.tar.gz node-channels_0.0.5-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
Re: [Pkg-javascript-devel] documentation about distributing minified versions of files
On 05/08/2013 07:29 AM, Jérémy Lal wrote: There are two different needs : 1) packaged webapp that depends on libjs-* package 2) user project that depends on libjs-* package. For 1) your suggestion would work, but it wouldn't for 2). Why not? I don't see what problems it causes for that scenario. Something that would work for 2) is user Makefile that helps setup symlinks or copies of the packaged files. Symlinks if the user wants to be able to upgrade the files along with packages upgrades, copies if he doesn't. In both cases it's up to a user script to install minified/unminified version, possibly renaming the files and so on. this sounds like we would be encouraging a maintenance nightmare. what if the user adds a new script or a new symlink manually to the same directory, and then re-runs the makefile hook to bring the external dependencies up to date or to switch from minified to non-minified? for people who deploy their code from (signed) tags in a VCS, do they have to have a new tag at each deployment that re-runs this hook to adjust the links, thereby diverging from their VCS checkout? But if the user has to install libjs-jquery or libjs-jquery-minified each time, it is a painful process. why is this painful? During development, you install libjs-jquery alongside whatever other development tools, libraries, frameworks your user project depends on. your user project links to the /usr/share/javascript/jquery directory, whose contents are provided by libjs-jquery. In deployment, the sysadmins install libjs-jquery-minified on the live server instead. this installs minified files in /usr/share/javascript/jquery . the user project does not change at all. Regards, --dkg 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] documentation about distributing minified versions of files
On 09/05/2013 21:09, Daniel Kahn Gillmor wrote: On 05/09/2013 02:11 PM, David Prévot wrote: Hi, Le 09/05/2013 13:40, Daniel Kahn Gillmor a écrit : why is this painful? During development, you install libjs-jquery alongside whatever other development tools, libraries, frameworks your user project depends on. your user project links to the /usr/share/javascript/jquery directory, whose contents are provided by libjs-jquery. I fail to understand the benefit of the split (as in “what real life problem is this supposed to solve?”). It makes it possible, at a system level, to switch any particular piece of javascript into (or out of) debug mode without needing to make any changes to the rest of your webapp stack. looked at another way, it makes it possible to deploy the same code with minified javascript even though you develop with debuggable non-minified js. Is this useful? it seems like it might be to me, but i could be convinced otherwise. If the server hosts several webapps, it locks webapps in production or development mode *all at once*, and there should be a way to not do it all at once. Jérémy. 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] documentation about distributing minified versions of files
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, Le 09/05/2013 15:09, Daniel Kahn Gillmor a écrit : On 05/09/2013 02:11 PM, David Prévot wrote: Please note that some projects (including ownCloud, packaged on Debian) allow the web administrator to switch (temporarily) in debug mode, where, among other things, the non-minified JavaScript are used instead of the usual minified ones. […] interesting, thanks for this data point. does this switch work by taking advantage of the min.js suffix, or via some other mechanism? Via the .min.js suffix if I remember correctly (or other specific suffixes, since not all minified JavaScript in ownCloud use the .min.js suffix). does it work for all js (including libraries), or just for the owncloud-native js segments? All JavaScript if I remember correctly (especially since upstream embedded convenient copies of external libraries, usually replaced by symlinks in the Debian package). That reminds me we may have to add back the non-minified (symlinks to) JavaScript inside the ownCloud package (for this debug feature), so I’m going to check it again pretty soon and will be back here with more accurate data if I notice I didn’t remember correctly. […] Should we expect each framework to implement it separately? Please note that, in the ownCloud case, the non-minified JavaScript is not the only feature of the debug mode, of course (and thus can’t be addressed in a JavaScript-only generic way, and maybe not even in a generic way at all). Regards David -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJRi/x/AAoJELgqIXr9/gnykOoP/j44V8XlJPUTF7E0xGtLrns9 xoJnTxxJinHEt7f2s+j1kQAMdjq3vZ5aqdRJWBPotM86TXIZ0p4Am2XHGrWnYTTg 9FyALNvWUH1hgCiUv9pr7iC8T1alz8BIG7uMoJc+avgfmLp8XsuzChCLvXTNTVhX ObyGhFoBLHgj/qVLZbNaCqvKskxQxUdSVa49fevfw7mDP8FhKdLesZIvxEOZmVSv z+ruSW5ft2REQruWb63loT4o8bnCBOGo7vpxE2VUF23C+elnJfxYVtAzAA8P73Mx WBZhd93mS1I6OXltYTrGq2D2fmyQp3oAJ5nsxlNHq2OCLMRBjyJFzpZxIR81yNKz Fv6M4cNVH23t7nm4Y52nu89+TKYCPMq4DzSwc/peJNkZxGCwFXeX7b1nZB38CCwJ +Dg1bmo7wJ+n2ffReco29c2sTeIzWaQhtOA/5nsPRO46fginGlPN9NUWPbVJAXIY EJIW8lQRnhExDJ6ytUwAXQWZEtYujDrdjMyecTaJkzixCSl1nofq5IYkxjs3psYP JSwMApSl952mRRS9y1a9DPbdNo+LR0YNII3wEFY4g1Mcurlr87tgox+jBlOU56ZQ C/EzvWypCc+T5a4kuXjBjIZP1zYzymM/r9qQkV6MRJE3aKlDCtpMZ0IBrcKTY0bp 7G2O4SoHONbZiCDkJbOz =6d3B -END 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#707640: ITP: node-security -- Safely encoding and decoding methods with Node.js
Package: wnpp Severity: wishlist Owner: Mike Gabriel mike.gabr...@das-netzwerkteam.de * Package name: node-security Version : 1.0.0 Upstream Author : Chad Weider cwei...@oofn.net * URL : https://github.com/cweider/js-security * License : Expat Programming Lang: Javascript Description : Safely encoding and decoding methods with Node.js Safely encode/decode HTML, Javascript and CSS data compliant to the standard as demanded by the OWASP when using Node.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] Bug#707642: ITP: node-node-redis -- Redis client implementation for Node.js
Package: wnpp Severity: wishlist Owner: Mike Gabriel mike.gabr...@das-netzwerkteam.de * Package name: node-node-redis Version : 0.1.6 Upstream Author : Tim Smart t...@fostle.com * URL : https://github.com/tim-smart/node-redis * License : Expat Programming Lang: Javascript Description : Redis client implementation for Node.js Redis is a networked, in-memory, key-value data store with optional durability. . This module provides Redis client support for Node.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] Processing of node-node-redis_0.1.6-1_amd64.changes
node-node-redis_0.1.6-1_amd64.changes uploaded successfully to localhost along with the files: node-node-redis_0.1.6-1.dsc node-node-redis_0.1.6.orig.tar.gz node-node-redis_0.1.6-1.debian.tar.gz node-node-redis_0.1.6-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-node-redis_0.1.6-1_amd64.changes is NEW
Mapping sid to unstable. binary:node-node-redis is NEW. source:node-node-redis is NEW. Your package contains new components which requires manual editing of the override file. It is ok otherwise, so please be patient. New packages are usually added to the override file about once a week. ___ 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#707656: ITP: node-node-dequeue -- Simple Double Ended Queue Datastructure for Node.js
Package: wnpp Severity: wishlist Owner: Mike Gabriel mike.gabr...@das-netzwerkteam.de * Package name: node-node-dequeue Version : 1.0.3 Upstream Author : Sean (lleo) M. Egan lle...@gmail.com * URL : https://github.com/lleo/node-dequeue * License : BSD-2-clause Programming Lang: Javascript Description : Simple Double Ended Queue Datastructure for Node.js Dequeue is implemented as a doubly linked circular list with a titular head node--an empty node to designate the beginning and the end of the circularly linked list. . It is a drop-in replacement for javascript-arrays-as-fifo. ___ 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-dequeue_1.0.3-1_amd64.changes
node-dequeue_1.0.3-1_amd64.changes uploaded successfully to localhost along with the files: node-dequeue_1.0.3-1.dsc node-dequeue_1.0.3.orig.tar.gz node-dequeue_1.0.3-1.debian.tar.gz node-dequeue_1.0.3-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-dequeue_1.0.3-1_amd64.changes is NEW
Mapping sid to unstable. binary:node-dequeue is NEW. source:node-dequeue is NEW. Your package contains new components which requires manual editing of the override file. It is ok otherwise, so please be patient. New packages are usually added to the override file about once a week. ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
