[Pkg-javascript-devel] Nieuwsbrief met nieuwe veilingen
Voeg n...@io-auctions.nl toe aan je adressenboek om er zeker van te zijn dat je e-mails van I&O Auctions zult ontvangen This mail has been sent to: pkg-_javascript_-devel@lists.alioth.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] rickshaw is marked for autoremoval from testing
rickshaw 1.5.0.dfsg-1 is marked for autoremoval from testing on 2014-12-23 It (build-)depends on packages with these RC bugs: 768719: d3: FTBFS in jessie: build-dependency not installable: node-jsdom ___ 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] jarisplayer is marked for autoremoval from testing
jarisplayer 2.0.15+20131104~dfsg-1 is marked for autoremoval from testing on 2014-12-08 It is affected by these RC bugs: 768738: jarisplayer: FTBFS in jessie: build-dependency not installable: haxe ___ 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] colors.js_1.0.3-2_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 23 Nov 2014 00:13:14 -0200 Source: colors.js Binary: node-colors Architecture: source all Version: 1.0.3-2 Distribution: unstable Urgency: low Maintainer: Debian Javascript Maintainers Changed-By: Marcelo Jorge Vieira Description: node-colors - Get color and style in your node.js console Changes: colors.js (1.0.3-2) unstable; urgency=low . * Really remove uglify from build-deps Checksums-Sha1: 430d34810d01b67aa055f9a93deeb5738171124a 1914 colors.js_1.0.3-2.dsc 7669f427e7c531470808c8cddd5b5afc6d3eeb8b 1830 colors.js_1.0.3-2.diff.gz d10aec19b52c4f38c8939583e8b10d3da7da61bc 8632 node-colors_1.0.3-2_all.deb Checksums-Sha256: dd3829dbad08aed27d8e528b0c70f3c56f08802af3e53a4c7da44ded8b3e013d 1914 colors.js_1.0.3-2.dsc ff0491942e404dc01a9b3effe814c131a4b21a02ddae69512a9118a710e43f95 1830 colors.js_1.0.3-2.diff.gz 690d4d7d697559bd60d8ec68f2a4afb9c672836c12bf4e4c13e6b967d8a3318d 8632 node-colors_1.0.3-2_all.deb Files: 7beebaf67632fca055664b3f1d427423 1914 web optional colors.js_1.0.3-2.dsc ba278768616e482b7be87ad6798d84a1 1830 web optional colors.js_1.0.3-2.diff.gz 01baa7a45238002baf23e9e392bedb78 8632 web optional node-colors_1.0.3-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUcUMHAAoJEFuSTuMQBVzTx1kP/2IVnPF9H8MEHhTytv1nFz3O djz+V0giE8GTV+SeT7PpaCv7GkYh/lQdoefdHXx5tz+ndnUDH1g9iKiS6sSLYD22 3bUDtZPGAD1gpTec/Ho2wY9fLjroA4p8wp68WAQgdx49H6Y5LVYwQItfmXJg/S5A KJ8+iUPuWrxd7SXDnxDMZRVLk4cfiMGu/Ci9UaECJ9ug9qRXTfLa2lU7ti4koJve wAZ7JjiXFZCSNItnxFr6uP7VE+7vi5Y5ywqjl6raZY83tQ9Twy0j8PDH/9vNyupU Ndgo0/uc8g/ivXa6h3rLeD6rM96A6XOnnrXRj91EMvf/Iw56fZrtTUn/exwL4eik 0pFzm81P/P+ykqqcSs+FqUmlGPgwzqj7oysifTVQxQncNdm7DBcvFoFAA7DzvctM K7rhQmEWNAJdYIw7ftJhQutF8lnsHwFZ8PIdUQbNWLp81jf/Pjtjl9ZIj6SpkTZe E9TtT7nPYf28mKi5AJf8lfcc9EpbnJcvsRJEzIdfF2gnjhiQzfl7qcnFLtzvXJ8O oLDAyoyG70ur+2e+e77S3lP1HfXu0NKSdbG7J30p2d7A9RoisV3sJcaTeoIrlDji lAvog36Ff5BbG1TLGBhF4EN0NQwSWj8a0divzSr6NtrX0NWN8IxLmBqTyeuKQybS nSiacVnKaPuZRAU2WRai =2uVc -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] explorercanvas_0.r3-4_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 23 Nov 2014 00:22:19 -0200 Source: explorercanvas Binary: libjs-excanvas Architecture: source all Version: 0.r3-4 Distribution: unstable Urgency: low Maintainer: Debian Javascript Maintainers Changed-By: Marcelo Jorge Vieira Description: libjs-excanvas - HTML5 Canvas for Internet Explorer Changes: explorercanvas (0.r3-4) unstable; urgency=low . * Use canonical Vcs-fields * Replaced 'yui-compressor' with 'uglifyjs' * Updated copyright format * Updated Standards-Version to 3.9.6 (no changes) Checksums-Sha1: 9f4d998904fe0a1c585de09360e64e4fe8e420ad 2000 explorercanvas_0.r3-4.dsc 0245ed199d5868b09ea942a43ba5b58f3840e274 2040 explorercanvas_0.r3-4.debian.tar.xz ec7098b6eca6f1b56c6f20ea9a632d4094899789 45286 libjs-excanvas_0.r3-4_all.deb Checksums-Sha256: d168011ed1f110f82b5039a6b070167f1f262d2a35d7fa25a6b5462f73761637 2000 explorercanvas_0.r3-4.dsc afcaa3e229d9b423988fc30439aeee1599c9dac8ad94430309404f9cf9f0c11f 2040 explorercanvas_0.r3-4.debian.tar.xz 71694fba2f85355323f3c5f1ea57f1aa016609e6b4bc81d8470d327bcefc7869 45286 libjs-excanvas_0.r3-4_all.deb Files: c5b4648ec6407eeb48a567f89359eae8 2000 web optional explorercanvas_0.r3-4.dsc 2a09d14d13ddc8d3fd99503cc22168c5 2040 web optional explorercanvas_0.r3-4.debian.tar.xz 51bfcb2fdb301b27c1c0d4491ebb3bf4 45286 web optional libjs-excanvas_0.r3-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUcUj7AAoJEFuSTuMQBVzTyuQQAJL2jlriyHFEmttkq8TzmmIU 0u45ETqA7ZKM9R+d67v6BhwFf6KDJwTzJK3OLE08xei5Wq9es7Btuhb88orEXLK1 UTFUELW/f2CYyKmwJdl12TbSWTP76K2OvA0cPNeuSOhlAGdcf24gc59ExRZdosLf TShvS4BMVGYDymFAESD2eFSJQw20HBJXvKZ1KtzgzozVzGhlH5y0d2UQWqfYBotc L3NM7bxvSXZIY6dbjdMoHjLrEq85O7nM8HfwsAGisJS3XnXUQz8sDJxWgZZS4HJ3 cBmOxPSPIYn3Za+B+KU84y+7Q7LlaKj24plscDzDwPlJeDE5rY2qOMKBiCCt7fXt mnAxFbOO2aHeK9zmZ/l7CvlEzNkRD8rVFHMOIXKWkdGPB212wKt3JRBm4SJ6Eg2w FBuWgb9WuXWfZc+OwVaHqakcHMmdfnZ+955s6n50bKO/E+2y+qzxzFxH8oS5yWN/ 75eRqikRQCMzjxIbs38OKZ5wDrSrHV5IQ/zZtouXrX54VHR+37/ErNr9b/Mcj1g5 vcYQZGaSzvCca9/Dv3EBHHal2jmv3egV8cFaUh0V3BqvqJojvxpsFCGYVbnquUvS MsVBLyP+JHeISbUW6425QwS6vmQayMcmRFVrc8Xeb5G4OZycbBMjGTGDBk6Pdgsn cGn+jghLySpuwnK57cnK =YVCv -END PGP SIGNATURE- Thank you for your contribution to Debian. ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processing of explorercanvas_0.r3-4_amd64.changes
explorercanvas_0.r3-4_amd64.changes uploaded successfully to localhost along with the files: explorercanvas_0.r3-4.dsc explorercanvas_0.r3-4.debian.tar.xz libjs-excanvas_0.r3-4_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 colors.js_1.0.3-2_amd64.changes
colors.js_1.0.3-2_amd64.changes uploaded successfully to localhost along with the files: colors.js_1.0.3-2.dsc colors.js_1.0.3-2.diff.gz node-colors_1.0.3-2_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-sink-test_1.0.2-2_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 22 Nov 2014 21:13:29 -0200 Source: node-sink-test Binary: libjs-sink-test node-sink-test Architecture: source all Version: 1.0.2-2 Distribution: unstable Urgency: low Maintainer: Debian Javascript Maintainers Changed-By: Marcelo Jorge Vieira Description: libjs-sink-test - Asynchronous JavaScript Unit Testing Framework node-sink-test - Asynchronous JavaScript Unit Testing Framework Changes: node-sink-test (1.0.2-2) unstable; urgency=low . * Remove libjs-colors dependency * Updated Standards-Version to 3.9.6 (no changes) * Use canonical Vcs-fields Checksums-Sha1: 9ccd19cdab7f4e78652fc534180c4e96b3764608 2055 node-sink-test_1.0.2-2.dsc e5622613a9dad4c31119eca276019dea210aee54 2168 node-sink-test_1.0.2-2.debian.tar.xz f6f526047fd3ca7b3b5676e4e8dafd555d6aee69 7996 libjs-sink-test_1.0.2-2_all.deb 39c8a64075f8759b1e93faf4e79e5288a3557a6a 5842 node-sink-test_1.0.2-2_all.deb Checksums-Sha256: 0ff44f6f347d4959ba5b2323a44fbde1d377df9bfce52fbd732e87da6b2241f6 2055 node-sink-test_1.0.2-2.dsc d96c12c5609a87f16327dab46713cefab513bfbdb83a1df46c6c09bfebbeec0f 2168 node-sink-test_1.0.2-2.debian.tar.xz e47e9e9a1de137f6a917fdfe854d4717726fc0a2ccb4cda27af98e02f1ae67e0 7996 libjs-sink-test_1.0.2-2_all.deb 56e12dcb8927c33aa5c5f5aa2d452f17c2c7a7c813cec8268b94932568d6fbeb 5842 node-sink-test_1.0.2-2_all.deb Files: fc203bd405a6ddd60b19fbd715ee20a2 2055 web optional node-sink-test_1.0.2-2.dsc 2f1ff5809f9d8feae5c5c8f53173e75a 2168 web optional node-sink-test_1.0.2-2.debian.tar.xz aa60114ebf639e5a13122cd4d39a6906 7996 web optional libjs-sink-test_1.0.2-2_all.deb c15da3bf516614f682763465214d52cd 5842 web optional node-sink-test_1.0.2-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUcSG6AAoJEFuSTuMQBVzTYnIP/iqIh+auRIw9/9h3BLBYQzKU PmIi/dQG6C6NkbIvwkUDoyaWJ/vekf++j9ZWuO+231gXni0aNBgB4ux4maDcDtpM W44lPMYgcaflyL0T8OHLQxNOyFVtm/1AcKsB5uWXk3Uro3JmVzryNklIgFXtlJNm XNEzHzei7MX4gnyq+62VxdY1y3QSVSQGPjlErzUh8L+EcCIkYFA8sQpNQPJbaLo5 Jm19hq+JBWZs51/w8M2M2zhRUjj48knVeVf5X5FHyEJ12APbPVQtpBF/55ZK99+T l6aDM7IEqTqfUg+if/7EKoqQcmJs1dDWlfT2lO80zh8MjjEtntQJ2s4HDbxnKR0D OtNW8aLR9vO1KIrDLJ8U+HMlX/zPFkrzDZDexY+fz9cuBUUW8XmnKD4hf9ivlIuV 21mHOcCXVoBVP+Yov47uY1wfHBOK6BBGOLsEG2Gw6dspGAFEoLHJAmGyCxpJG5Bf z078UgTjgCJfTWdeAmrqQScBqA1QLTFBcC3+SE1z+9VfxxHZWcOT3JtHqfd6KtNb P0mk49zaVdIhpkweXgrzoKkHVE14sDIyB3MG6l1G5jzFgUlnnLil9lAAfbcfsuka tLGZLsI4pqb/ygPOHwmgqC3/pKzEmeam+wy0qpXDaavigNc0nxt+UjLXeEWcYhMb vp0GGYwwwkwlYL6w0ghW =3z0B -END PGP SIGNATURE- Thank you for your contribution to Debian. ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processing of node-sink-test_1.0.2-2_amd64.changes
node-sink-test_1.0.2-2_amd64.changes uploaded successfully to localhost along with the files: node-sink-test_1.0.2-2.dsc node-sink-test_1.0.2-2.debian.tar.xz libjs-sink-test_1.0.2-2_all.deb node-sink-test_1.0.2-2_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-sink-test_1.0.2-2_amd64.changes REJECTED
node-sink-test_1.0.2-2.dsc: Invalid size hash for node-sink-test_1.0.2.orig.tar.gz: According to the control file the size hash should be 9442, but node-sink-test_1.0.2.orig.tar.gz has 9485. If you did not include node-sink-test_1.0.2.orig.tar.gz in you upload, a different version might already be known to the archive software. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns. ___ 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-sink-test_1.0.2-2_amd64.changes
node-sink-test_1.0.2-2_amd64.changes uploaded successfully to localhost along with the files: node-sink-test_1.0.2-2.dsc node-sink-test_1.0.2-2.debian.tar.xz libjs-sink-test_1.0.2-2_all.deb node-sink-test_1.0.2-2_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] Bug#770406: marked as done (libv8-3.14.5: Add libv8 virtual package with dep on latest libv8-#.#.#.)
Your message dated Sun, 23 Nov 2014 00:19:39 +0100 with message-id <1416698379.32334.3.ca...@melix.org> and subject line Re: Bug#770406: libv8-3.14.5: Add libv8 virtual package with dep on latest libv8-#.#.#. has caused the Debian Bug report #770406, regarding libv8-3.14.5: Add libv8 virtual package with dep on latest libv8-#.#.#. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 770406: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770406 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libv8-3.14.5 Version: 3.14.5.8-8 Severity: normal -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libv8-3.14.5 depends on: ii libc6 2.19-10 ii libgcc1 1:4.9.1-12 ii libstdc++6 4.9.1-12 libv8-3.14.5 recommends no packages. libv8-3.14.5 suggests no packages. -- no debconf information Adding a virtual package named libv8 will make it much easier to create packages which depend on libv8. I'm having a problem with a binary package I've created which depends on libv8. If I specify a dependency on libv8-3.14.5 directly then my package wont install on some systems. If I leave out the dep then my software wont run with out the user manually searching for the latest version of libv8 and installing it. Please help. --- End Message --- --- Begin Message --- Le samedi 22 novembre 2014 à 15:11 -0800, Joseph Coffland a écrit : > Jérémy, > > So you don't want to provide the virtual package because packages which > depend on it will likely break? I know in at least one case the portion > of the API that my package used worked with multiple versions of libv8 but > the package naming issue forced my users to install libv8 manually. > > Actually, what I really need to do is get my source package into the > Debian system. I have a fairly popular and mature Open-Source project but > I've been overwhelmed by the Debian package submission process and still > don't fully grock it. All right, If you want to use the latest available, just Build-Depend on libv8-dev. This is the answer closing the bug. Because libv8 api breaks in unforeseeable ways, it isn't updated to new branches very often, even in debian/unstable. In the future, we'll have smooth transitions with libv8-3.26 coexisting with libv8-3.14 until all software are ported to the new version. Debian is currently debugging the "jessie" release - you will have a hard(er) time getting a package uploaded in NEW - and a long time before it is accepted in the archive. We call that status "freeze". That doesn't forbid starting to work on the package... what's your software ? i'm usually curious about software using libv8. Jérémy.--- End Message --- ___ 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#770406: Bug#770406: libv8-3.14.5: Add libv8 virtual package with dep on latest libv8-#.#.#.
Hi Joseph, Quoting Joseph Coffland (2014-11-23 00:11:51) > So you don't want to provide the virtual package because packages > which depend on it will likely break? I know in at least one case the > portion of the API that my package used worked with multiple versions > of libv8 but the package naming issue forced my users to install libv8 > manually. > > Actually, what I really need to do is get my source package into the > Debian system. I have a fairly popular and mature Open-Source project > but I've been overwhelmed by the Debian package submission process and > still don't fully grock it. I recommend you to consider joining a team instead of doing package maintenance on your own - especially if new to the art of Debian packaging. For a package linked against libv8 it might be sensible to join the Javascript team - if in doubt there is interest in the team to work on the project you have, simply drop a mail to our list and ask what we feel :-) https://wiki.debian.org/Javascript Regards, - 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] colors.js_1.0.3-1_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 16 Nov 2014 16:46:33 -0200 Source: colors.js Binary: node-colors Architecture: source all Version: 1.0.3-1 Distribution: unstable Urgency: low Maintainer: Debian Javascript Maintainers Changed-By: Marcelo Jorge Vieira Description: node-colors - Get color and style in your node.js console Changes: colors.js (1.0.3-1) unstable; urgency=low . * New upstream version + Removed libjs-colors and uglify dependency * Updating debian/watch * Use canonical Vcs-fields * Updated Standards-Version to 3.9.6 (no changes) Checksums-Sha1: 9de392a20060240330f013fbc4782f1781752f81 1927 colors.js_1.0.3-1.dsc 251e2c80adf344a87a8edc6dac6f0f340b4f31c9 88656 colors.js_1.0.3.orig.tar.gz 1a457a8dd401a636c1abef34ee26bb403936f196 1795 colors.js_1.0.3-1.diff.gz 63ef2fd11d6f9fc4bcfef7730baf03f5d356f4ce 8598 node-colors_1.0.3-1_all.deb Checksums-Sha256: 29b87dc41f37bd72531bcdbfa9126bc8bf466fd990245dfe8ffcf143f131a528 1927 colors.js_1.0.3-1.dsc 7f348d4bbfe94b88435a793cb7c8d9931e7fe178f094b1e57afb86275ea8c635 88656 colors.js_1.0.3.orig.tar.gz edc7f867c77155913b93642f5e457031935ec25b1a0c1c09745b6f222981274e 1795 colors.js_1.0.3-1.diff.gz c9d570b37e85485b326fc031997498a929da50414c5a37d44f2eba3fa2d5887d 8598 node-colors_1.0.3-1_all.deb Files: fbace6be6b030fe5c967f7811a638c00 1927 web optional colors.js_1.0.3-1.dsc ce8f620ddabfde0cb449b5aef82bf11f 88656 web optional colors.js_1.0.3.orig.tar.gz e23d55b6c9fe0f61c55fef7b687b9e7a 1795 web optional colors.js_1.0.3-1.diff.gz d1d9288f88205a95e1b24a9f043f6137 8598 web optional node-colors_1.0.3-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUcRg2AAoJEFuSTuMQBVzTXAMQAJv/FMsf29rpN1pPlOSzelaF dQM//84hpGzL/PH6f9XRczGFkrC0qoep9NyBk8Q1rR06F35rQlKkOKtnexMflYsK shzL6X8x5//dyLlHICt2PmvfTtTo8LdSIv6kOnrtYkrU19ylhgMqGGrPJsgtnH99 dnKE7x35vceChlKy1/tdQKAAXcbE5jpDfUCVUbLDjwzAEzvPwZdZ+jXxdmCLEnXK BF9oeVGtcETT322r33FT65KEjg9AHRZxhVg4A68/Ot+kGKrV32cJJlaZnViX80pi 8MSf0DX8L+Oz9oT6Q89q7tgB0HMPsxLnyWqy9XHo4kUYw4NXfzWzrgcAdwS5+TJY Nf2kjnPy13mHIyK94pBFMHEwXoW2tqLHovWtynIDnRfFTLyjWqhsAiDVEIAIEbA4 eoiX1AakjafTCswNQ+u9KNZtUZuU+xAZH/cfrfHZ825Sz+F5swZR/3pP0JB6TST3 PSU0evIgxe8GmS3OUfZClhVFXD+eU5/KSNKfKYSgPhXn71OIMMP6PvZ3nYZe6bi0 YGV8LZhr/NiqwsEnZWa8xgWbAYW0YY2OF4O0OeBJCI5x+9v6VuUYbvGFLka3od2C SsLSEG0JFah4VOI7ZgRn0NKf6z8SAvyzoewHq/sZ5PeLmwC3FmbYGaMoaOaQDE4s RRK2jxMbc08E1ol4GUMu =D3T3 -END PGP SIGNATURE- Thank you for your contribution to Debian. ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processing of colors.js_1.0.3-1_amd64.changes
colors.js_1.0.3-1_amd64.changes uploaded successfully to localhost along with the files: colors.js_1.0.3-1.dsc colors.js_1.0.3.orig.tar.gz colors.js_1.0.3-1.diff.gz node-colors_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] Bug#770406: libv8-3.14.5: Add libv8 virtual package with dep on latest libv8-#.#.#.
Jérémy, So you don't want to provide the virtual package because packages which depend on it will likely break? I know in at least one case the portion of the API that my package used worked with multiple versions of libv8 but the package naming issue forced my users to install libv8 manually. Actually, what I really need to do is get my source package into the Debian system. I have a fairly popular and mature Open-Source project but I've been overwhelmed by the Debian package submission process and still don't fully grock it. Joseph On Sat, November 22, 2014 2:59 pm, Jérémy Lal wrote: > Le samedi 22 novembre 2014 à 13:26 -0800, Joseph Coffland a écrit : >> ../.. The problem >> stems from the fact that libv8 includes the library version in the >> library >> name not just in the package name. I know this has become common (boost >> does too) but it's a PITA for packages which depend on such packages. > > Actually there's a reasonable explanation for that fact : > upstream libv8 doesn't care about API compatibility between versions, > even patch-level updates can break API. > Even when API compatibility matches their version numbers, ABI > compatibility is not something upstream tries to ensure. Note that it is > more difficult to achieve with C++ libs than with C libs. > Like Boost indeed, programs depending on a given version will often > require patches to be able to be built on a later minor update, and must > all be rebuilt in any case (because of potential ABI incompatibilities). > This is a PITA - not only for debian - for all other programs depending > on libv8 and that mostly explain also why nodejs 0.10 branch was stuck > with libv8-3.14. > > I hope that (kind of) rant gives you a clearer view of the situation. > > Jérémy. > > > > -- Cauldron Development LLC http://www.cauldrondevelopment.com/ Cell: 208-409-9128 ___ 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#770406: libv8-3.14.5: Add libv8 virtual package with dep on latest libv8-#.#.#.
Le samedi 22 novembre 2014 à 13:26 -0800, Joseph Coffland a écrit : > ../.. The problem > stems from the fact that libv8 includes the library version in the library > name not just in the package name. I know this has become common (boost > does too) but it's a PITA for packages which depend on such packages. Actually there's a reasonable explanation for that fact : upstream libv8 doesn't care about API compatibility between versions, even patch-level updates can break API. Even when API compatibility matches their version numbers, ABI compatibility is not something upstream tries to ensure. Note that it is more difficult to achieve with C++ libs than with C libs. Like Boost indeed, programs depending on a given version will often require patches to be able to be built on a later minor update, and must all be rebuilt in any case (because of potential ABI incompatibilities). This is a PITA - not only for debian - for all other programs depending on libv8 and that mostly explain also why nodejs 0.10 branch was stuck with libv8-3.14. I hope that (kind of) rant gives you a clearer view of the situation. 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#768677: marked as done (node-redis: FTBFS in jessie: Tests failures)
Your message dated Sat, 22 Nov 2014 23:39:54 +0100 with message-id and subject line Not reproducible has caused the Debian Bug report #768677, regarding node-redis: FTBFS in jessie: Tests failures to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 768677: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768677 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-redis Version: 0.12.1-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > - optional_callback: 1 ms > - optional_callback_undefined: 0 ms > - enable_offline_queue_true:node_redis: no callback to send error: Length: 84 > Uncaught exception: Error: Length: 84 > at ReplyParser. (/«PKGBUILDDIR»/index.js:317:31) > at ReplyParser.emit (events.js:95:17) > at ReplyParser.send_error (/«PKGBUILDDIR»/lib/parser/javascript.js:296:10) > at ReplyParser.execute (/«PKGBUILDDIR»/lib/parser/javascript.js:181:22) > at RedisClient.on_data (/«PKGBUILDDIR»/index.js:547:27) > at Socket. (/«PKGBUILDDIR»/index.js:102:14) > at Socket.emit (events.js:95:17) > at Socket. (_stream_readable.js:748:14) > at Socket.emit (events.js:92:17) > at emitReadable_ (_stream_readable.js:410:10) > make[1]: *** [override_dh_auto_test] Error 1 > debian/rules:13: recipe for target 'override_dh_auto_test' failed The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/node-redis_0.12.1-2_jessie.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. --- End Message --- --- Begin Message --- Hi, I can't reproduce the issue. The package builds in a jessie and in a sid chroot. Regards, Andreas --- End Message --- ___ 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#770406: libv8-3.14.5: Add libv8 virtual package with dep on latest libv8-#.#.#.
Jérémy, > Your package won't install on some systems anyway, since libv8 does not > build/run on all architectures. I don't need it to install on all systems. Just the ones I support which are the same as for libv8. >>From what you say it looks like your package dependency on libv8 is > optional ? If that's the case then use a Recommends or Suggests > relationship in debian/control. I don't think I explained my problem or the solution well enough. What I would like to have is a virtual package named 'libv8' which depends on the latest 'libv8-#.#.#', whatever that maybe. This way my package only needs to depend on 'libv8' and not have to guess the version that might be installed on the user's system. Also you could then install libv8 like this: sudo apt-get install libv8 Right now you have to first search for the latest version. The problem stems from the fact that libv8 includes the library version in the library name not just in the package name. I know this has become common (boost does too) but it's a PITA for packages which depend on such packages. Thanks, Joseph -- Cauldron Development LLC http://www.cauldrondevelopment.com/ Cell: 208-409-9128 ___ 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] Nieuwsbrief I&O-dagaanbieding: Waterval, Chicco pratende timmerman, parfum, colgate tandpasta, waszakken, geheugenkaartjes & messensets
Voeg n...@io-dagaanbieding.nl toe aan je adressenboek om er zeker van te zijn dat je e-mails van I&O-dagaanbieding zult ontvangen Uw Dagaanbieding van vrijdag 21 november 2014 Deze week ook: Op I&O Dagaanbieding vind u superdeals met kortingen tot wel 100 %! Elke dag weer een leuke, exclusieve deal met veel korting aanbieden is ons doel. Bespaar veel tijd en geld door gewoon te bestellen uit je luie stoel !! Je kan je gratis inschrijven en dit neemt maar enkele seconden tijd in beslag ! Hoe werkt het ?Elke dag worden er exclusieve deals aangeboden, check dus zeker elke dag onze site voor nieuwe deals. Het spreekt eigenlijk voor zich, u plaatst een bestelling, U zorgt voor de betaling en wij zorgen dat het product zo snel mogelijk bij u thuis afgeleverd wordt. OP = OP Hulp nodig? Wij zijn niet bang voor lastige vragen en staan altijd klaar om deze op te lossen.E: i...@io-dagaanbieding.com This mail has been sent to :pkg-_javascript_-devel@lists.alioth.debian.org ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#768698: marked as done (leaflet: FTBFS in jessie: build-dependency not installable: node-jake)
Your message dated Sat, 22 Nov 2014 15:15:00 +0100 with message-id <20141122141500.gb30...@ramacher.at> and subject line Re: Bug#768698: leaflet: FTBFS in jessie: build-dependency not installable: node-jake has caused the Debian Bug report #768698, regarding leaflet: FTBFS in jessie: build-dependency not installable: node-jake to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 768698: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768698 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: leaflet Version: 0.7.3~dfsg-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > ┌──┐ > │ Install leaflet build dependencies (apt-based resolver) > │ > └──┘ > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-leaflet-dummy : Depends: node-jake but it is not > installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/leaflet_0.7.3~dfsg-1_jessie.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. --- End Message --- --- Begin Message --- On 2014-11-09 08:43:05, Lucas Nussbaum wrote: > Source: leaflet > Version: 0.7.3~dfsg-1 > Severity: serious > Tags: jessie sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20141108 qa-ftbfs > Justification: FTBFS in jessie on amd64 > > Hi, > > During a rebuild of all packages in jessie (in a jessie chroot, not a > sid chroot), your package failed to build on amd64. > > Relevant part (hopefully): > > ┌──┐ > > │ Install leaflet build dependencies (apt-based resolver) > >│ > > └──┘ > > > > Installing build dependencies > > Reading package lists... > > Building dependency tree... > > Reading state information... > > Some packages could not be installed. This may mean that you have > > requested an impossible situation or if you are using the unstable > > distribution that some required packages have not yet been created > > or been moved out of Incoming. > > The following information may help to resolve the situation: > > > > The following packages have unmet dependencies: > > sbuild-build-depends-leaflet-dummy : Depends: node-jake but it is not > > installable > > E: Unable to correct problems, you have held broken packages. > > apt-get failed. node-jake is back in testing and leaflet builds again. Closing. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature --- End Message --- ___ 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#768704: marked as done (leaflet-markercluster: FTBFS in jessie: build-dependency not installable: node-jake)
Your message dated Sat, 22 Nov 2014 15:16:07 +0100 with message-id <20141122141607.gc30...@ramacher.at> and subject line Re: Bug#768704: leaflet-markercluster: FTBFS in jessie: build-dependency not installable: node-jake has caused the Debian Bug report #768704, regarding leaflet-markercluster: FTBFS in jessie: build-dependency not installable: node-jake to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 768704: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768704 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: leaflet-markercluster Version: 0.4.0~dfsg-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > ┌──┐ > │ Install leaflet-markercluster build dependencies (apt-based resolver) > │ > └──┘ > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-leaflet-markercluster-dummy : Depends: node-jake but it > is not installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/leaflet-markercluster_0.4.0~dfsg-1_jessie.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. --- End Message --- --- Begin Message --- On 2014-11-09 08:43:02, Lucas Nussbaum wrote: > Source: leaflet-markercluster > Version: 0.4.0~dfsg-1 > Severity: serious > Tags: jessie sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20141108 qa-ftbfs > Justification: FTBFS in jessie on amd64 > > Hi, > > During a rebuild of all packages in jessie (in a jessie chroot, not a > sid chroot), your package failed to build on amd64. > > Relevant part (hopefully): > > ┌──┐ > > │ Install leaflet-markercluster build dependencies (apt-based resolver) > >│ > > └──┘ > > > > Installing build dependencies > > Reading package lists... > > Building dependency tree... > > Reading state information... > > Some packages could not be installed. This may mean that you have > > requested an impossible situation or if you are using the unstable > > distribution that some required packages have not yet been created > > or been moved out of Incoming. > > The following information may help to resolve the situation: > > > > The following packages have unmet dependencies: > > sbuild-build-depends-leaflet-markercluster-dummy : Depends: node-jake but > > it is not installable > > E: Unable to correct problems, you have held broken packages. > > apt-get failed. node-jake is back in testing and leaflet-markercluster builds again. Closing. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature --- End Message --- ___ 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#768672: marked as done (node-cssom: FTBFS in jessie: build-dependency not installable: node-jake)
Your message dated Sat, 22 Nov 2014 14:50:50 +0100 with message-id <20141122135050.ga30...@ramacher.at> and subject line Re: Bug#768672: node-cssom: FTBFS in jessie: build-dependency not installable: node-jake has caused the Debian Bug report #768672, regarding node-cssom: FTBFS in jessie: build-dependency not installable: node-jake to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 768672: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768672 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-cssom Version: 0.3.0-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > ┌──┐ > │ Install node-cssom build dependencies (apt-based resolver) > │ > └──┘ > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-node-cssom-dummy : Depends: node-jake but it is not > installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/node-cssom_0.3.0-1_jessie.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. --- End Message --- --- Begin Message --- On 2014-11-09 08:44:06, Lucas Nussbaum wrote: > Source: node-cssom > Version: 0.3.0-1 > Severity: serious > Tags: jessie sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20141108 qa-ftbfs > Justification: FTBFS in jessie on amd64 > > Hi, > > During a rebuild of all packages in jessie (in a jessie chroot, not a > sid chroot), your package failed to build on amd64. > > Relevant part (hopefully): > > ┌──┐ > > │ Install node-cssom build dependencies (apt-based resolver) > >│ > > └──┘ > > > > Installing build dependencies > > Reading package lists... > > Building dependency tree... > > Reading state information... > > Some packages could not be installed. This may mean that you have > > requested an impossible situation or if you are using the unstable > > distribution that some required packages have not yet been created > > or been moved out of Incoming. > > The following information may help to resolve the situation: > > > > The following packages have unmet dependencies: > > sbuild-build-depends-node-cssom-dummy : Depends: node-jake but it is not > > installable > > E: Unable to correct problems, you have held broken packages. > > apt-get failed. node-jake is back in testing and node-cssom builds again. Closing Cheers. -- Sebastian Ramacher signature.asc Description: Digital signature --- End Message --- ___ 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] Processed: coffeescript: diff for NMU version 1.4.0-1.1
Processing control commands: > tags 750716 + pending Bug #750716 [src:coffeescript] coffeescript: FTBFS against uglify 2.x series - Cannot call method 'parse' of undefined Added tag(s) pending. -- 750716: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750716 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
