[Pkg-javascript-devel] Bug#1057028: node-stable: please remove me from uploaders

[Andrius Merkys]

Source: node-stable
Severity: wishlist

Hello,

Back in a day I packaged/sponsored a bunch of node packages needed by 
node-shiny-server. I ended up never using shiny-server and/or 
node-shiny-server, but with the responsibility for its dependencies. 
Thus I would like to be removed from the uploaders of this package.


Best,
Andrius


OpenPGP_signature.asc
Description: OpenPGP digital signature
-- 
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#1057027: node-pause: please remove me from uploaders

[Andrius Merkys]

Source: node-pause
Severity: wishlist

Hello,

Back in a day I packaged/sponsored a bunch of node packages needed by 
node-shiny-server. I ended up never using shiny-server and/or 
node-shiny-server, but with the responsibility for its dependencies. 
Thus I would like to be removed from the uploaders of this package.


Best,
Andrius


OpenPGP_signature.asc
Description: OpenPGP digital signature
-- 
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#1057026: node-morgan: please remove me from uploaders

[Andrius Merkys]

Source: node-morgan
Severity: wishlist

Hello,

Back in a day I packaged/sponsored a bunch of node packages needed by 
node-shiny-server. I ended up never using shiny-server and/or 
node-shiny-server, but with the responsibility for its dependencies. 
Thus I would like to be removed from the uploaders of this package.


Best,
Andrius


OpenPGP_signature.asc
Description: OpenPGP digital signature
-- 
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#1057024: node-client-sessions: please remove me from uploaders

[Andrius Merkys]

Source: node-client-sessions
Severity: wishlist

Hello,

Back in a day I packaged/sponsored a bunch of node packages needed by 
node-shiny-server. I ended up never using shiny-server and/or 
node-shiny-server, but with the responsibility for its dependencies. 
Thus I would like to be removed from the uploaders of this package.


Best,
Andrius


OpenPGP_signature.asc
Description: OpenPGP digital signature
-- 
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#1057025: node-ip-address: please remove me from uploaders

[Andrius Merkys]

Source: node-ip-address
Severity: wishlist

Hello,

Back in a day I packaged/sponsored a bunch of node packages needed by 
node-shiny-server. I ended up never using shiny-server and/or 
node-shiny-server, but with the responsibility for its dependencies. 
Thus I would like to be removed from the uploaders of this package.


Best,
Andrius


OpenPGP_signature.asc
Description: OpenPGP digital signature
-- 
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#1017811: node-wikibase-cli: FTBFS without Internet access

[Andrius Merkys]

Hello,

I have commented out a pair of test cases which attempted network access 
in the upload of node-wikibase-cli 15.15.4-5. Could you please check 
whether FTBFS continues?


On Wed, 14 Dec 2022 12:16:39 +0100 Sven Mueller  wrote:

Interestingly, in our build environment which has some extremely limited
network access, the package build fails before tests are even run:

Linking /usr/bin/wb-set-label to
/usr/share/nodejs/wikibase-cli/bin/wb-set-label
Linking /usr/bin/wb-sparql to /usr/share/nodejs/wikibase-cli/bin/wb-sparql
Linking /usr/bin/wb-summary to /usr/share/nodejs/wikibase-cli/bin/wb-summary
Linking /usr/bin/wb-update-claim to
/usr/share/nodejs/wikibase-cli/bin/wb-update-claim
Linking /usr/bin/wb-update-qualifier to
/usr/share/nodejs/wikibase-cli/bin/wb-update-qualifier
Linking /usr/bin/wd to /usr/share/nodejs/wikibase-cli/bin/wd
   dh_installdocs -i
   dh_installchangelogs -i
   dh_installexamples -i
   debian/rules override_dh_installman
make[1]: Entering directory '/<>'
help2man wb --name 'command-line interface to Wikibase' --no-info >
debian/wb.1
help2man: can't get `--help' info from wb
Try `--no-discard-stderr' if option outputs to stderr
make[1]: *** [debian/rules:10: override_dh_installman] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: binary-indep] Error 2
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned
exit status 2


I do not quite get this, AFAIK tests are run before dh_installman. Thus 
in your case tests pass, but override_dh_installman fails, right?


Thanks,
Andrius

--
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#1054432: Bug#1054432: node-puppeteer: website is build with Docusaurus not packaged for debian

[Andrius Merkys]

Hi,

On 2023-10-23 22:04, Bastien Roucariès wrote:

Source:  node-katex


Source package names in Subject and Source do not match. Please retitle 
if this is not intentional.


Best,
Andrius

--
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] Passing on maintenance of node-shiny-server dependencies

[Andrius Merkys]

Hi all,

Back in a day I packaged/sponsored a bunch of node packages needed by 
node-shiny-server. I ended up never using shiny-server and/or 
node-shiny-server, but with the responsibility for its dependencies. I 
would be happy if someone from Med or JS teams could step up and replace 
me as the uploader for these packages:


node-client-sessions
node-ip-address
node-morgan
node-pause
node-stable

The packages are in a good shape, most of them have no open bugs and are 
up-to-date with their upstreams. I will wait for responses for a couple 
of weeks before orphaning them.


Best wishes,
Andrius

--
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#1043352: node-eventemitter3: drop debian/todo as tests are run

[Andrius Merkys]

Source: node-eventemitter3
Severity: wishlist
Version: 4.0.7-3

Hello,

node-eventemitter3 contains a debian/todo file with the following content:

  Tests depend on node-assume, which is not yet packaged (#962635):

  mocha spec --timeout 1 test/test.js

node-assume is now packaged and it seems that mocha tests are now used 
both the build and autopkgtest stage. Thus debian/todo is outdated and 
should be removed.


Andrius

--
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#1035716: node-agent-base: upstream has moved development to other repository

[Andrius Merkys]

Source: node-agent-base
Severity: normal

Hello,

The upstream of node-agent-base has merged several repositories into 
one, thus debian/watch should be updated to see more recent versions of 
this package. Upstream message could be found here [1].


[1] 
https://github.com/TooTallNate/node-agent-base/issues/53#issuecomment-1535566963


Andrius

--
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#1033350: Bug#1033350: node-should: please provide type declarations

[Andrius Merkys]

Hi,

On 2023-03-23 17:05, Yadd wrote:
should.js already provides its typescript definitions, @types/should is 
an empty package. Maybe the issue is just to rename "typings" field into 
"types"


Thanks for the prompt fix. It may have been my mistake to forget to 
include 'should' into debian/nodejs/extlinks. Anyway, build passes this 
step now when having node-should 13.2.3~dfsg-7 installed.


Best wishes,
Andrius

--
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#1033350: node-should: please provide type declarations

[Andrius Merkys]

Package: node-should
Version: 13.2.3~dfsg-6
Severity: wishlist

Hello,

I am working to update node-wikibase-sdk to 9.0.5 (newest release ATM). 
The new release has tests depending on @types/should which does not seem 
to be packaged.


Andrius

--
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#1017607: node-wikibase-edit: Test fails with node-fetch >= 3

[Andrius Merkys]

Hello,

On Thu, 18 Aug 2022 12:12:09 +0200 Yadd  wrote:

node-fetch 3 is ready in experimental. It is an hybrid package:
 * ES part is node-fetch-3
 * CJS part reproduces node-fetch-2 behavior

This changes are OK for all packages except node-wikibase-cli and
node-wikibase-edit. Sadly I didn't succeed to find why test fail with
it.


For node-wikibase-edit the problem might be caused because I used 
node-fetch as a drop-in replacement for node-cross-fetch which is not 
packaged yet. Most likely a divergence between APIs of these two 
happened, causing node-wikibase-edit to fail.


A bit different situation happens with node-wikibase-cli (no 
node-cross-fetch). But it may happen that node-wikibase-cli fails as it 
depends on node-wikibase-edit.


Andrius

--
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#1017811: node-wikibase-cli: FTBFS without Internet access

[Andrius Merkys]

control: tags -1 + moreinfo

Hi Steve,

On Sat, 20 Aug 2022 15:05:03 -0700 Steve Langasek
 wrote:
> In Ubuntu, node-wikibase-cli fails to build from source because dh_auto_test
> runs a test suite at build time which requires Internet access, and the
> Ubuntu build environment does not allow access to the Internet.
> 
> Debian packages should not fail to build when they are built offline.

Thanks for reporting this bug. I wonder why Debian buildds do not fail,
but AFAIR there are no guarantees they are off network during package
builds.

> The attached patch fixes the package to run the testsuite but ignore any
> failures.  I've uploaded this patch to Ubuntu to fix the failure there.

While this overcomes the FTBFS, this is not the way I would want the
package to be. It would be much better to find a way to skip tests
requiring network access and keep the remaining ones to catch possible
regressions.

Thanks,
Andrius

-- 
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#1013566: Bug#1013566: node-sockjs: FTBFS: sockjs.coffee:137:9: error: Can't reference 'this' before calling super in derived class constructors

[Andrius Merkys]

Hi Yadd,

On 2022-06-24 17:10, Yadd wrote:
> I prepared a fix, pushed to salsa. Could you take a look ?

Thanks a lot, reviewed and uploaded.

Best wishes,
Andrius

-- 
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#1007915: Bug#1007915: node-wikibase-cli: incompatible with node-commander >= 8

[Andrius Merkys]

On 2022-03-30 07:50, Yadd wrote:
> /usr/bin/* links were wrong. I fixed all these issues

Thanks a lot!

Best,
Andrius

-- 
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#1007915: Bug#1007915: node-wikibase-cli: incompatible with node-commander >= 8

[Andrius Merkys]

Hi Yadd,

On 2022-03-29 19:17, Yadd wrote:
> On 29/03/2022 17:44, Yadd wrote:
>> Hi Andrius,
>>
>> you fix is enough for commander 8, I'm currently writing commander 9
>> patch
> 
> Fixed and pushed. However package looks unusable because all bin/*
> commands are not in $PATH. You could either:
>  * install all commands in /usr/bin
>  * or change path in /usr/bin/wd and /usr/bin/wb

Thanks a lot for taking care of this! I will check why the executables
do not end in /usr/bin/. Once I am done, I will upload.

Thanks once more,
Andrius

-- 
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#1008200: node-send: patched node-mime-types cause problems for other reverse-dependencies

[Andrius Merkys]

Hello,

On 2022-03-24 11:39, Nilesh Patra wrote:
> node-send is patched[1] to use node-mime-types instead of node-mime.

The patch should be dropped altogether, since node-ms is now a package
on its own.

> [1]: 
> https://salsa.debian.org/js-team/node-send/-/blob/master/debian/patches/0001-use_ms_from_debug.patch#L15

Andrius

-- 
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#1007915: Bug#1007915: node-wikibase-cli: incompatible with node-commander >= 8

[Andrius Merkys]

Hi,

On 2022-03-18 16:13, Yadd wrote:
> Maybe this can help:
> https://salsa.debian.org/js-team/node-terser/-/blob/debian/latest/debian/patches/1001_commander.patch

Thanks for pointer. I think I managed to go this far myself by patching:

-const program = require('commander')
+const program = require('commander').storeOptionsAsProperties(true)

However, commander seems to handle positional CLI arguments differently
now, and no longer outputs help if any of them are missing.

Best,
Andrius

-- 
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#1007915: node-wikibase-cli: incompatible with node-commander >= 8

[Andrius Merkys]

Source: node-wikibase-cli
Version: 15.15.4
Severity: serious
Tags: help

While node-wikibase-cli was in NEW, node-commander was updated from
6.2.1 to 9.0.0. node-wikibase-cli is compatible with node-commander 6.x
only and simple patching does not seem to help. I will try patching it a
bit more, but I would appreciate any help from someone more accustomed
to node-commander API.

Andrius

-- 
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#1006469: Bug#1006469: Bug#1006469: node-puppeteer shouldn't embed devtools-protocol

[Andrius Merkys]

On 2022-02-28 08:58, Andrius Merkys wrote:
> If I get a second opinion that
> node-devtools-protocol is not worthy as a package on its own, I will RM it.

Here I meant second opinion besides mine. So if anyone would say
node-devtools-protocol is not worth staying in Debian on its own, I will
RM it.

Best,
Andrius

-- 
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))

[Andrius Merkys]

Hi Eric,

On 2022-02-27 22:36, Eric Brown wrote:
> Likewise, thank you very much! It’s exciting that the dependencies for
> shiny-server are coming together. Please note the upstream for
> sockjs-client responded to me and released 1.6.0 which also updates some
> other dependency versions.

You are welcome. I have uploaded node-sockjs-client on Friday, it is in
NEW now. I will update it to 1.6.0 once it clears NEW.

It would be nice if someone could take a look at shiny-server, since it
starts to come together finally. I most likely will not have time for
that. I would suggest against updating it at first, as new JS
dependencies have a tendency to appear rapidly.

Best,
Andrius

-- 
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#1006469: Bug#1006469: node-puppeteer shouldn't embed devtools-protocol

[Andrius Merkys]

Hello,

On 2022-02-28 06:09, Martina Ferrari wrote:
>> node-puppeteer embeds a copy of devtools-protocol while Debian has
>> node-devtools-protocol. Please drop this and use node-devtools-protocol
>> dependency
> 
> This was done on purpose, as it is not really workable to keep them
> separate due to how tightly coupled the code is to the version of the
> protocol. Keeping them separate will mean endless trouble, forcing both
> packages to always be updated in step, and if anybody ever updates the
> devtools package separately it most surely will break puppeteer.

I packaged node-devtools-protocol with the hope to un-embed it from
node-puppeteer, but I am mostly convinced it is node-devtools-protocol
that should be removed. If I get a second opinion that
node-devtools-protocol is not worthy as a package on its own, I will RM it.

Best,
Andrius

-- 
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))

[Andrius Merkys]

Hello,

Replying to Nilesh and Andreas in the same mail.

On 2022-02-25 07:49, Andreas Tille wrote:
> 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).

I admit I got confused a bit. There is an orphaning bug [1] without an
owner and ITP bug [2] owned by Pirate Praveen. I think I will merge
these and close them with the upload.

[1] https://bugs.debian.org/836492
[2] https://bugs.debian.org/886155

>> 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).

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.

Best,
Andrius

-- 
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))

[Andrius Merkys]

On Thu, 24 Feb 2022, 22:21 Andreas Tille,  wrote:

> Am Wed, Feb 23, 2022 at 06:10:24PM +0200 schrieb Andrius Merkys:
> > >
> https://github.com/sockjs/sockjs-client/commit/d9584abe2c7c913ce95a1aea29e5744dd85e1af4
> > > <
> 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?


Sure. It would be nice to get ACK from Pirate, though, as he owns the ITP.

FYI, the upload will have to go through NEW due to both source and binary
package renaming.

Best,
Andrius
-- 
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))

[Andrius Merkys]

Hi Eric,

On 2022-02-22 14:52, Eric Brown wrote:
> If I’m understanding the below correctly, it appears that the node-json3
> may already have been removed from the dependency socksjs-client, but
> the updated version is not released yet.
> 
> 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.

Best,
Andrius

-- 
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))

[Andrius Merkys]

Hi Eric,

On 2022-02-22 14:52, Eric Brown wrote:
> If I’m understanding the below correctly, it appears that the node-json3
> may already have been removed from the dependency socksjs-client, but
> the updated version is not released yet.
> 
> https://github.com/sockjs/sockjs-client/commit/d9584abe2c7c913ce95a1aea29e5744dd85e1af4
> 

Great - this saves quite some work.

> I wonder if we ask the dev to consider a release, and then update the
> Debian package, that would solve the problem?

Preferably. Otherwise we could convert this commit to a patch and
attempt applying it, or package development version, but having a stable
release would be better.

Best,
Andrius

-- 
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))

[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).

> [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

-- 
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] block request on js-team packages?

[Andrius Merkys]

Hi Nilesh,

On 2022-01-28 09:48, Nilesh Patra wrote:
> On 1/28/22 12:55 PM, Andrius Merkys wrote:
>> Thanks for the pointer. However, it is not evident to me how this bug
>> could cause false-positive freeze blocks, but maybe there is a whole
>> story behind that. Just minutes ago there was an inquiry on this on
>> debian-devel@, I hope to see the explanation there.
> 
> There's a block-all source hint added, see here[1]
> which is translating to the deep freeze message, it is definitely
> misleading but probably to my understanding britney
> code is not mature enough for real reasons yet.
> 
> About the bug, as far as I saw IRC (I don't see it often - chat pasted
> below) binutils is producing broken binaries because of that
> bug, and since virtually everything in debian would depend on that
> package everything is blocked for now.
> I hope that helps clarify it a bit :)
> 
> [1]: https://release.debian.org/britney/hints/elbrus

[pasted chat skipped]

Thanks, this explains the situation well.

Best,
Andrius

-- 
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] block request on js-team packages?

[Andrius Merkys]

Hi Nilesh,

On 2022-01-27 17:00, Nilesh Patra wrote:
> It is because of:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004272

Thanks for the pointer. However, it is not evident to me how this bug
could cause false-positive freeze blocks, but maybe there is a whole
story behind that. Just minutes ago there was an inquiry on this on
debian-devel@, I hope to see the explanation there.

Best,
Andrius

-- 
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] block request on js-team packages?

[Andrius Merkys]

Hi,

On 2022-01-27 16:49, Yadd wrote:
> tracker.d.o shows reasons. Fixed for node-pbkdf2

I still see "Not touching package due to block request by elbrus (Follow
the freeze policy when applying for an unblock)" in [1], which seems
misleading to me. We are not in freeze, AFAIK.

[1] https://tracker.debian.org/pkg/node-pbkdf2

Andrius

-- 
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] block request on js-team packages?

[Andrius Merkys]

Hi,

On 2022-01-27 16:09, Nicolas Mora wrote:
> It seems that the last javascript packages uploaded to unstable can't
> migrate to testing due to a blocking request, for example:
> 
> https://tracker.debian.org/pkg/node-pbkdf2
> https://tracker.debian.org/pkg/node-jose
> https://tracker.debian.org/pkg/node-i18next
> 
> I don't see any information in the mailing lists, does anyone have
> information about that?

This is not limited to javascript packages. All my migrations seem to be
blocked as well no matter the team/language.

Andrius

-- 
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#1001203: libjs-modernizr: New upstream version required for Rainloop

[Andrius Merkys]

Hi Daniel,

Thanks for sharing your insight into libjs-modernizr.

On 2022-01-21 11:04, Daniel Ring wrote:

On 1/11/2022 1:43 AM, Andrius Merkys wrote:

You said you were interested in updating libjs-modernizr. I need
libjs-modernizr >= 3.5.0 to package node-puppeteer. Could you prepare an
update on a fork/branch in salsa?


I took a look at the changes and it appears that Modernizr upstream has 
switched to a new build system, so updating the Debian package will take 
a non-trivial amount of work. The most significant dependencies appear 
to already be present in Debian, but the new build script still needs to 
be patched.


Are you talking about gulp? I have almost no experience with it, but I 
saw some packages in Debian using it, I might give a shot hacking with it.


Unfortunately, now that the holidays have ended I no longer have 
sufficient spare time to work on this. I'll keep it on my backlog to 
revisit the next time I update the Rainloop package, but it may be a while.


Sure. Would you mind if I import new upstream release to, say, 
'experimental' branch on salsa to try packaging it? Should you have 
anything to contribute, you would be welcome, but I surely get that you 
may not have sufficient time for it.


Best,
Andrius

--
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] RFH: puppeteer tests

[Andrius Merkys]

Hi Yadd,

Thanks a lot for your help!

I see you have updated puppeteer to v13.0.1. Martina and I have
attempted to stick to earlier versions, but if you had luck building
v13.0.1, IMO this is even better.

On 2022-01-14 10:41, Yadd wrote:
> I started to modify your package. The problem for tests is that it
> launches chromium, then this requires X server.

Have you tried xvfb? Most of the time it works for me.

On 2022-01-14 11:18, Yadd wrote:
> and package needs a local chrome (not chromium), automatically
> downloaded during `npm install`

That is what I feared. However, README.md talks about chromium as well,
and firefox seem to have been supported at some stage. As for downloads,
I saw there was a mention of puppeteer-core which attempts to use
as-installed browsers, but I admit I did not do a deep research there.

On 2022-01-14 11:25, Yadd wrote:
> I disabled also the minimal test you put on debian/tests/pkg-js/test: it
> requires network (launches npm view). You should rewrite it in shell
> script (it just compare chrome version to what is set in its
> package.json and node-devtools-protocol version)

Right, I disabled the same test in commit
c28ad891ecd88b517565b03e94d1d1818baf4fdc of 'run-tests' branch.

Thanks once more,
Andrius

-- 
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] RFH: puppeteer tests

[Andrius Merkys]

Hello,

Martina and I have been working on packaging puppeteer, an API to
control Chrome over the DevTools Protocol. Martina got the package
building on sbuild, but we are stuck with tests. Most likely the blocker
is incorrect combination of extcopies/extlinks, but we are not able to
sort it out ourselves. Thus we would be very grateful if someone more
experienced could give it a look.

Packaging of puppeteer is on salsa [1], be sure to use 'run-tests'
branch, as 'master' has tests disabled.

puppeteer depends on devtools-protocol (in NEW). It has to be built from
salsa [2] too, branch 'package-v0.0.869402', as I uploaded an earlier
version to NEW.

Bonus issue is de-vendoring of mitt, which is used for puppeteer tests.
In turn, mitt depends on esm, and this seems nontrivial to package.
However, most likely it has to be done sooner or later, just to be able
to run puppeteer tests.

[1] https://salsa.debian.org/js-team/node-puppeteer
[2] https://salsa.debian.org/js-team/node-devtools-protocol

Thanks in advance,
Andrius

-- 
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#1001203: libjs-modernizr: New upstream version required for Rainloop

[Andrius Merkys]

Hi Daniel,

You said you were interested in updating libjs-modernizr. I need
libjs-modernizr >= 3.5.0 to package node-puppeteer. Could you prepare an
update on a fork/branch in salsa?

Best,
Andrius

-- 
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] node-config_3.3.6.9.g98f2fc9-1_amd64.changes REJECTED

[Andrius Merkys]

Hi Thorsten,

On 2021-12-10 21:00, Thorsten Alteholz wrote:
> please mention "Paul Vorbach and contributors" in your debian/copyright.
Thanks for spotting this! Yadd has fixed the issue, I have uploaded the
fixed version.

Best,
Andrius

-- 
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] Obsolete-new packages

[Andrius Merkys]

Hi Yadd,

On 2021-11-21 15:18, Yadd wrote:
> I just updated npm2deb, however it is a good practice to launch
> `lintian-brush`. In addition, npm2deb's agorithm is very questionable,
> in particular for the search for reverse dependencies.

Thanks for the recommendation. I was not using lintian-brush before as I
usually manage to sort out lintian errors and warnings by hand. Thus I
did not see much need. Now I gave it a shot, it indeed sorted out some
minor lintian notices for me.

> I'll try to package my personal tools which permits to fix many things
> automatically. The best would to include them in lintian-brush but sadly
> I've no talent in Python (all my tools are Perl scripts).

Great!

Best,
Andrius

-- 
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] Obsolete-new packages

[Andrius Merkys]

Hi Yadd,

First and foremost, thank you very much for taking care of my packages!
And sorry for the low quality. I will take your notice into consideration.

On 2021-11-21 09:46, Yadd wrote:
> I don't think it's normal to push package with npm2deb default template
> without looking at debian/* files
> 
>  * debhelper: was 11 in Buster, >2 years ago!
>  * dh-sequence-nodejs: only Buster doesn't know it
>  * : requires for ages
>  * ...
> 
> We have automatic tools such lintian-bruch and we have lintian that
> shows problems. Why are you pushing such dirty work ?

I must admit my knowledge of JS packaging lags quite a lot, thus I rely
a lot on tools. I would expect npm2deb to produce initial packaging at a
fair state, and lintian to throw warnings/errors about the "dirty work"
(as opposed to notes which are quite invisible).

I am aware that npm2deb is not developed by Debian JS Team, thus it is
quite natural it does not follow JS Team policies close enough. Maybe it
should be taken over by Debian, or its usage to do packaging in Debian
be strongly discouraged? (Maybe it is already, only I am not aware).

Best,
Andrius

-- 
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#974064: Bug#974064: node-client-sessions: Remove dependency to (deprecated) node-request

[Andrius Merkys]

Hi,

On 2021-10-08 11:43, Yadd wrote:
> Take a look at
> https://github.com/sindresorhus/got/blob/main/documentation/migration-guides/request.md

Thanks for the link. I recall trying to follow these guidelines, but I
dropped the ball on it.

However, the package seems abandoned upstream and is reportedly broken
[1]. It would be better to find a more up-to-date fork.

[1] https://github.com/mozilla/node-client-sessions/issues/150

Best,
Andrius

-- 
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] Bug#985231: Bug#985231: Bug#985231: TypeError: Cannot use 'in' operator to search for 'dependencies' in ../package.json

[Andrius Merkys]

On 2021-03-19 07:55, Pirate Praveen wrote:
> On 2021, മാർച്ച് 18 8:22:54 PM IST, Andrius Merkys  wrote:
>> Codesearch does not list any uses of node-sass binary. Thus I think it
>> is safe to remove it.
> 
> How? A command line interface can be used directly by users.
> 
> Isn't the command supposed to allow compiling .scss files to .css? 

I am by no means making any claims about usage of node-sass by the end
users. My point was that codesearch.debian.net shows no hits, thus by
removing node-sass executable we are not breaking any other package in
Debian, what would be detrimental during the freeze. Sorry if I was not
clear enough.

My opinion is that shipping broken executable should be a
release-critical bug. Thus if we want to have node-node-sass package in
bullseye, we should either fix node-sass executable, or not ship it at all.

> But I agree if no one is interested to fix this, removing may be the best 
> option now. 
> 
> If someone comes up to fix later, we can add it back.

I suggest doing the same.

Best,
Andrius

-- 
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] Bug#985231: Bug#985231: TypeError: Cannot use 'in' operator to search for 'dependencies' in ../package.json

[Andrius Merkys]

Hi,

On 2021-03-18 18:55, Nilesh Patra wrote:
> On 18 March 2021 8:22:54 pm IST, Andrius Merkys  wrote:
>
> On 2021-03-15 13:45, Pirate Praveen wrote:
>>> If no one steps in to fix this, then we can consider removing it.
>> Codesearch does not list any uses of node-sass binary. Thus I think it
>> is safe to remove it.
> ACK. This should be done after freeze, right?

I would be better to not ship broken things in bullseye, and remove them
afterwards. I suggest removing it before bullseye, and re-adding in the
next point release.

>>>> Also maybe this bug should be reassigned to
>> node-normalize-package-data?
>>> Is node-node-sass using a compatible version of node-normalize-path?
>>>
>>> May be it is expecting a different API? (If the version
>> node-node-sass expects in its package.json is different from the
>> version available in the archive, this can happen).
>>
>> In package.json, node-node-sass does not mention neither
>> node-normalize-package-data nor node-normalize-path.
> It might not be a direct dependency but a transitive one.

True. I prefer leaving it for someone with appropriate knowledge to
investigate further.

Best,
Andrius



-- 
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] Bug#985231: Bug#985231: TypeError: Cannot use 'in' operator to search for 'dependencies' in ../package.json

[Andrius Merkys]

Hello,

On 2021-03-15 13:45, Pirate Praveen wrote:
> On 2021, മാർച്ച് 15 4:21:37 PM IST, Nilesh Patra  wrote:
>>> $ node-sass
>>> /usr/share/nodejs/normalize-package-data/lib/fixer.js:138
>>> if (!(deps in data)) return
>>> ^
>>
>> Since node-node-sass is supposed to be used as a library, probably we do not 
>> need to vendor this binary: /usr/bin/node-sass -> 
>> ../lib/x86_64-linux-gnu/nodejs/node-sass/bin/node-sass
> 
> If someone wants to use the binary and someone cares to make it work, we can 
> fix it.
> 
> If no one steps in to fix this, then we can consider removing it.

Codesearch does not list any uses of node-sass binary. Thus I think it
is safe to remove it.

>> Also maybe this bug should be reassigned to node-normalize-package-data?
> 
> Is node-node-sass using a compatible version of node-normalize-path?
> 
> May be it is expecting a different API? (If the version node-node-sass 
> expects in its package.json is different from the version available in the 
> archive, this can happen).

In package.json, node-node-sass does not mention neither
node-normalize-package-data nor node-normalize-path.

Best,
Andrius

-- 
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] [RFS] -- node-agent-base

[Andrius Merkys]

On 2021-03-17 06:50, Yadd wrote:
> Le 16/03/2021 à 12:22, Andrius Merkys a écrit :
>> I am getting lintian warnings:
>>
>> W: node-agent-base: nodejs-module-not-declared node-async-listen
>> usr/share/nodejs/async-listen/package.json
>> W: node-agent-base: nodejs-module-not-declared node-types-agent-base
>> usr/share/nodejs/@types/agent-base/package.json
>>
>> Could you give them a look?
> 
> Provides: ${nodejs:Provides}

Thanks. Uploaded.

Best,
Andrius

-- 
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] [RFS] -- node-agent-base

[Andrius Merkys]

Hi,

On 2021-03-14 14:49, VIVEK K J wrote:
>   I've been modified node-agent-base package for including
> typescript definitions.. The modified repo is available at
> https://salsa.debian.org/vivekkj/node-agent-base .
> Requesting for Sponsorship..

I am getting lintian warnings:

W: node-agent-base: nodejs-module-not-declared node-async-listen
usr/share/nodejs/async-listen/package.json
W: node-agent-base: nodejs-module-not-declared node-types-agent-base
usr/share/nodejs/@types/agent-base/package.json

Could you give them a look?

Best,
Andrius

-- 
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] [RFS] -- node-agent-base

[Andrius Merkys]

On 2021-03-15 13:51, Pirate Praveen wrote:
> On 2021, മാർച്ച് 15 11:55:19 AM IST, Andrius Merkys  wrote:
>> On 2021-03-14 14:49, VIVEK K J wrote:
>>> I've been modified node-agent-base package for including
>>> typescript definitions.. The modified repo is available at
>>> https://salsa.debian.org/vivekkj/node-agent-base .
>>> Requesting for Sponsorship..
>>
>> Could you please open a merge request against the main repository under
>> salsa.debian.org/js-team/ ? As bullseye
> 
>  A merge request with change in upstream version is harder to do than pulling 
> from a repo. You need to update 3 branches and tags when you import a new 
> version. Adding a component require importing new upstream tarballs.

I see. OK, I was not aware of the new component.

Vivek has pushed everything to js-team/node-agent-base - thanks! I will
upload to experimental ASAP.

Best,
Andrius

-- 
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] [RFS] -- node-agent-base

[Andrius Merkys]

Hi Nilesh,

On 2021-03-15 12:29, Nilesh Patra wrote:
> On 15 March 2021 2:13:10 pm IST, Andrius Merkys  wrote:
>> On 2021-03-15 09:24, Pirate Praveen wrote:
>>> We can upload to experimental so work depending on it does not have
>> to wait.
>>
>> Makes sense. How about creating branch 'experimental' on
>> js-team/node-agent-base and opening a merge request against it from
>> vivekkj/node-agent-base?
> 
> Experimental on a seperate branch doesn't happen in JS team AFAICT. More work 
> :-)
> For example see node-mermaid and npm
OK, so if someone wants to upload to unstable, one will have to branch
off from the last git tag referring to an upload to unstable, right?
Because node-mermaid, for example, already has a new upstream release on
git 'master' branch. Due to that, I prefer the other way round, as
explained by Michael in debian-med@ a couple of weeks ago [1]. I am not
aware of JS team's consensus on the matter.

[1] https://lists.debian.org/debian-med/2021/02/msg00045.html

Best,
Andrius

-- 
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] [RFS] -- node-agent-base

[Andrius Merkys]

On 2021-03-15 09:24, Pirate Praveen wrote:
> On 2021, മാർച്ച് 15 11:55:19 AM IST, Andrius Merkys  wrote:
>> On 2021-03-14 14:49, VIVEK K J wrote:
>>> I've been modified node-agent-base package for including
>>> typescript definitions.. The modified repo is available at
>>> https://salsa.debian.org/vivekkj/node-agent-base .
>>> Requesting for Sponsorship..
>>
>> Could you please open a merge request against the main repository under
>> salsa.debian.org/js-team/ ? As bullseye freeze has already started, I
>> will not merge and upload right away, but will do that as soon as the
>> freeze is over.
> 
> We can upload to experimental so work depending on it does not have to wait.

Makes sense. How about creating branch 'experimental' on
js-team/node-agent-base and opening a merge request against it from
vivekkj/node-agent-base?

Best,
Andrius

-- 
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] [RFS] -- node-agent-base

[Andrius Merkys]

Hello,

On 2021-03-14 14:49, VIVEK K J wrote:
>   I've been modified node-agent-base package for including
> typescript definitions.. The modified repo is available at
> https://salsa.debian.org/vivekkj/node-agent-base .
> Requesting for Sponsorship..

Could you please open a merge request against the main repository under
salsa.debian.org/js-team/ ? As bullseye freeze has already started, I
will not merge and upload right away, but will do that as soon as the
freeze is over.

Thank you for working on this!

Best,
Andrius

-- 
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#981919: 981919: remove mkdirp-classic as well

[Andrius Merkys]

Hello,

mkdirp-classic can also be removed, as it has been packaged as
node-mkdirp-classic. I assume it is embedded here only because of tar-fs.

Andrius

-- 
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#981919: node-yarnpkg: use Debian-provided node-tar-fs

[Andrius Merkys]

Source: node-yarnpkg
Version: 1.22.10+~cs22.25.14-2

node-yarnpkg embeds tar-fs, which has been recently packaged as
node-tar-fs. Please consider using the Debian package instead the
embedded source.

Andrius

-- 
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#980549: Bug#980549: pkg-js-autopkgtest: outdated description

[Andrius Merkys]

On 2021-01-20 15:00, Andrius Merkys wrote:
>> Description: collection of autopktest scripts for Perl packages

Sorry, this line should have been:

> Description: collection of autopktest scripts for Nodejs packages

Nevertheless, 'autopktest' spelling remains.

Best,
Andrius

-- 
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#980549: pkg-js-autopkgtest: outdated description

[Andrius Merkys]

Package: pkg-js-autopkgtest
Version: 0.9.63

There is a couple of outdated/incorrect bits in the description (in
debian/control) of pkg-js-autopkgtest:

> Description: collection of autopktest scripts for Perl packages

s/autopktest/autopkgtest/

>  Packages using the tests with autopkgtests in this package
>  can simply set "Testsuite: autopkgtest-nodejs" in debian/control.

Is 'autopkgtest-nodejs' the right value?
/usr/share/doc/pkg-js-autopkgtest/README.md says it is
'autopkgtest-pkg-nodejs'.

>  Cf. /usr/share/doc/pkg-js-autopkgtest/README.autopkgtest.md
>  for information on the tests and how to tweak them.

This file is not installed by the package anymore.

Andrius

-- 
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] node-uuid 8.x transition

[Andrius Merkys]

On 2020-12-08 08:45, Pirate Praveen wrote:
> On 2020, ഡിസംബർ 8 10:53:26 AM IST, Andrius Merkys  wrote:
>> Hello,
>>
>> On 2020-12-07 20:46, Pirate Praveen wrote:
>>> I have fixed node-request to work with node-uuid 8 API and it also fixed
>>> yarnpkg/gitlab.
>>
>> Does this mean node-request is going to be part of bullseye? There was a
>> mass bug filling (see #974064 for example) suggesting otherwise.
> 
> No, it does not have to be in bullseye. yarnpkg was broken due to this bug, 
> which is also not going to be in bullseye. So any package that wants to be in 
> bullseye should replace dependency on node-request with some other package.

OK, thanks for clarifying this.

> I think we should file an rc bug against node-request to allow auto removal 
> from testing.

I agree. By seeing node-request being worked on I assumed it has been
decided to keep it in bullseye.

Best,
Andrius

-- 
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] node-uuid 8.x transition

[Andrius Merkys]

Hello,

On 2020-12-07 20:46, Pirate Praveen wrote:
> I have fixed node-request to work with node-uuid 8 API and it also fixed
> yarnpkg/gitlab.

Does this mean node-request is going to be part of bullseye? There was a
mass bug filling (see #974064 for example) suggesting otherwise.

Best,
Andrius

-- 
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#975819: 975794 and 975819 are related

[Andrius Merkys]

Hello,

It seems #975794 (node-ws) and #975819 (node-agent-base) are related as
they concern the same piece of code of agent-base, which is packaged in
node-agent-base and embedded in node-ws. Removing agent-base source from
node-ws is underway (#972541).

Best,
Andrius

-- 
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#973962: node-url-parse: please use packaged node-assume

[Andrius Merkys]

Source: node-url-parse

Hello,

'node-url-parse' embeds a copy of source code of 'assume' node module,
which has recently entered Debian as 'node-assume'. Please switch from
embedded code copy to Debian-packaged module.

Best,
Andrius

-- 
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#973961: node-original: please use packaged node-assume

[Andrius Merkys]

Source: node-original

Hello,

'node-original' embeds a copy of source code of 'assume' node module,
which has recently entered Debian as 'node-assume'. Please switch from
embedded code copy to Debian-packaged module.

Best,
Andrius

-- 
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] node-fn.name vs node-fn-name

[Andrius Merkys]

Hello,

On 2020-11-05 11:37, Paul Wise wrote:
> Based solely on the usage information in the README, their APIs are
> compatible, so just changing from fn.name to fn-name or vice versa in
> the require() call will be enough to switch between them.

Thanks, I will try it.

> I'm not sure which one is better, but fn-name started earlier and has
> more recent commits than fn.name.

I too would say that fn-name should be kept and fn.name should be removed.

> I noticed that neither fn-name nor fn-name have any reverse
> dependencies in Debian so perhaps they should just both be removed?

node-assume, which is yet to be uploaded, depends on fn.name. Once I get
to the autopkgtest, I will try drop-in replacing fn.name with fn-name.

> I also noticed that fn-name is outdated in Debian compared to upstream.

Indeed. I will give it a look.

Best,
Andrius

-- 
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] node-fn.name vs node-fn-name

[Andrius Merkys]

Hi Paul,

On 2020-11-05 01:27, Paul Wise wrote:
> Based on the GitHub descriptions, node-fn.name and node-fn-name have
> identical functionality. Should one of them be removed from Debian and
> should one of the upstream projects be replaced by the other within the
> NodeJS ecosystem? It seems pointless to have both exist.
> 
> https://github.com/sindresorhus/fn-name
> https://github.com/3rd-Eden/fn.name

I was aware of node-fn-name at the time I uploaded node-fn.name.
However, due to my lack of experience with NodeJS I did not compare the
packages to understand the difference of their APIs and functionality. I
would love to deduplicate (maybe by removing node-fn.name which should
have less reverse dependencies), but I need someone to confirm that
these packages could be used interchangeably, or provide patching
suggestions if APIs are different.

Best,
Andrius

-- 
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#972541: node-ws: embedded module agent-base is in Debian as node-agent-base

[Andrius Merkys]

Source: node-ws
Version: 7.3.1+~cs24.0.5-1

Dear Maintainer(s),

node-ws embeds nodejs module agent-base which has recently entered
Debian as package node-agent-base. Please remove the embedded module and
depend on node-agent-base instead.

Best wishes,
Andrius

-- 
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] Embedded modules more than once

[Andrius Merkys]

On 2020-09-03 16:23, Jonas Smedegaard wrote:
> Quoting Andrius Merkys (2020-09-03 14:59:38)
>> On 2020-09-03 15:54, Xavier wrote:
>>> buffer-equal:
>>>   - node-buffer-equal (1.0.0)
>>>   - node-vinyl-fs (1.0.0)
>> Does this (and the like) mean that  is now packaged as
>> node-? If so, such embedded modules might be removed.
> Why only "might"?
> 
> I fail to see *any* reason for embedded code to continue exist when 
> available non-embedded.  Please enlighten me, anyone...
> 
> ...or if not, then let us treat such cases as release-critical bugs!

I could not agree more. However, embedded copies sometimes are several
major releases behind, and their replacement requires extensive patching.

Andrius

-- 
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] Embedded modules more than once

[Andrius Merkys]

Hi Xavier,

On 2020-09-03 15:54, Xavier wrote:
> buffer-equal:
>   - node-buffer-equal (1.0.0)
>   - node-vinyl-fs (1.0.0)

Does this (and the like) mean that  is now packaged as
node-? If so, such embedded modules might be removed.

Best,
Andrius

-- 
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#963761: Bug#963761: Bug#963761: node-node-sass: missing versioned dependency relation?: Sass could not find a binding for your current environment

[Andrius Merkys]

On 2020-07-10 12:38, Jonas Smedegaard wrote:
> I suspect you are wrong about relaxing lower bounds to only upstream 
> part.

I got this idea from the way the issue was fixed in node-expat [1].
Could you explain why you think this is a bad idea?

[1]
https://salsa.debian.org/js-team/node-expat/-/commit/fbea3d7cae693f4bd6b7a5a0d7adfbb25792a6a1

Best,
Andrius



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