[Pkg-javascript-devel] ✔ Uw kopieermachine gratis voor 6 maanden en de nieuwe iPad 4
Sluit een huurcontract af aan een uitzonderlijke prijs voor één van onze nieuwe multifunctionele kleuren A3 Ricoh en geniet van een hele reeks voordelen ! 1 : Geen huurgeld voor uw machine voor 6 maanden ! 2 : Uw z/b onderhoudscontract gratis gedurende de hele duur van het contract 3 : Een gratis de nieuwe iPhone 5 of de nieuwe iPad 4 voor de 50 eerste onder u ! www.vcomm.be pr...@vcomm.be Tel.: 0800 95 598 - Fax: 02 686 30 31 ___ 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] New release of jquery-goodies
Hi Agustin, On Fri, 2013-01-11 at 18:31 -0300, Agustin Henze wrote: Hi, I added slides project[0] to jquery-goodies[1] source package. Can you upload it please? I need it into unstable because I have a package (nikola) that depends on it. [0] http://www.slidesjs.com/ [1] http://anonscm.debian.org/gitweb/?p=pkg-javascript/jquery-goodies.git I will upload it ;) Have you subscribed to our mailinglist already? http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel Cheers, -- Marcelo Jorge Vieira xmpp:me...@jabber-br.org http://metaldot.alucinados.com signature.asc Description: This is a digitally signed message part ___ 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#692312:
It's strange to me this is even an issue that's being argued, I would assume that a Debian package maintainer would be responsible enough to keep up with the latest stable releases of whatever they have taken on to maintain. Back in the real-world, the biggest problem is that 0.6 and 0.8 use completely different build systems, replacing waf with gyp (both for building node and native modules). I'm sure you can appreciate and respect the depth of this problem alone. Please review the changes (published 6 months ago): https://github.com/joyent/node/wiki/API-changes-between-v0.6-and-v0.8 Rick ___ 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#692312: Bug#692312:
On Mon, Jan 14, 2013 at 03:09:42PM -0500, Rick Waldron wrote: It's strange to me this is even an issue that's being argued, I would assume that a Debian package maintainer would be responsible enough to keep up with the latest stable releases of whatever they have taken on to maintain. Back in the real-world, the biggest problem is that 0.6 and 0.8 use completely different build systems, replacing waf with gyp (both for building node and native modules). I'm sure you can appreciate and respect the depth of this problem alone. Please review the changes (published 6 months ago): [1]https://github.com/joyent/node/wiki/API-changes-between-v0.6-and-v0.8 Just read through these -- there are some seriously breaking changes new upstream releases of our node modules must be writing against this API, I'd argue keeping nodejs back holds our packaged node apps pretty badly. I mean, literally anything that touches the filesystem ... Rick References Visible links 1. https://github.com/joyent/node/wiki/API-changes-between-v0.6-and-v0.8 ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel Fondly, Paul -- .''`. Paul Tagliamonte paul...@debian.org : :' : Proud Debian Developer `. `'` 4096R / 8F04 9AD8 2C92 066C 7352 D28A 7B58 5B30 807C 2A87 `- http://people.debian.org/~paultag signature.asc Description: 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#692312: Bug#692312:
Quoting Rick Waldron (2013-01-14 21:09:42) It's strange to me this is even an issue that's being argued, I would assume that a Debian package maintainer would be responsible enough to keep up with the latest stable releases of whatever they have taken on to maintain. Back in the real-world, the biggest problem is that 0.6 and 0.8 use completely different build systems, replacing waf with gyp (both for building node and native modules). I'm sure you can appreciate and respect the depth of this problem alone. Please review the changes (published 6 months ago): [1]https://github.com/joyent/node/wiki/API-changes-between-v0.6-and-v0.8� If the purpose of above was to contribute to move this bugreport forward, then you failed: It is not at all helpful to educate on how irresponsible maintainers are, how much of a dreamworld they live in, or for how long new upstream release have been out. If the purpose was to provoke, then you succeeded. Happy now? What would help is elaborate on what renders Nodejs 0.6 branch unusable. There is currently code in Debian that will potentially be rendered unusable by the upgrade, so it would be nice to know what would be the gain compared to such potential extra burden. - 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#692312: Bug#692312:
On 14/01/2013 21:46, Jonas Smedegaard wrote: Quoting Rick Waldron (2013-01-14 21:09:42) It's strange to me this is even an issue that's being argued, I would assume that a Debian package maintainer would be responsible enough to keep up with the latest stable releases of whatever they have taken on to maintain. Back in the real-world, the biggest problem is that 0.6 and 0.8 use completely different build systems, replacing waf with gyp (both for building node and native modules). I'm sure you can appreciate and respect the depth of this problem alone. Please review the changes (published 6 months ago): [1]https://github.com/joyent/node/wiki/API-changes-between-v0.6-and-v0.8� If the purpose of above was to contribute to move this bugreport forward, then you failed: It is not at all helpful to educate on how irresponsible maintainers are, how much of a dreamworld they live in, or for how long new upstream release have been out. If the purpose was to provoke, then you succeeded. Happy now? What would help is elaborate on what renders Nodejs 0.6 branch unusable. There is currently code in Debian that will potentially be rendered unusable by the upgrade, so it would be nice to know what would be the gain compared to such potential extra burden. I agree with Jonas that there is no kind of urgency in updating nodejs. Please ignore provocations like Rick Waldron does. He has even brought that matter upstream [0]. It's a lot of work to do again, and i wish i could do it at once. Here's what i propose (mind that all will go to experimental during freeze) : Can be quickly done : * update libv8 (maybe 3.15.11.x) * update nodejs to 0.8 Takes time : * package missing node-gyp deps, update npm deps * package node-gyp 0.8.2 Rather quick once that is done : * update npm to 1.2.0 Note that i'm not pledging for someone to do that - it's my intention to do it. Helping will only make it happen sooner. Regards, Jérémy [0] https://groups.google.com/forum/#!topic/nodejs/W_6avRSG_a8 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#692312: features missing from 0.6.x
Hello! Here are some of the important changes between 0.6 and 0.8: * replaced the node-waf build system with gyp. This greatly simplifies the process of building multiplatform extensions and is the currently supported mechanism for publishing modules with architecture-specific binary components. waf has been strongly deprecated upstream * added much better support for localized error handling in the form of domains (http://nodejs.org/api/domain.html) * included numerous fixes to TLS and SSL support that have not been backported to the (now de facto end-of-life) 0.6.21 * added access to a significant number of new JavaScript language features (exposed via the --harmony comand-line flag) due to being built against a newer version of V8 * made significant improvements to the cluster and child_process core modules (involving how data is passed between processes and how file descriptors are handled) that make working with subsidiary processes more straightforward and less error-prone * perhaps least significantly (but something I use all over the place in the code I support), there is a new timer function in process.hrtime() that has nanosecond precision (if not accuracy) There are also many, many minor bug fixes and tweaks between the two at an operational level, and given that npm allows modules to specify what version of core they'll run against, there are many modules on npm (sorry, don't have an exact number for you, but I can get it if it's important) that will simply not work with the version of Node packaged for Debian. Taking a step back, upstream is getting very close to releasing 0.10, and given that it includes a newer, rationalized version of Node's support for streams, is going to result in a tremendously large delta between 0.6 and 0.10. As it stands, the version of Node distributed with Debian is unusable for me, and I regularly help confused Debian users on #node.js on Freenet either get up and running with Chris Lea's PPA (which is for a different distribution) because the version included with Node is too old for them as well. ___ 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#692312: Clarification on problems maintaining 0.6.x packages in the Node ecosystem.
This issue seems to be getting a little muddled, Rick was pointing to issues that would affect relying on newer packages of Node.js for existing code bases that target 0.6.x; however as Node Package Manager (NPM) modules continue to evolve, in particular, and target the newer versions of node certain aspects become difficult to maintain for a 0.6.x author. These issues involve: 1. Lack of support for some problems when using the WAF build system (and the purpose of moving to gyp covered in detail on node.js' mailing lists) 2. Misleading module support, due to default engine version. (see: `npm help json`'s engines field) 3. Documentation issues, missing direct links to docs on the nodejs.orgwebsite due to 0.8.x being the recommended stable release (use google to find em instead, and even then pick the right one?). 4. Various bug fixes that are not back ported. These do not break any existing code for node@0.6.x, however, they could introduce problems with maintenance, bug fixes, support, security, etc. Removing 0.6.x would be a problematic situation since there are breaking API changes, but it appears the original goal of this conversation was to include a 0.8.x package more than to remove the 0.6.x package entirely. I personally do not use the packages, but wished to clarify this since it seems to be terse conversation that leads to confusion on both ends. Jonas and Paul, can you clarify why those reasons are not encouraging, and/or a way to rephrase the original intent of the issue in a manner that is appropriate? It seems if a fork of 0.6.x was maintained and kept up to date with all the bug fixes this would be appropriate, but as documentation fixes and code fixes are not being back ported to 0.6.x it would be encouraging to know the route to take this issue. We have little wish to change your existing code, but would like to take the proper steps to update the package to a new version for both current and future reference. Thans for your patience, Bradley Meck ___ 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 dear
How are you doing today? I Hope fine. My name is Mercy Stokes. I am interested in friendship with you, if you don't mind I will like you to contact me through my email address for easy communication. I promise to send my picture to you and also tell you more about myself when I receive your mail. I believe distance and age doesn't matter in a serious relationship but love matters most. I will be waiting for your email. Yours sincerely, Mercy, ___ 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] Bonjour
Bonjour, Je vous prie de bien vouloir m'excuser pour cette intrusion qui peut paraître surprenante à première vue, d'autant plus qu'il n'existe aucune relation entre nous. Je vous adresse ce courrier qui; j'espère retiendra quelque part votre attention, j ai eu votre adresse grâce a mes propres recherches sur le Web, c'est là que j'ai décidé de vous contactez et vous parlez de mon projet. Je suis Patricia, 22ans, l’unique de mon honorable père décédé suite à un arrêt cardiaque. Je voudrais vous présenter ma situation, et solliciter votre aide pour récupérer un bien légué par mon défunt père, en espérant que je ne serai ni déçue, ni trahie. Par conséquent, je voudrais de par amour et par humanisme solliciter votre aide pour le transfert d'un patrimoine financier s'élevant à 7,5 millions de dollars américains pour un projet d'investissement afin de permettre à la création de gestion de biens immobiliers et autres nécessiteux dans une directive caritative et humanitaire de façon à ce que le passage de mon défunt père sur la terre des hommes ne soit pas un vide. Et, pour compenser votre aide, je serai ravie de vous consentir 25% du capital. Néanmoins, je voudrais avoir confirmation des informations suivantes : nom, prénom et profession. Une fois ces informations reçues, je disposerai afin de vous mettre en contact avec le bienfondé(*notaire*)et entrevoir le transfert de ces fonds en accord avec l’initiative à laquelle j’ai opté pour une mise à profit et un bon usage de ce capital. Nb: Fournir un nouveau compte sécurisé pour le transfert des fonds, Me faire parvenir une lettre d'invitation pour obtenir facilement le visa, Poursuivre mes études et Me conseiller pour investir ces fonds et sauver ma vie cause des menaces perpétuelles que me font les ennemies de mon défunt père. Veuillez croire à mes dires d’où loin de moi l’idée de toutes supercheries à caractère contraignantes ou frauduleuses. Dans l'espoir de vous lire, Recevez mes très cordiales salutations, surtout veuillez garder la discrétion, la confidentialité et l'honnêteté. Que Dieu vous bénisse! Patricia Sao. ___ 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 dear
How are you doing today? I Hope fine. My name is Mercy Stokes. I am interested in friendship with you, if you don't mind I will like you to contact me through my email address for easy communication. I promise to send my picture to you and also tell you more about myself when I receive your mail. I believe distance and age doesn't matter in a serious relationship but love matters most. I will be waiting for your email. Yours sincerely, Mercy, ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
