Re: [Pkg-javascript-devel] can we use my fork of node-findit?
On Thu, Oct 16, 2014 at 2:17 PM, Andrew Kelley superjo...@gmail.com wrote: On Wed, Oct 15, 2014 at 12:44 AM, Jérémy Lal kapo...@melix.org wrote: What should I do? Since both have same API, i'd add your patches as quilt patches to node-findit that is already in debian and add a binary package node-findit2 (symlinking /usr/lib/nodejs/findit to findit2). Or the reverse, change upstream and add binary node-findit to node-findit2. What about this? * Add patch as quilt patch to node-findit that is already in debian * When packaging other package updates that depend on findit2, patch them to depend on node-findit instead, since the patch provides the findit2 API and bug fixes. If you are OK with that strategy, then node-findit is ready for review and upload. Also if this strategy is OK, then node-multiparty is updated and ready for review and upload. Felipe, if Jérémy says that this strategy for node-findit is OK, then the groovebasin package is updated and ready for review and upload. ___ 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] can we use my fork of node-findit?
Le jeudi 16 octobre 2014 à 14:17 -0700, Andrew Kelley a écrit : On Wed, Oct 15, 2014 at 12:44 AM, Jérémy Lal kapo...@melix.org wrote: What should I do? Since both have same API, i'd add your patches as quilt patches to node-findit that is already in debian and add a binary package node-findit2 (symlinking /usr/lib/nodejs/findit to findit2). Or the reverse, change upstream and add binary node-findit to node-findit2. What about this? * Add patch as quilt patch to node-findit that is already in debian * When packaging other package updates that depend on findit2, patch them to depend on node-findit instead, since the patch provides the findit2 API and bug fixes. I agree up to that point where you imply that findit2 has a different API ? If that's the case then findit2 must be... findit2 ! 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] Processing of node-commander_2.3.0-1_sourceupload.changes
node-commander_2.3.0-1_sourceupload.changes uploaded successfully to localhost along with the files: node-commander_2.3.0-1.dsc node-commander_2.3.0.orig.tar.gz node-commander_2.3.0-1.debian.tar.xz node-commander_2.3.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-commander_2.3.0-1_sourceupload.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 17 Oct 2014 13:22:50 +0200 Source: node-commander Binary: node-commander Architecture: source all Version: 2.3.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers pkg-javascript-devel@lists.alioth.debian.org Changed-By: Leo Iannacone l...@ubuntu.com Description: node-commander - Complete solution for Node.js command-line interfaces Changes: node-commander (2.3.0-1) unstable; urgency=medium . * Imported Upstream version 2.3.0 * Bump Standard-Version 3.9.6 * Do not install packages.json as doc * Add autopkgtest suite Checksums-Sha1: fcc9ec724993a774782d6dbe932ef2c17ea4f6ba 2085 node-commander_2.3.0-1.dsc 57379e6a18a5d5e25b1f0b87212f212a255d6c32 13844 node-commander_2.3.0.orig.tar.gz 5ffea42f39bb548aa9356b3f9030a11239c3e02d 3404 node-commander_2.3.0-1.debian.tar.xz d9470c09dbc42e526efb4a4397fdf028f30f2d53 14560 node-commander_2.3.0-1_all.deb Checksums-Sha256: ed7ff85a8607a5e57ef14b864ac97097c0e97971afc4c63fc53b3d6e74987d21 2085 node-commander_2.3.0-1.dsc 56a5ccb98110385d2792fef86a19ca449e8bc8bc77ce791e672002d23e9b701d 13844 node-commander_2.3.0.orig.tar.gz 9cfcb7fad955d4174a81e8454a317e13748b02a01edb4a3b49d6bdb3b1867d11 3404 node-commander_2.3.0-1.debian.tar.xz 2317c94fb43a7510c5f60b9c10a21200c37efc2a7c6ed2c999b5db366706f9c1 14560 node-commander_2.3.0-1_all.deb Files: 203e1654cac9d2f773efae63630f5223 2085 web extra node-commander_2.3.0-1.dsc d8a4945e1ab87a84329a3d3f40538af3 13844 web extra node-commander_2.3.0.orig.tar.gz 2d1fb6913f0b426f123b24cfe7f7fb53 3404 web extra node-commander_2.3.0-1.debian.tar.xz aff1b9dbf64b55eb1b4022380dc0a47e 14560 web extra node-commander_2.3.0-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJUQP0yAAoJEDMrlP7SgvwleLEQAIV8KX1dI66xgfw+ThQwfYyf mW7SHxRQCOWN9nAwr+iK0i6GsQSS6zuDDuP6lqJ8HxkzLj7t9YQbwG2PfdnJ5JUV eTTUT6YUY2SVb+bFt4IcvkR0aWQcTbnHP4K2ojbATOyImxTxRVw7HxaPEEfA3AV7 j8T6cbTFBcCK/3mlmy8rkQjBWxrWlm1WLOC1dhUw4HCM47DUx7EByNCG3wYXcR37 z4i++tfG7paqYaUfhbGHjsWAYBBA/6JH/9252a/qt9EmlsX8w9TBsqIoH1AVSLF/ ZyuTIsN+qe2VODlmJggtsOkNEV2SXGJlBodiBjv5G6mDDKZKZCJ6iWqsfezI+MWO gerNDf7TOHazKs4M6fVMItd7mIrIZ9WZK4EwO+mTu5qjOYWRgclvlbsb7uV4+Ni+ xlObVInTsDCBKIc8tnNJaM9iQ+OFXnjRPeGqFXC5q33QcJ75aKAoAZv67BbqudTL /ZizMc7Mb55G4QQg1fGytk+GFLNRxrST4t02qb8Zgu46/tOT2YY/KdLi5oZn4NlO x7lcmf79m0U+UQtF0EF/8aRMWbgwwiV1f2FbM+mz+eF6uQHZPN0TqYOejgwmU6kM /Ixxez250nnlFVgncyucs00DGeYgk3rOn8uvtIkgPcHRYMxui0fRy79B0f9FBs5I cOQOrYSJRL4fGzF3NHHh =WpC4 -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-htmlparser2 3.7.3-1 MIGRATED to testing
FYI: The status of the node-htmlparser2 source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 3.7.3-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] libjs-twitter-bootstrap-datepicker 1.3.1+dfsg1-1 MIGRATED to testing
FYI: The status of the libjs-twitter-bootstrap-datepicker source package in Debian's testing distribution has changed. Previous version: 0.0.0.1-1 Current version: 1.3.1+dfsg1-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. ___ 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-yauzl 2.0.1-1 MIGRATED to testing
FYI: The status of the node-yauzl source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 2.0.1-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. ___ 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] can we use my fork of node-findit?
On Fri, Oct 17, 2014 at 12:15 AM, Jérémy Lal kapo...@melix.org wrote: Le jeudi 16 octobre 2014 à 14:17 -0700, Andrew Kelley a écrit : On Wed, Oct 15, 2014 at 12:44 AM, Jérémy Lal kapo...@melix.org wrote: What should I do? Since both have same API, i'd add your patches as quilt patches to node-findit that is already in debian and add a binary package node-findit2 (symlinking /usr/lib/nodejs/findit to findit2). Or the reverse, change upstream and add binary node-findit to node-findit2. What about this? * Add patch as quilt patch to node-findit that is already in debian * When packaging other package updates that depend on findit2, patch them to depend on node-findit instead, since the patch provides the findit2 API and bug fixes. I agree up to that point where you imply that findit2 has a different API ? If that's the case then findit2 must be... findit2 ! Hmm, in this case, since upstream seems to be ignoring my pull request, maybe I will * rename the module to a better fork name (as I did with formidable - multiparty) * add new node module to debian * update packages to depend on new module * delete node-findit from debian since nothing depends on it ___ 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] can we use my fork of node-findit?
Le vendredi 17 octobre 2014 à 15:04 -0700, Andrew Kelley a écrit : On Fri, Oct 17, 2014 at 12:15 AM, Jérémy Lal kapo...@melix.org wrote: Le jeudi 16 octobre 2014 à 14:17 -0700, Andrew Kelley a écrit : On Wed, Oct 15, 2014 at 12:44 AM, Jérémy Lal kapo...@melix.org wrote: What should I do? Since both have same API, i'd add your patches as quilt patches to node-findit that is already in debian and add a binary package node-findit2 (symlinking /usr/lib/nodejs/findit to findit2). Or the reverse, change upstream and add binary node-findit to node-findit2. What about this? * Add patch as quilt patch to node-findit that is already in debian * When packaging other package updates that depend on findit2, patch them to depend on node-findit instead, since the patch provides the findit2 API and bug fixes. I agree up to that point where you imply that findit2 has a different API ? If that's the case then findit2 must be... findit2 ! Hmm, in this case, since upstream seems to be ignoring my pull request, maybe I will * rename the module to a better fork name (as I did with formidable - multiparty) * add new node module to debian * update packages to depend on new module * delete node-findit from debian since nothing depends on it If that's the case, then please keep a name close to the original one, so that when packaging a module depending on (old) findit, one can find easily the new findit to be a match. You might also want to commit to keep a backward-compatible API with node-findit. These are only suggestions. Jérémy. ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] can we use my fork of node-findit?
On Fri, Oct 17, 2014 at 3:40 PM, Jérémy Lal kapo...@melix.org wrote: Le vendredi 17 octobre 2014 à 15:04 -0700, Andrew Kelley a écrit : On Fri, Oct 17, 2014 at 12:15 AM, Jérémy Lal kapo...@melix.org wrote: Le jeudi 16 octobre 2014 à 14:17 -0700, Andrew Kelley a écrit : On Wed, Oct 15, 2014 at 12:44 AM, Jérémy Lal kapo...@melix.org wrote: What should I do? Since both have same API, i'd add your patches as quilt patches to node-findit that is already in debian and add a binary package node-findit2 (symlinking /usr/lib/nodejs/findit to findit2). Or the reverse, change upstream and add binary node-findit to node-findit2. What about this? * Add patch as quilt patch to node-findit that is already in debian * When packaging other package updates that depend on findit2, patch them to depend on node-findit instead, since the patch provides the findit2 API and bug fixes. I agree up to that point where you imply that findit2 has a different API ? If that's the case then findit2 must be... findit2 ! Hmm, in this case, since upstream seems to be ignoring my pull request, maybe I will * rename the module to a better fork name (as I did with formidable - multiparty) * add new node module to debian * update packages to depend on new module * delete node-findit from debian since nothing depends on it If that's the case, then please keep a name close to the original one, so that when packaging a module depending on (old) findit, one can find easily the new findit to be a match. You might also want to commit to keep a backward-compatible API with node-findit. These are only suggestions. I have thought about it, and I decided to keep the name as findit2. Also I agree to commit to backward-compatible API with node-findit, so that debian packages can use findit2 instead. I should have a package done here shortly. One thing that is kind of funny, is that since I cleaned up the code considerably, the lines of code is now small enough that FTP masters might say it is too small!! But hopefully if we tell them we are going to remove node-findit and this package is intended to replace it, then they will be OK with it. ___ 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] can we use my fork of node-findit?
On Fri, Oct 17, 2014 at 3:43 PM, Andrew Kelley superjo...@gmail.com wrote: On Fri, Oct 17, 2014 at 3:40 PM, Jérémy Lal kapo...@melix.org wrote: Le vendredi 17 octobre 2014 à 15:04 -0700, Andrew Kelley a écrit : On Fri, Oct 17, 2014 at 12:15 AM, Jérémy Lal kapo...@melix.org wrote: Le jeudi 16 octobre 2014 à 14:17 -0700, Andrew Kelley a écrit : On Wed, Oct 15, 2014 at 12:44 AM, Jérémy Lal kapo...@melix.org wrote: What should I do? Since both have same API, i'd add your patches as quilt patches to node-findit that is already in debian and add a binary package node-findit2 (symlinking /usr/lib/nodejs/findit to findit2). Or the reverse, change upstream and add binary node-findit to node-findit2. What about this? * Add patch as quilt patch to node-findit that is already in debian * When packaging other package updates that depend on findit2, patch them to depend on node-findit instead, since the patch provides the findit2 API and bug fixes. I agree up to that point where you imply that findit2 has a different API ? If that's the case then findit2 must be... findit2 ! Hmm, in this case, since upstream seems to be ignoring my pull request, maybe I will * rename the module to a better fork name (as I did with formidable - multiparty) * add new node module to debian * update packages to depend on new module * delete node-findit from debian since nothing depends on it If that's the case, then please keep a name close to the original one, so that when packaging a module depending on (old) findit, one can find easily the new findit to be a match. You might also want to commit to keep a backward-compatible API with node-findit. These are only suggestions. I have thought about it, and I decided to keep the name as findit2. Also I agree to commit to backward-compatible API with node-findit, so that debian packages can use findit2 instead. I should have a package done here shortly. One thing that is kind of funny, is that since I cleaned up the code considerably, the lines of code is now small enough that FTP masters might say it is too small!! But hopefully if we tell them we are going to remove node-findit and this package is intended to replace it, then they will be OK with it. Alright, node-findit2 is packaged up and ready for review and upload. I think we should send a note to the FTP masters that it will replace node-findit. ___ 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] can we use my fork of node-findit?
Le vendredi 17 octobre 2014 à 16:03 -0700, Andrew Kelley a écrit : Alright, node-findit2 is packaged up and ready for review and upload. I think we should send a note to the FTP masters that it will replace node-findit. Maybe it can be written in the long description of the package ? This module is a backward-compatible rewrite of node-findit ___ 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] can we use my fork of node-findit?
Good idea. Done. On Fri, Oct 17, 2014 at 4:06 PM, Jérémy Lal kapo...@melix.org wrote: Le vendredi 17 octobre 2014 à 16:03 -0700, Andrew Kelley a écrit : Alright, node-findit2 is packaged up and ready for review and upload. I think we should send a note to the FTP masters that it will replace node-findit. Maybe it can be written in the long description of the package ? This module is a backward-compatible rewrite of node-findit ___ 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] PCB Prototype Fabrication/Printed circuit board Supply与您共享了相册。
Dear Sir/Madam, Glad to know you from your great website, I'm proud to introduce you our high quality PCB products, Our advantage is - The most experienced PCB sample manufacture from CHINA Quick PCB Prototype Fabrication Fast shipment according to customer's requirement High quality with material Grade A FR-4 1 - 6 layer boards All free test Please kindly send us some drawings or manufacturing requirements description! We provide 10% discount for all our new customers, and for volume order please feel free to get back to us, we will assure you our best price. I would appreciate if you forward this letter to Technical Manager or to other expert responsible for technical integration of new products in your company, for we could discuss all the details of our future cooperation. Thanks for your attention to the above, we look forward to hearing back from you. Best regards, NiLu https://picasaweb.google.com/lh/sredir?uname=11373304602496030target=ALBUMid=6056634317235226705authkey=Gv1sRgCMvIsqqWr83TuAEinvite=CJuxv4cDfeat=email ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] libjs-twitter-bootstrap-datepicker is marked for autoremoval from testing
libjs-twitter-bootstrap-datepicker 1.3.1+dfsg1-1 is marked for autoremoval from testing on 2014-11-17 It (build-)depends on packages with these RC bugs: 750717: twitter-bootstrap: FTBFS against uglify 2.x series - -nc is not a supported option ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
