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

[Andreas Tille]

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).
> > 
> 
> Gitlab has 1600+ node dependencies when I counted last time (may have even 
> grown bigger by now). So currently it is just a yarn install in contrib 
> section for most dependencies. With security updates coming every month 
> packaging node dependencies is happening very very slow. So if you see my 
> name anywhere in any node package, just go ahead and do the right thing, as 
> noted by Nilesh (just coordinate well in case of breaking changes). I'm not 
> particularly attached to any team maintained packages, I'm only happy if 
> others update packages where I'm an uploader.

I perfectly understand since we both obviously share the same attitude.  Thanks 
for clarifying explicitly anyway

   Andreas. 

-- 
http://fam-tille.de

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Andreas Tille]

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
> way I would not have to deal with Breaks+Replaces due to same locations
> occupied by two different packages.

Perfectly fine for me.

Thanks a lot for caring for this package

   Andreas. 

-- 
http://fam-tille.de

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Andreas Tille]

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?

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).
 
> But in any case, this does not seem to have any reverse dependencies so this 
> should be safe to upload. As far as I know Praveen, he will not stop you 
> until it breaks something (the package is in a bitrot anyway)

Yes.
 
> >FYI, the upload will have to go through NEW due to both source and binary
> >package renaming.
> 
> Although this does not make much sense to do this here but still if you want 
> to play extra safe, you might want to upload it targetting experimental.

You might even consider using the old name for an upload to unstable and
at the same time push a renamed package to experimental via new.  This
would enable to keep on working on shiny-server (despite I'm not sure
whether we need to be in a hurry here ... I personally have other things
on my table unfortunately).

Kind regards

  Andreas. 

-- 
http://fam-tille.de

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Andreas Tille]

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 into a patch, and now sockjs-client builds and
> passes its autopkgtest successfully. So we do not have to wait for the
> next release.

Would you mind uploading?

Kind regards
Andreas.

-- 
http://fam-tille.de

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Andreas Tille]

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 the old name without the leading "node-" (which is wrong
but I intended to avoid passing new queue for the moment).

I think we can close the open bug[3] with the new latest upstream
version which I've injected.  Unfortunately we have a new problem as
autopkgtest shows[4]

   sockjs-client : Depends: node-json3 (>= 3.3.2) but it is not installable

while we had this package before it was removed[5] from Debian.

I need to admit that I have no idea how to sensibly proceed from here
and would love if someone from Debian Javascript Maintainers would take
over from here.

Kind regards
 Andreas.

[1] https://tracker.debian.org/pkg/sockjs-client
[2] https://salsa.debian.org/js-team/node-sockjs-client
[3] https://bugs.debian.org/979958
[4] https://salsa.debian.org/js-team/node-sockjs-client/-/jobs/2499248
[5] https://bugs.debian.org/931653

Am Tue, Feb 22, 2022 at 08:23:23AM +0200 schrieb Andrius Merkys:
> Hi Eric,
> 
> On 2022-02-22 06:43, Eric Brown wrote:
> > It appears that significant progress has been made in packaging the
> > dependencies of shiny-server. I wonder if anyone is interested and
> > able to revisit packaging shiny-server?
> 
> In past I have worked to package the dependencies of shiny-server.
> Sadly, I do not have enough free cycles to work on shiny-server now. It
> would be great if someone experienced in JS (js-team?) could give it a look.
> 
> As for the remaining dependencies, sockjs, sockjs-client and rewire
> stands out. There is some work on sockjs-client done in salsa, seemingly
> never uploaded.
> 
> Best,
> Andrius
> 
> 

-- 
http://fam-tille.de

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Andreas Tille]

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 installable
> > 
> > while we had this package before it was removed[5] from Debian.
> > 
> > I need to admit that I have no idea how to sensibly proceed from here
> > and would love if someone from Debian Javascript Maintainers would take
> > over from here.
> 
> Citing [6]:
> 
>   JSON 3 is **deprecated** and **no longer maintained**. Please don't
>   use it in new projects, and migrate existing projects to use the
>   native `JSON.parse` and `JSON.stringify` instead.
> 
> My sense is that sockjs-client needs node-json3 usage replaced with
> calls to native JSON module (by upstream or by patch).

I'd fully agree here but I decided to let the needed action be taken
by someone who is comfortable with JS universe (which I'm not).

Kind regards

  Andreas.

> > [1] https://tracker.debian.org/pkg/sockjs-client
> > [2] https://salsa.debian.org/js-team/node-sockjs-client
> > [3] https://bugs.debian.org/979958
> > [4] https://salsa.debian.org/js-team/node-sockjs-client/-/jobs/2499248
> > [5] https://bugs.debian.org/931653
> 
> [6] https://www.npmjs.com/package/json3
> 
> Best,
> Andrius
> 

-- 
http://fam-tille.de

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Andreas Tille]

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 version and refresh the packaging to latest standards.
Thanks to Nilesh Patra the new dependency node-jmespath was packaged
and uploaded to new queue as well.

Nilesh also pointed out that the node-aws-sdk source also contains some
ruby code.  I personally can find it only below the dir doc-src but just
to be sure (and besides to ask for help and cooperation in general) I'd
like to raise the topic here.  I'm wondering whether there is some
connection to ruby-aws-sdk.

Any comments are welcome.

Kind regards

  Andreas.


[1] https://lists.debian.org/debian-ai/2021/04/msg0.html
[2] https://salsa.debian.org/js-team/node-aws-sdk

-- 
http://fam-tille.de

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Andreas Tille]

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
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Andreas Tille]

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?
> 
> I have some experience in packaging JS, and I would be willing to help.
> However, this is a lot of dependencies, and they will most likely depend
> on other unpackaged JS stuff. I am afraid this might be a can of worms.

My experience from other languages made me perfectly expect this.

> Nevertheless, I would give it a shot.

Thanks a lot for any help

 Andreas. 

-- 
http://fam-tille.de

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Andreas Tille]

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 >= 2.5.2 while ejs.js is 1.0.0 due to old
> GitHub repo, so points to src:node-ejs). libjs-ejs isn't used by any
> package.

Perfectly fine for me.

Kind regards

Andreas. 

-- 
http://fam-tille.de

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Andreas Tille]

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 package
for Buster some action seems to be needed.  Please do not ask me
personally about it since I do not have the slightest interest in this
package at all but simply realised that it has the autoremoval from
testing flag set despite your upload.

Thank you for your contribution

Andreas.

-- 
http://fam-tille.de

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Andreas Tille]

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 pkgconfig and a symlink instead.
> I suppose i need to ask a removal of libv8 from unstable (it's removed from
> testing) to
> be able to "take" libv8-dev. Or maybe declare a libv8-in-nodejs-dev package
> ?

Conflicts: libv8-dev (<= version)
Replaces: libv8-dev
Provides: libv8-dev

> In any case i don't know if i should make a libv8-xx package (which would
> basically be
> symlinks to libnode).
> Any advice is welcome...

That should be fine.

Kind regards

   Andreas.

-- 
http://fam-tille.de

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Andreas Tille]

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 in buster?

According to

https://tracker.debian.org/pkg/r-cran-v8

Topic "testing migrations" waiting for 1 day is all we need to
do. ;-)  Thanks to the autopkgtests we have only a 2 day waiting
period for the testing migration.

According to

https://tracker.debian.org/pkg/nodejs

libnode-js version 10.15.2 migratet to testing at 4.2.

Thanks again

   Andreas.

-- 
http://fam-tille.de

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Andreas Tille]

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 all the work of keeping ABI 
> >stability,
> 
> The libv8 part of Nodejs is currently included in Debian as a _private_ 
> shared library part of libnode.
> 
> I guess you can try link with that private library - as an alternative 
> to waiting for someone to refactor packages, have ftpmasters approve new 
> package names, and then have it available in experimental.

I admit I do not understand what exactly I need to do to use that
private shared library.  I checked the content of the packages
libnode-dev and libnode64 and did not found anything that looks
like libv8.  Could you give any more verbose hint how I can link
against the private shared library you mentioned?

Kind regards

 Andreas.

-- 
http://fam-tille.de

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Andreas Tille]

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 build its v8 as a shared lib, and provide it
> > > it makes sense because upstream nodejs do all the work of keeping ABI
> > > stability,
> > > backporting security fixes, choosing the right version, and so on.
> > > - take over maintenance and distribute it independently of nodejs
> >
> > This sounds like a pretty sensible solution.  I see you and Jonas are
> > also uploaders for nodejs.  It would be really great if you could do
> > this.
> >
> Which one ?

I'd prefer

 - change nodejs to build its v8 as a shared lib, and provide it


   it makes sense because upstream nodejs do all the work of keeping ABI

  
   stability,

I admit I do not fully understand what you mean by

 - bundle it - nodejs bundles it

(sounds similar to what you write above.

I think the "take over maintenance and distribute it" has no real future
considering that an RC bug in libv8 did not even received an answer.  I
guess the reason for this is that you have other things to play with. ;-)

> Also i won't upload new nodejs versions until it goes to testing, of course.

What about experimental for the moment?

Kind regards

  Andreas.


-- 
http://fam-tille.de

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Andreas Tille]

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 this package.
> 
> Indeed, i am sorry for this bad state of things; i thought i could handle
> it,
> but obviously i couldn't.
> 
> Possible solutions (besides not using it at all):
> - bundle it - nodejs bundles it
> - change nodejs to build its v8 as a shared lib, and provide it
> it makes sense because upstream nodejs do all the work of keeping ABI
> stability,
> backporting security fixes, choosing the right version, and so on.
> - take over maintenance and distribute it independently of nodejs

This sounds like a pretty sensible solution.  I see you and Jonas are
also uploaders for nodejs.  It would be really great if you could do
this.

Kind regards

   Andreas.

-- 
http://fam-tille.de

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Andreas Tille]

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 buster-ignore??? - I had no idea that we ignore CVEs at all but
anyway) it probably can not migrate to testing since it does not even
build:

   #853512 libv8-3.14: ftbfs with GCC-7

This bug is RC since 6 months but there is no response from any
uploader.  So I tried to clone the repository from Salsa and realised
that there is none at the place I would have expected
(https://salsa.debian.org/js-team/libv8).  Is there any other place
(besides digging into Alioth archives where I could find the
repository?)  I admit I'm not motivated to find out how to restore
old repositories but would rather use

   gbp import-dscs --ignore-repo-config --debsnap --pristine-tar libv8

instead.  Any information about the status of this package would be
really welcome.

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 this package.

Kind regards

   Andreas.

PS: Please CC me.  I'm not subscribed to this list.

-- 
http://fam-tille.de

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Andreas Tille]

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
> 
> See: https://wiki.debian.org/Javascript/Nodejs?highlight=%28webpack%29

Thanks for the helpful hint.  I made some progress but now I get:


ERROR in ./src/index.js
Module not found: Error: Can't resolve '@jupyterlab/outputarea' in 
'/home/andreas/debian-maintain/salsa/js-team/juniper/src'
 @ ./src/index.js 5:0-69

ERROR in ./src/index.js
Module not found: Error: Can't resolve '@jupyterlab/rendermime' in 
'/home/andreas/debian-maintain/salsa/js-team/juniper/src'
 @ ./src/index.js 6:0-87

ERROR in ./src/index.js
Module not found: Error: Can't resolve '@jupyterlab/services' in 
'/home/andreas/debian-maintain/salsa/js-team/juniper/src'
 @ ./src/index.js 4:0-64

ERROR in ./src/index.js
Module not found: Error: Can't resolve '@phosphor/widgets' in 
'/home/andreas/debian-maintain/salsa/js-team/juniper/src'
 @ ./src/index.js 3:0-43

ERROR in ./src/index.js
Module not found: Error: Can't resolve 'codemirror' in 
'/home/andreas/debian-maintain/salsa/js-team/juniper/src'
 @ ./src/index.js 1:0-36

ERROR in ./src/index.js
Module not found: Error: Can't resolve 'codemirror/mode/python/python' in 
'/home/andreas/debian-maintain/salsa/js-team/juniper/src'
 @ ./src/index.js 2:0-51


May be that's a matter of missing Build-Depends (I've added
node-babel-loader but with for instance libjs-codemirror is not
providing anything that would help here).

Any further hints?

Kind regards

   Andreas.

PS: I'm not subscribed to this list so CC would be welcome
but I can (obviously) read the web archive. ;-)

-- 
http://fam-tille.de

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Andreas Tille]

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] https://salsa.debian.org/js-team/juniper

-- 
http://fam-tille.de

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Andreas Tille]

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 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:
 node-prismjs : Depends: node-clipboard (>= 1.7.1) but it is not installable


There is no package node-clipboard available in Debian.

Kind regards

   Andreas.


-- System Information:
Debian Release: 9.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Andreas Tille]

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 could be easily removed.  It would
be nice if you could do this soon (I'd volunteer to prepare something
in Git for your review) since quite a chain of dependencies will
be in danger to get removed from testing.

Kind regards and thanks for maintaining libjs-twitter-bootstrap-datepicker
   Andreas.

-- System Information:
Debian Release: 9.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libjs-twitter-bootstrap-datepicker depends on:
ii  dpkg 1.18.25
pn  libjs-twitter-bootstrap  

Versions of packages libjs-twitter-bootstrap-datepicker recommends:
ii  javascript-common  11

libjs-twitter-bootstrap-datepicker suggests no packages.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Andreas Tille]

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 any help at all.
> 
> They moved their build system to rollup (it is already packaged). The new 
> build command is,
> 
> rollup -c build/rollup-config.js
> 
> From, package.json  -> scripts -> build

Sounds like a promising hint for the Uploaders of this package.
 
> I can help if you want to learn JS packaging. My plate is full with gitlab 
> node dependencies, so can't take more.

Pirate, I've learned about you at DebConf and that your are competing
quite a lot with myself in the number of uploaded packages. ;-) I'm also
watching new queue with lots of packages of yours.  But my situation is
similar:  I need to restrict my involvement and learning JS will drain
time and energy from all the other stuff I'm doing.  So thanks for the
kind offer to teach JS packaging - I'd prefer if you find one or more
other people doing this (and I have also heard that your are teaching a
lot).

Kind regards

  Andreas.

-- 
http://fam-tille.de

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Andreas Tille]

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 for someone to test which reverse dependencies break with the 
> newer Leaflet.

My poor (rather non-existing) JS knowledge might explain my possibly
naive question: Does it make sense to spent time to test a version which
is obviously outdated at the time of testing?  I'd consider it a
sensible strategy to upload 1.3.x to experimental and do the testing on
this version since the motivation of testers might be higher.
 
> Bonus points for providing patches to automate such testing ;-)
 
Sorry, I do not even know how to test manually and I have zero resources
to dive into this.
 
> > I need to package r-cran-leaflet which has a code copy of leaflet 
> > 1.3.1.  I guess the recent upstream version 1.3.4 will be fine as 
> > well.
> 
> This bug#844075 is about updating to release 1.0.1 (impractical to 
> eternally be about "latest").  I have adjusted the title accordingly.

Remembering my naivity - but I'd consider this a diversion from the bug
reporters intention (Ross in CC).  If the report said "latest" than
changing the bug title to "current at time of bug report" might or might
not intended by the reporter.  So I'd rather ask back what's really
needed.
 
> Please file a separate bug if r-cran-leaflet cannot be patched to use 
> Leaflet 1.0.3 now in experimental (and please have that new bugreport 
> track a specific lowest-possible version to not repeat this confusion).

I admit I will not dive into patching some code to support older
versions of some code copies before I do not see any other chance.  I
for myself consider living with a code copy until the Debian package
catches up the more promising strategy here.

Kind regards

   Andreas.

-- 
http://fam-tille.de

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Andreas Tille]

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, but indeed they 
> need to be checked thoroughly for incompatibilities.

Any news here?  I need to package r-cran-leaflet which has a code copy
of leaflet 1.3.1.  I guess the recent upstream version 1.3.4 will be
fine as well. 

I gave the packaging a naive try imported the new version into leaflet
Git[1] but ended up with:

 debian/rules build
test -x debian/rules
mkdir -p "."
jake build
jake aborted.
Error: No Jakefile. Specify a valid path with -f/--jakefile, or place one in 
the current directory.
at api.fail (/usr/lib/nodejs/jake/api.js:326:18)
at EventEmitter.utils.mixin.run (/usr/lib/nodejs/jake/jake.js:317:9)
(See full trace by running task with --trace)
make: *** [debian/rules:32: build/libjs-leaflet] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
I: copying local configuration
E: Failed autobuilding of package


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 any help at all.

Kind regards

   Andreas.


[1] https://salsa.debian.org/js-team/leaflet

-- 
http://fam-tille.de

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Andreas Tille]

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
+++ b/webpack.config.js
@@ -20,11 +20,11 @@ const outputs = [
 entry: [
   // 'babel-polyfill' is very large, list features explicitly
   'regenerator-runtime/runtime',
-  'core-js/fn/array/includes',
-  'core-js/fn/object/assign',
-  'core-js/fn/promise',
-  'core-js/fn/string/starts-with',
-  'core-js/fn/symbol',
+  '/usr/lib/nodejs/core-js/fn/array/includes',
+  '/usr/lib/nodejs/core-js/fn/object/assign',
+  '/usr/lib/nodejs/core-js/fn/promise',
+  '/usr/lib/nodejs/core-js/fn/string/starts-with',
+  '/usr/lib/nodejs/core-js/fn/symbol',
   // main lib
   './lib/index.js'
 ],

which did not help.
 
> > jsonld.js does not work.  The file size of this uncompressed file is way
> > smaller than the minimazion result and doese not work together with the
> > R code.  Thus I really need to undergo the process to create the
> > minimized JS.
> 
> https://wiki.debian.org/Javascript/#Using_build_tools_like_grunt has
> examples.

Is there any actual package example?  The anchor does not exist (any
more) on that wiki page (which should be updated to Salsa anyway ;-) ).

Kind regards

 Andreas.

-- 
http://fam-tille.de

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Andreas Tille]

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 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 node_modules/webpack-merge
> > └── lodash@4.17.10
> > ...
> > ERROR in multi regenerator-runtime/runtime core-js/fn/array/includes 
> > core-js/fn/object/assign core-js/fn/promise core-js/fn/string/starts-with 
> > core-js/fn/symbol ./lib/index.js
> > Module not found: Error: Can't resolve 'babel-loader' in 
> > '/home/andreas/debian-maintain/salsa/r-pkg-team/0_prospective/r-cran-jsonld/debian/JS/jsonld.js'
> >  @ multi regenerator-runtime/runtime core-js/fn/array/includes 
> > core-js/fn/object/assign core-js/fn/promise core-js/fn/string/starts-with 
> > core-js/fn/symbol ./lib/index.js
> > ...
> > Any idea how to get the minimized JS?  Simply taking the non-minimized
> > jsonld.js does not work.  The file size of this uncompressed file is way
> > smaller than the minimazion result and doese not work together with the
> > R code.  Thus I really need to undergo the process to create the
> > minimized JS.
> >
> > Any idea how to approach this?
> > ...
> > [1] 
> > https://salsa.debian.org/r-pkg-team/r-cran-jsonld/blob/master/debian/JS/get-jsonld.min
> >
> 
> Hi, I'm an upstream developer for jsonld.js and the one to blame for
> the webpack config. ;-)

Thanks a lot for stepping in here.

> I'm getting 404 on that salsa repo so I'm not
> sure what your script is doing.

I re-checked the link and I guess it was just a temporary error.

> In npm world you can build
> jsonld.min.js with "npm install && npm run build-webpack".  That's how
> it's published to npm.

This works for me now.

> I've never tried building with apt installed
> modules.  If upstream changes would help make this all easier, let me
> know.

While your hint was sufficient for me to get the compressed JS out of
the JS sources you might like to have a look at

   
https://salsa.debian.org/r-pkg-team/r-cran-jsonld/tree/a5535fdc49edb0584c774f224c1bc23ff76810f0/debian/JS

There is the error

   
https://salsa.debian.org/r-pkg-team/r-cran-jsonld/blob/a5535fdc49edb0584c774f224c1bc23ff76810f0/debian/JS/get-jsonld.min.err

if I try to build via

   webpack --config ../webpack.config.js lib/jsonld.js dist/jsonld.js 
--output-library=jsonld

No idea whether there is some hidden bug in the JS code.

Kind regards

Andreas.

-- 
http://fam-tille.de

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Andreas Tille]

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 node_modules/webpack-merge
└── lodash@4.17.10
Hash: eaf5c95c94821ab4944c9f696b4a89040915c26b
Version: webpack 3.5.6
Child
Hash: eaf5c95c94821ab4944c
Time: 140ms
Asset Size  Chunks Chunk Names
jsonld.js  3.61 kB   0  [emitted]  jsonld
   [0] multi regenerator-runtime/runtime core-js/fn/array/includes 
core-js/fn/object/assign core-js/fn/promise core-js/fn/string/starts-with 
core-js/fn/symbol ./lib/index.js 100 bytes {0} [built]

ERROR in multi regenerator-runtime/runtime core-js/fn/array/includes 
core-js/fn/object/assign core-js/fn/promise core-js/fn/string/starts-with 
core-js/fn/symbol ./lib/index.js
Module not found: Error: Can't resolve 'babel-loader' in 
'/home/andreas/debian-maintain/salsa/r-pkg-team/0_prospective/r-cran-jsonld/debian/JS/jsonld.js'
 @ multi regenerator-runtime/runtime core-js/fn/array/includes 
core-js/fn/object/assign core-js/fn/promise core-js/fn/string/starts-with 
core-js/fn/symbol ./lib/index.js

ERROR in multi regenerator-runtime/runtime core-js/fn/array/includes 
core-js/fn/object/assign core-js/fn/promise core-js/fn/string/starts-with 
core-js/fn/symbol ./lib/index.js
Module not found: Error: Can't resolve 'core-js/fn/array/includes' in 
'/home/andreas/debian-maintain/salsa/r-pkg-team/0_prospective/r-cran-jsonld/debian/JS/jsonld.js'
 @ multi regenerator-runtime/runtime core-js/fn/array/includes 
core-js/fn/object/assign core-js/fn/promise core-js/fn/string/starts-with 
core-js/fn/symbol ./lib/index.js

ERROR in multi regenerator-runtime/runtime core-js/fn/array/includes 
core-js/fn/object/assign core-js/fn/promise core-js/fn/string/starts-with 
core-js/fn/symbol ./lib/index.js
Module not found: Error: Can't resolve 'core-js/fn/object/assign' in 
'/home/andreas/debian-maintain/salsa/r-pkg-team/0_prospective/r-cran-jsonld/debian/JS/jsonld.js'
 @ multi regenerator-runtime/runtime core-js/fn/array/includes 
core-js/fn/object/assign core-js/fn/promise core-js/fn/string/starts-with 
core-js/fn/symbol ./lib/index.js

ERROR in multi regenerator-runtime/runtime core-js/fn/array/includes 
core-js/fn/object/assign core-js/fn/promise core-js/fn/string/starts-with 
core-js/fn/symbol ./lib/index.js
Module not found: Error: Can't resolve 'core-js/fn/promise' in 
'/home/andreas/debian-maintain/salsa/r-pkg-team/0_prospective/r-cran-jsonld/debian/JS/jsonld.js'
 @ multi regenerator-runtime/runtime core-js/fn/array/includes 
core-js/fn/object/assign core-js/fn/promise core-js/fn/string/starts-with 
core-js/fn/symbol ./lib/index.js

ERROR in multi regenerator-runtime/runtime core-js/fn/array/includes 
core-js/fn/object/assign core-js/fn/promise core-js/fn/string/starts-with 
core-js/fn/symbol ./lib/index.js
Module not found: Error: Can't resolve 'core-js/fn/string/starts-with' in 
'/home/andreas/debian-maintain/salsa/r-pkg-team/0_prospective/r-cran-jsonld/debian/JS/jsonld.js'
 @ multi regenerator-runtime/runtime core-js/fn/array/includes 
core-js/fn/object/assign core-js/fn/promise core-js/fn/string/starts-with 
core-js/fn/symbol ./lib/index.js

ERROR in multi regenerator-runtime/runtime core-js/fn/array/includes 
core-js/fn/object/assign core-js/fn/promise core-js/fn/string/starts-with 
core-js/fn/symbol ./lib/index.js
Module not found: Error: Can't resolve 'core-js/fn/symbol' in 
'/home/andreas/debian-maintain/salsa/r-pkg-team/0_prospective/r-cran-jsonld/debian/JS/jsonld.js'
 @ multi regenerator-runtime/runtime core-js/fn/array/includes 
core-js/fn/object/assign core-js/fn/promise core-js/fn/string/starts-with 
core-js/fn/symbol ./lib/index.js

ERROR in multi regenerator-runtime/runtime core-js/fn/array/includes 
core-js/fn/object/assign core-js/fn/promise core-js/fn/string/starts-with 
core-js/fn/symbol ./lib/index.js
Module not found: Error: Can't resolve 'regenerator-runtime/runtime' in 
'/home/andreas/debian-maintain/salsa/r-pkg-team/0_prospective/r-cran-jsonld/debian/JS/jsonld.js'
 @ multi regenerator-runtime/runtime core-js/fn/array/includes 
core-js/fn/object/assign core-js/fn/promise core-js/fn/string/starts-with 
core-js/fn/symbol ./lib/index.js
Child
Hash: 9f696b4a89040915c26b
Time: 126ms
Asset Size  Chunks Chunk Names
jsonld.min.js  1.24 kB   0  [emitted]  jsonld
   [0] multi regenerator-runtime/runtime core-js/fn/array/includes 
core-js/fn/object/assign core-js/fn/promise core-js/fn/string/starts-with 
core-js/fn/symbol ./lib/index.js 100 bytes {0} [built]

ERROR in multi regenerator-runtime/runtime core-js/fn/array/includes 
core-js/fn/object/assign core-js/fn/promise 

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

[Andreas Tille]

Hi Paolo,

On Tue, Apr 24, 2018 at 04:17:35PM +0200, Paolo Greppi wrote:
> That one is not in stretch but not in sid so it fails criterion 1.

Criterion 1 is "are in sid/unstable" and I get

$ apt-cache policy libjs-handlebars
libjs-handlebars:
  Installiert:   (keine)
  Installationskandidat: 3:4.0.10-5
  Versionstabelle:
 3:4.0.10-5 501
501 http://httpredir.debian.org/debian testing/main amd64 Packages
501 http://httpredir.debian.org/debian testing/main i386 Packages
 50 http://httpredir.debian.org/debian unstable/main amd64 Packages
 50 http://httpredir.debian.org/debian unstable/main i386 Packages

Am I missing something?  I admit I also consider the criterion "belongs
to release xy" as some artificial criterion.  Even packages outside sid
have either some history (before removed from sid), might be in
experimental - so interesting) or are in preparation (in new or even
before uploaded to new).  I fail to see any reason why those should not
be restricted to salsa.

> We may decide to perform a separate automated migration for those

I'd strongly recommend this to save developer work.

Kind regards and thanks 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" 
> <pkg-javascript-de...@lists.alioth.debian.org>
> Oggetto: 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 pkg_javascript in vcs_browser field
> > 3. had no repo on salsa.
> 
> I've just checked a totally random clone that was by chance on my
> harddisk.  Package libjs-handlebars seems to fit the criteria above but
> I can not find it on salsa.  Am I missing something?
> 
> Kind regards
> 
> Andreas.
> 
> -- 
> http://fam-tille.de

-- 
http://fam-tille.de

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Andreas Tille]

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 pkg_javascript in vcs_browser field
> 3. had no repo on salsa.

I've just checked a totally random clone that was by chance on my
harddisk.  Package libjs-handlebars seems to fit the criteria above but
I can not find it on salsa.  Am I missing something?

Kind regards

Andreas.

-- 
http://fam-tille.de

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Andreas Tille]

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

  Andreas.

-- 
http://fam-tille.de

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Andreas Tille]

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 Maintainers.  I would really love if
somebody would adapt one of the several scripts developed by other teams
and do some mass migration.  I just have manually migrated the only
package I maintain in the team (datatables-extensions) but I once did
some backporting of packages and thus have some interest in some other
packages of the team.  Should I just sit and wait trusting that
something will happen with those packages I'm interested in in the next
two weeks as long as Alioth is online?

Kind regards

  Andreas.

-- 
http://fam-tille.de

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel