Re: [Pkg-javascript-devel] node-websocket_1.0.19-2~bpo8+1_amd64.changes REJECTED

On 01/10/15 10:27, Rhonda D'Vine wrote: >Dear Daniel, > > * Daniel Pocock [2015-09-30 09:38:07 CEST]: >> On 29/09/15 20:25, Alexander Wirt wrote: >>> we (ftpmasters) expect you to update packages in bpo regulary during the >>> whole lifetime of a suit

[Pkg-javascript-devel] Bug#799656: [JsSIP] Re: Bug#799656: NaN 2.x issue

On 28/09/15 18:18, Iñaki Baz Castillo wrote: > 2015-09-24 15:14 GMT+02:00 Daniel Pocock : >> Can anybody from the JsSIP team comment on this? How do you feel about >> having node-nan 2.x in the dependency hierarchy? Will you continue >> using node-websocket or would you p

Re: [Pkg-javascript-devel] node-websocket_1.0.19-2~bpo8+1_amd64.changes REJECTED

On 29/09/15 20:25, Alexander Wirt wrote: > On Tue, 29 Sep 2015, Daniel Pocock wrote: > >> >> >> On 29/09/15 20:13, Alexander Wirt wrote: >>> On Tue, 29 Sep 2015, Daniel Pocock wrote: >>> >>>> >>>> >>>&g

Re: [Pkg-javascript-devel] node-typedarray-to-buffer_3.0.3-3~bpo8+1_amd64.changes REJECTED

On 29/09/15 18:01, Alexander Wirt wrote: > > This version is not even in debian. Sorry about that, I was updating a lot of these packages and forgot to dput this one, thanks for pointing that out, I have uploaded it now ___ Pkg-javascript-devel mail

Re: [Pkg-javascript-devel] node-websocket_1.0.19-2~bpo8+1_amd64.changes REJECTED

On 29/09/15 20:13, Alexander Wirt wrote: > On Tue, 29 Sep 2015, Daniel Pocock wrote: > >> >> >> On 29/09/15 18:01, Alexander Wirt wrote: >>> >>> Package not in testing >>> >> >> >> The version in testing had to be updat

Re: [Pkg-javascript-devel] node-websocket_1.0.19-2~bpo8+1_amd64.changes REJECTED

On 29/09/15 18:01, Alexander Wirt wrote: > > Package not in testing > The version in testing had to be updated to 1.0.22 to work with node-nan 2.0.x. It is not clear if that dependency will be placed in debian-packports node-websocket versions <= 1.0.21 work with the node-nan version curren

Re: [Pkg-javascript-devel] jssip_0.6.34-5~bpo8+1_amd64.changes REJECTED

On 29/09/15 18:01, Alexander Wirt wrote: > > Package not in testing. These packages only had their VCS fields updated, otherwise they are the same as the packages in testing ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.deb

[Pkg-javascript-devel] Bug#799656: NaN 2.x issue

On 24/09/15 15:16, Jérémy Lal wrote: > > > 2015-09-24 14:59 GMT+02:00 Daniel Pocock <mailto:dan...@pocock.pro>>: > > > > On 24/09/15 14:53, Jérémy Lal wrote: > > 2015-09-24 14:42 GMT+02:00 Daniel Pocock <mailto:dan...@pocock.pro> >

[Pkg-javascript-devel] Bug#799656: NaN 2.x issue

On 24/09/15 14:58, Jérémy Lal wrote: > 2015-09-24 14:53 GMT+02:00 Jérémy Lal <mailto:kapo...@melix.org>>: > > 2015-09-24 14:42 GMT+02:00 Daniel Pocock <mailto:dan...@pocock.pro>>: > > > > This is failing because node-nan 2.x is now in

[Pkg-javascript-devel] Bug#799656: NaN 2.x issue

On 24/09/15 14:53, Jérémy Lal wrote: > 2015-09-24 14:42 GMT+02:00 Daniel Pocock <mailto:dan...@pocock.pro>>: > > > > This is failing because node-nan 2.x is now in unstable > > I've filed a bug upstream requesting support for node-nan 2.x &g

[Pkg-javascript-devel] Bug#799656: NaN 2.x issue

This is failing because node-nan 2.x is now in unstable I've filed a bug upstream requesting support for node-nan 2.x Maybe both old and new versions of node-nan will be needed in stretch? https://packages.qa.debian.org/n/node-nan.html ___ Pkg-javas

Re: [Pkg-javascript-devel] Small Node.js packages in NEW

On 16/08/15 12:58, Ross Gammon wrote: > On 07/23/2015 06:18 PM, Daniel Pocock wrote: >> c) would we consider a temporary nodejs-modules.deb omnibus package >> solution, with something like: >> >> Provides: node-foo, node-bar, ... >> Conflicts: node-foo, node

[Pkg-javascript-devel] libjs packages from Node packages?

In the Node policy[1], point 5, it says "*should* generate a *libjs-foo* binary package if the script is usable also for web-broser (see Javascript/Policy for more info) " Many Node packages specify something like a "browser" variation of their script

Re: [Pkg-javascript-devel] node-websocket_1.0.19-1_amd64.changes REJECTED

Hi Paul, I'm just following up on this, would you be able to approve it now that I updated the copyright file? Regards, Daniel On 30/07/15 12:07, Daniel Pocock wrote: > > > On 29/07/15 20:00, Paul Richards Tagliamonte wrote: >> >> Howdy maintainer, >> >

Re: [Pkg-javascript-devel] node-websocket_1.0.19-1_amd64.changes REJECTED

On 29/07/15 20:00, Paul Richards Tagliamonte wrote: > > Howdy maintainer, > > At least src/validation.cc is MIT/Expat licensed. Please include it in > your copyright file. > Thanks for the feedback, I've added that and uploaded again https://github.com/dpocock/WebSocket-Node/commit/b8dcd2380

Re: [Pkg-javascript-devel] Small Node.js packages in NEW

On 09/04/15 09:18, Dominique Dumont wrote: >> I don't have a better solution for small packages, but as long as there is >> no improvement in package handling, I think there should be no exception. >> I would still prefer the bundling of several small packages into bigger >> chunks. Isn't git

Re: [Pkg-javascript-devel] Comments regarding node-is-typedarray_1.0.0-1_amd64.changes

On 18/07/15 12:24, Thorsten Alteholz wrote: > Hi Daniel, > > this package seems to be another candidate for a small-package-reject. > Can't you merge this stuff into another package? > I was making a 1-to-1 mapping from NodeJS / NPM package names to Debian package names as described in the p

Re: [Pkg-javascript-devel] uploading new browserify-lite version

On 08/07/15 09:29, Jérémy Lal wrote: > 2015-07-07 23:20 GMT+02:00 Andrew Kelley >: > > Hi Jérémy, > > Daniel is interested in browserify-lite and I have completed and > packaged up some feature requests that he had. He has offered to > upload the ne

[Pkg-javascript-devel] browserify/browserify-lite automation

The most basic way of using browserify is not really consistent with the Debian approach. In most packages, we do everything to avoid having bundled libraries (e.g. in a C++ project) and aim to have each library in its own package so that any one library can be updated individually to fix a bug o

[Pkg-javascript-devel] packaging npm dependency graphs

There are more and more interesting projects using npm and related technologies like grunt and browserify browserify is a heavy user of npm dependencies itself[1] One idea that I had is that we could run some service (maybe using the URL http://npm.debian.net) to: a) automatically clone all th

Re: [Pkg-javascript-devel] About node browserify, massive npm dependency graphs

On 30/04/14 10:48, Leo Iannacone wrote: > Node browserify is a kind of software which makes node modules > compatible and runnable for browsers. > > It seems many modules use it, so it would be nice package it. > > I have taken a look, and it madly depends on dozens of packages/modules[0]. > >

[Pkg-javascript-devel] Bug#771299: support for JsSIP event name 'confirmed'

Package: jscommunicator-web-phone Version: 2.0.1-1 Severity: important The latest JsSIP releases now emit an event called 'confirmed' instead of 'started' For people to use newer JsSIP versions, JSCommunicator should recognise this event. For maximum flexibility, JSCommunicator needs to handle

[Pkg-javascript-devel] Fwd: Bug#769779: Acknowledgement (O: sipml5 -- JavaScript SIP stack)

: 769...@bugs.debian.org To: Daniel Pocock Thank you for filing a new Bug report with Debian. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they

[Pkg-javascript-devel] Bug#768639: jQuery UI not available

Package: drupal7-mod-drucall Version: 2.1-1 Severity: serious The new version of JSCommunicator requires some jQuery UI functionality Drupal7 provides jQuery UI in the page but doesn't expose the API automatically. Must use drupal_add_library to get it. Fixed upstream in 2.2. _

[Pkg-javascript-devel] Bug#768632: uses prop method, doesn't work with jQuery 1.4.4 in drupal7

Package: libjs-jscommunicator Version: 2.0.0-1 Severity: serious The version of drupal7 in Debian contains jQuery 1.4.4 JSCommunicator is using the prop method in jQuery, it only works with jQuery 1.6 or later To avoid breaking the DruCall method, we need to use the attr method instead. Already

[Pkg-javascript-devel] Bug#768630: not all Font Awesome files accessible under module URL

Package: drupal7-mod-fontawesome Version: 1.0-1 Severity: serious Only the css directory is symlinked into Drupal The other directories also need to be symlinked into Drupal ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian

[Pkg-javascript-devel] Bug#768502: function name mismatch

Package: drupal7-mod-jqueryi18nproperties Version: 1.0.0-1 Severity: serious Upstream bug: https://www.drupal.org/node/2371299 There is a mismatch in a PHP function name. This makes the function impossible to call. Upstream v1.1 fixes it. ___ Pkg-jav

[Pkg-javascript-devel] Bug#768363: adjust font-awesome dependency version

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/11/14 21:22, Jonas Smedegaard wrote: > Quoting Daniel Pocock (2014-11-06 20:43:48) >> The font-awesome package has a ~ symbol in the dfsg version. >> >> Therefore, depending on the constraint (>= 4.2.0) doesn'

[Pkg-javascript-devel] Bug#768363: adjust font-awesome dependency version

Package: libjs-jscommunicator Version: 2.0.0-1 Severity: serious The font-awesome package has a ~ symbol in the dfsg version. Therefore, depending on the constraint (>= 4.2.0) doesn't match the version 4.2.0~dfsg-1 Relax the dependency to depend on (>= 4.1.0~dfsg) __

[Pkg-javascript-devel] Bug#768354: must sync with JSCommunicator itself

Package: drupal7-mod-drucall Version: 2.0.1-1 Severity: serious A newer JSCommunicator version was uploaded but the DruCall module could not be uploaded earlier while waiting for the FTP masters to approve new Drupal dependency wrapper packages drupal7-mod-jqueryi18nproperties and drupal7-mod-font

[Pkg-javascript-devel] Bug#768351: must declare dependencies the Drupal way

Package: drupal7-mod-jscommunicator Version: 1.0.1-2 Severity: serious The .info file needs to include all dependencies for Drupal to ensure they are enabled correctly at runtime. ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.d

Re: [Pkg-javascript-devel] drupal7-mod-jqueryi18nproperties_1.0.0-1_amd64.changes REJECTED

On 10/10/14 16:15, Daniel Pocock wrote: > On 10/10/14 13:42, Luca Falavigna wrote: >> Hi Daniel, >> >> 2014-10-10 13:24 GMT+02:00 Daniel Pocock : >>> On 10/10/14 13:00, Luca Falavigna wrote: >>> jQuery-i18n-properties is not actually part of this package -

Re: [Pkg-javascript-devel] drupal7-mod-jqueryi18nproperties_1.0.0-1_amd64.changes REJECTED

On 10/10/14 13:42, Luca Falavigna wrote: > Hi Daniel, > > 2014-10-10 13:24 GMT+02:00 Daniel Pocock : >> On 10/10/14 13:00, Luca Falavigna wrote: >> jQuery-i18n-properties is not actually part of this package - it is just >> a dependency >> >> The package itse

Re: [Pkg-javascript-devel] drupal7-mod-jqueryi18nproperties_1.0.0-1_amd64.changes REJECTED

On 10/10/14 13:00, Luca Falavigna wrote: > Hi, > > in COPYING file, it's stated jQuery-i18n-properties is licensed under MIT > terms. > Please mention this in the copyright file. jQuery-i18n-properties is not actually part of this package - it is just a dependency The package itself is a wrappe

Re: [Pkg-javascript-devel] jquery-i18n-properties_1.0.9-1_amd64.changes REJECTED

On 03/08/14 19:00, Ansgar Burchardt wrote: > > Hi, > > the copyright and license information for css/blueprint/* is missing. > Did you look at the 1.1.0 upload? It was missing in 1.0.9 only. Maybe I forgot to upload 1.1.0-1, it was on my disk but I don't see an email acknowledgment for any

[Pkg-javascript-devel] JavaScript policy clarifications?

Looking at https://wiki.debian.org/Javascript/Policy there are some ambiguities in point 4 (*should* ship a /minified/ version for each script, generated at build time (use /uglifyjs/ to this purpose) ) - a package should /only/ ship a minified version of a script, or it should ship both mini

[Pkg-javascript-devel] Bug#736077: Bug#736077: dont leak private network information (at least not by default)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 19/01/14 15:22, Holger Levsen wrote: > package: libjs-jssip tags: security > > Hi Daniel, > > thanks for working on usuable + secure RTC in the webbrowser! > > During your presentation at the Paris mini-debconf I just learned > that your libj

[Pkg-javascript-devel] Bug#740489: include correct UA version string

package: libjs-jssip version: 0.4.0.20140212.1-1 The UA version string in the SIP headers is incorrect This is a bug in the way we use make instead of upstream's grunt build system to build the JavaScript. If grunt becomes part of Debian, then we will just use grunt and the problem will go away.

[Pkg-javascript-devel] Bug#716796: JSHint is optional

JSHint is optional, as noted earlier, it is just a tool to spot mistakes We can still build a valid jQuery package without running JSHint during the build Any calls to JSHint can be replaced with a call to /bin/true ___ Pkg-javascript-devel mailing l

Re: [Pkg-javascript-devel] [Pkg-monitoring-maintainers] Bug#736104: Sourceless file

Hi pkg-javascript, Can anybody comment on the jQuery version in sid? It is still 1.7 while more and more upstreams appear to be using newer versions I would obviously like to resolve the source issue below by linking to a packaged jQuery. If it won't happen soon please let me know so I can fi

Re: [Pkg-javascript-devel] Comments regarding drupal7-mod-jscommunicator_1.0.0-1_amd64.changes

On 14/01/14 12:23, Thorsten Alteholz wrote: > Hi Daniel, > > your debian/copyright says that this package is GPLv2, but > according to COPYING it should be GPLv2+. > Maybe you can correct this in one of the next uploads. Thanks for the feedback, I've fixed both in the repositories so it will defi

Re: [Pkg-javascript-devel] backport nodejs to wheezy

On 11/10/13 13:30, Jonas Smedegaard wrote: > Quoting Daniel Pocock (2013-10-11 13:09:38) >> On 11/10/13 11:22, Jonas Smedegaard wrote: >>> Quoting Daniel Pocock (2013-10-11 10:22:48) >>>> On 11/10/13 10:20, Jérémy Lal wrote: >>>>> On 11/10/2013 09:47, D

Re: [Pkg-javascript-devel] backport nodejs to wheezy

On 11/10/13 11:22, Jonas Smedegaard wrote: > Quoting Daniel Pocock (2013-10-11 10:22:48) >> On 11/10/13 10:20, Jérémy Lal wrote: >>> On 11/10/2013 09:47, Daniel Pocock wrote: >>>> I'm just wondering if anybody else thinks a wheezy-backports >>>> ve

Re: [Pkg-javascript-devel] backport nodejs to wheezy

On 11/10/13 10:20, Jérémy Lal wrote: > On 11/10/2013 09:47, Daniel Pocock wrote: >> On 11/05/13 17:46, Marcelo Jorge Vieira wrote: >>> Hi Jérémy, >>> >>> On Sun, 2013-05-05 at 23:35 +0200, Jérémy Lal wrote: >>>> On 05/05/2013 22:45, Marcelo Jorge Vi

Re: [Pkg-javascript-devel] backport nodejs to wheezy

On 11/05/13 17:46, Marcelo Jorge Vieira wrote: > Hi Jérémy, > > On Sun, 2013-05-05 at 23:35 +0200, Jérémy Lal wrote: >> On 05/05/2013 22:45, Marcelo Jorge Vieira wrote: >>> Hi Jérémy, >>> >>> What do you think about backport nodejs to wheezy? >> When the migration from nodejs 0.6 to nodejs 0.10 is

Re: [Pkg-javascript-devel] Comments regarding jssip_0.3.7-1_amd64.changes

On 06/09/13 09:32, Luca Falavigna wrote: > Hi, > > I'm wondering about the files under src/Grammar/dist/. > According to README.md, it seems they are generated using PEG.js. > > Can these files be generated at build time, and with what tool? PEGjs has been packaged too The package includes two bu

[Pkg-javascript-devel] packaging dependencies for Drupal modules

Drupal has a libraries module that helps co-ordinate the use of dependencies This seems to fit well with Debian's way of sharing library code, so I've started packaging it: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704196 One of the main intentions of this is to share JavaScript code, su

[Pkg-javascript-devel] packaging JsSIP - npm, grunt, etc

I've had a look at JsSIP: https://github.com/versatica/JsSIP In particular, it is built using a tool called grunt, and that requires nodejs and the npm tool It also pulls in some other dependencies: https://github.com/opentelecoms-org/JsSIP/blob/master/package.json#L23 "devDependencies": {

Re: [Pkg-javascript-devel] packaging WebRTC, and pkg-javascript git repos

On 23/02/13 23:32, Jonas Smedegaard wrote: >> Also, I notice that git SCM wasn't enabled in alioth, so I enabled it. >> Now it displays a link to >> >> http://alioth.debian.org/scm/browser.php?group_id=100128 >> >> and doesn't easily let people browse all the repos > > As I understand it, the Al

[Pkg-javascript-devel] packaging WebRTC, and pkg-javascript git repos

Hi, Thanks for adding me to the group I'm planning to upload packages of the two main WebRTC clients, SIPml5 and JsSIP I haven't done any JavaScript packaging before so any feedback is welcome I'm also working on the server-side infrastructure for WebRTC to come into Debian: http://www.resipr