Re: [Pkg-javascript-devel] sockjs-client is in Debian but needs update (Was: [covid-19] shiny-server (Was: dependencies Re: ITP: streamlit))

Hi Pirate, Am Mon, Feb 28, 2022 at 01:32:41PM +0530 schrieb Pirate Praveen: > > > >Yes. The ITP should have been closed manually long before. The fact > >that this not happened yet is IMHO a sign that the original maintainer > >does not care any more for the package (and forgot to orphan it). >

Re: [Pkg-javascript-devel] sockjs-client is in Debian but needs update (Was: [covid-19] shiny-server (Was: dependencies Re: ITP: streamlit))

Hi Andrius, Am Fri, Feb 25, 2022 at 03:27:43PM +0200 schrieb Andrius Merkys: > > Since there are no reverse dependencies on libjs-sockjs and we are not > in a hurry with shiny-server (we can still work on that with local > node-sockjs-client package), I would like to avoid experimental. This >

Re: [Pkg-javascript-devel] sockjs-client is in Debian but needs update (Was: [covid-19] shiny-server (Was: dependencies Re: ITP: streamlit))

Hi, Am Fri, Feb 25, 2022 at 03:09:36AM +0530 schrieb Nilesh Patra: > > >Sure. It would be nice to get ACK from Pirate, though, as he owns the ITP. > > I am a bit confused, why would you need ack from someone who ITP'ed it, even > if you need the ack, you'd ask this to the maintainer, right?

Re: [Pkg-javascript-devel] sockjs-client is in Debian but needs update (Was: [covid-19] shiny-server (Was: dependencies Re: ITP: streamlit))

Hi Andrius, Am Wed, Feb 23, 2022 at 06:10:24PM +0200 schrieb Andrius Merkys: > > https://github.com/sockjs/sockjs-client/commit/d9584abe2c7c913ce95a1aea29e5744dd85e1af4 > > > > I have turned this commit

[Pkg-javascript-devel] sockjs-client is in Debian but needs update (Was: [covid-19] shiny-server (Was: dependencies Re: ITP: streamlit))

Hi, I checked the hint "some work on sockjs-client done in salsa" which is not complete since there is "competing work" even inside Debian[1]. Since its Git repository points to alioth I simply took the freedom to merge the old packaging code into the work on Salsa[2] and shamelessly sticked to

Re: [Pkg-javascript-devel] sockjs-client is in Debian but needs update (Was: [covid-19] shiny-server (Was: dependencies Re: ITP: streamlit))

Hi Andrius, Am Tue, Feb 22, 2022 at 01:27:57PM +0200 schrieb Andrius Merkys: > On 2022-02-22 13:20, Andreas Tille wrote: > > Unfortunately we have a new problem as > > autopkgtest shows[4] > > > >sockjs-client : Depends: node-json3 (>= 3.3.2) but it is not ins

Re: [Pkg-javascript-devel] ITP: node-aws-sdk -- Its the official AWS SDK for JavaScript, available for browsers and mobile devices, or Node.js backends

Hi folks, sorry for the long receiver list of this mail. As it was discussed[1] on debian-ai list about tensorflow dependencies, the package node-aws-sdk seems to be needed. Since there was some work on this package in Git[2] I took the freedom to update the packaging to the latest upstream

[Pkg-javascript-devel] Please bump my permissions on salsa.d.o/js-team

Hi, please bump my permissions on salsa.d.o/js-team to enable me creating new repositories (= Maintainer). I want to add some preconditions to work on tensorflow. Thanks a lot Andreas. -- http://fam-tille.de -- Pkg-javascript-devel mailing list

Re: [Pkg-javascript-devel] [covid-19] Lots of JS dependencies [Was: Missing dependancies for streamlit]

Hi Andrius, On Wed, Apr 08, 2020 at 07:19:10AM +0300, mer...@debian.org wrote: > On 2020-04-07 22:49, Andreas Tille wrote: > > Aaaargh. Could we include Debian JS team into our sprint? I think we'd > > definitely need help here? Any volunteer to help us fighting Covid-19? &

[Pkg-javascript-devel] Bug#921363: Bug#921363: Package does not migrate to testing

On Wed, Feb 27, 2019 at 01:40:44PM +0100, Xavier wrote: > > I filled a BTS to ftp.debian.org to remove this source package: a > node-ejs package exists with a up-to-date GitHub repo (that's why > migration is blocked). There is no reverse dependency to ejs.js (the > only one requires node-ejs >=

[Pkg-javascript-devel] Bug#921363: Package does not migrate to testing

Hi Utkarsh, I realised that you intend to take over this package but for a reason I do not understand myself it does not migrate to testing (see testing excuses at the tracker page: https://tracker.debian.org/pkg/ejs.js ). I admit I have no idea why but if you really want to save this

Re: [Pkg-javascript-devel] V8 depends from outdated and unmaintained libv8 with security issues

On Fri, Feb 08, 2019 at 11:48:57AM +0100, Jérémy Lal wrote: > > That would be absolutely fantastic, yes. Also a symlink from > > libv8.so-> libnode.so woulde be handy, because libv8 doesn't use > > pkg-config anywhere else so most bindings just test for linking with > > -lv8. > > > > Ok then no

Re: [Pkg-javascript-devel] V8 depends from outdated and unmaintained libv8 with security issues

Hi Jeroen, On Fri, Feb 08, 2019 at 07:36:10AM +0100, Jeroen Ooms wrote: > For those following this discussion: there is now a version of > r-cran-v8 that uses libnode-dev in sid. Thanks a lot for your quick and extremely helpful support. > Is there anything we need to > do to get r-cran-v8 back

Re: [Pkg-javascript-devel] Status of libv8?

Hi Jonas, On Fri, Jan 18, 2019 at 08:04:33PM +0100, Jonas Smedegaard wrote: > Quoting Andreas Tille (2019-01-18 18:39:34) > > I'd prefer > > > > - change nodejs to build its v8 as a shared lib, and provide it it > >makes sense because upstream nodejs do

Re: [Pkg-javascript-devel] Status of libv8?

On Fri, Jan 18, 2019 at 01:46:13PM +0100, Jérémy Lal wrote: > Le ven. 18 janv. 2019 à 13:04, Andreas Tille a écrit : > > > > > > Possible solutions (besides not using it at all): > > > - bundle it - nodejs bundles it > > > - change nodejs to bu

[Pkg-javascript-devel] Bug#760385: Status of libv8?

Hi Jérémy, On Fri, Jan 18, 2019 at 11:51:38AM +0100, Jérémy Lal wrote: > > However, when reading > > > >https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773671#59 > > > > it might rather the best idea to remove this lib from Debian at all and > > I need to see how I can avoid depending from

[Pkg-javascript-devel] Bug#773623: Status of libv8?

Hi, I just realised that one of my packages does not migrate to testing due to its dependency from r-cran-v8 and in turn from libv8-devel. I realised that while libv8 has 3 security bugs which are set to stretch-ignore (#760385, #773623, #773671 - should this somehow also be set to

Re: [Pkg-javascript-devel] Help needed to package juniper

Hi Paolo, > to know how upstream builds it, look at package.json in scripts.build key > > It says: > NODE_ENV=production webpack --display-chunks && rm -rf dist/*.juniper.min.js" > > so you'll need webpack. > > You'd then proceed to webpack.config.js to see what plugins/tools it will pull >

[Pkg-javascript-devel] Help needed to package juniper

Hi, I injected a packaging skeleton for juniper[1] since I need it for some dependency. Unfortunately I have no idea how to trigger the build in d/rules. Any hint how to do this properly? Thanks a lot for your patience about my beginners question Andreas. [1]

[Pkg-javascript-devel] Bug#916221: node-prismjs: Unable to install due to missing node-clipboard

Package: node-prismjs Severity: grave Justification: renders package unusable Hi, $ sudo apt-get install node-prismjs Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an

[Pkg-javascript-devel] Bug#911660: libjs-twitter-bootstrap-datepicker: Please make package independent from twitter-bootstrap

Package: libjs-twitter-bootstrap-datepicker Severity: important Hi, this package is marked for autoremoval on 21 November due to twitter-bootstrap: #907724. As far as I understood the dependencies it would alternatively work with twitter-bootstrap3. So it seems the twitter-bootstrap dependency

[Pkg-javascript-devel] Bug#844075: Bug#844075: Bug#844075: leaflet: Please provide the latest Leaflet package including a node module

On Thu, Aug 23, 2018 at 02:27:06PM +0530, Pirate Praveen wrote: > >Thus I will not push my poor naive changes (which was basically > >importing the new version and removing the patch which was trying to > >fix > >a not existing Jakefile). I have no experience with JS and thus will > >not be of

[Pkg-javascript-devel] Bug#844075: Bug#844075: leaflet: Please provide the latest Leaflet package including a node module

Hi Jonas, On Thu, Aug 23, 2018 at 10:49:52AM +0200, Jonas Smedegaard wrote: > Quoting Andreas Tille (2018-08-23 09:45:17) > > Any news here? > > Leaflet 1.0.3 is in experimental since a while. That means > incomatibilities should be easier to test. > > Pending is f

[Pkg-javascript-devel] Bug#844075: Bug#844075: leaflet: Please provide the latest Leaflet package including a node module

On Sat, Nov 12, 2016 at 12:14:37PM +0100, Jonas Smedegaard wrote: > Quoting Jérémy Lal (2016-11-12 10:51:08) > > leaflet reverse dependencies need extra careful checks, because i > > believe there are been many changes between 1.0 and 0.7. > > Right. Luckily only few packages depend on leaflet,

Re: [Pkg-javascript-devel] Problems to recreate minimized JS in r-cran-jsonld

Hi, On Thu, May 10, 2018 at 01:31:56PM +0500, Pirate Praveen wrote: > > You'll need to update webpack.config.js with system path for it to find apt > installed modules. I naively tried diff --git a/webpack.config.js b/webpack.config.js index 7ce5c6e..87f7559 100644 --- a/webpack.config.js +++

Re: [Pkg-javascript-devel] Problems to recreate minimized JS in r-cran-jsonld

Hi David, On Thu, May 10, 2018 at 02:42:29PM -0400, David I. Lehn wrote: > On Wed, May 9, 2018 at 5:35 AM, Andreas Tille <andr...@fam-tille.de> wrote: > > I was stumbling upon an issue with some minimized JS in the package > > r-cran-jsonld (ITPed in #898224). I tried to r

[Pkg-javascript-devel] Problems to recreate minimized JS in r-cran-jsonld

Hi, I was stumbling upon an issue with some minimized JS in the package r-cran-jsonld (ITPed in #898224). I tried to recreate jsonld.min.js and have written a script[1] which calls webpack in a clone of the Github reporsitory. Unfortunately the webpack call ends in: webpack-merge@4.1.2

Re: [Pkg-javascript-devel] R: Re: Migrating *all* packages from alioth to salsa (Was: migrating my packages from alioth to salsa)

s ro your work in any case Andreas. > - Messaggio originale - > Da: "Andreas Tille" <andr...@an3as.eu> > Inviato: ‎24/‎04/‎2018 15:26 > A: "Paolo Greppi" <paolo.gre...@libpf.com> > Cc: "Debian Javascript Maintainers" > &l

Re: [Pkg-javascript-devel] Re: Migrating *all* packages from alioth to salsa (Was: migrating my packages from alioth to salsa)

Hi Paolo, On Mon, Apr 23, 2018 at 05:38:58PM +0200, Paolo Greppi wrote: > > I have completed the migration from alioth/pkg-javascript-devel to salsa of > the > 1082 packages which: > 0. have maintainer_email='pkg-javascript-devel at lists.alioth.debian.org'. > 1. are in sid/unstable > 2. have

Re: [Pkg-javascript-devel] Migrating *all* packages from alioth to salsa (Was: migrating my packages from alioth to salsa)

On Wed, Apr 18, 2018 at 09:25:19AM +0200, Paolo Greppi wrote: > if there is a consensus in the js-team I can perform the mass migration. As I said before I do absolutely not feel like having a vote in this decision but I'd consider it very sensible if you would go for it. Kind regards

Re: [Pkg-javascript-devel] migrating my packages from alioth to salsa

Hi, On Thu Apr 5 20:55:49 Paolo Greppi wrote: > I have looked up the current vcs_browser fields from udd (1356 packages) and > the repos the js-team already has on salsa (217 repos). > ... I wonder whether there is some common strategy to migrate all remaining packaged by Debian Javascript