[Pkg-javascript-devel] Bug#958682: node-jsonld: Remove dependency to node-request

[Pirate Praveen]

On Sun, 29 Oct 2023 21:37:08 +0100 Jonas Smedegaard  wrote:

Yes, I still want to work on node-jsonld - I will make time to look at
this soon...


yarnpkg 4.0.2 was recently uploaded to unstable, so this and 
node-matrix-js-sdk are the only remaining reverse dependencies for 
node-request. We have an ack from its maintainer to remove it 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958692#42 so this is 
the only real blocker remaining to remove node-request.


--
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#1059337: RM: node-request-capture-har -- ROM; wrapper around deprecated node-request

[Pirate Praveen]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: node-request-capture-...@packages.debian.org
Control: affects -1 + src:node-request-capture-har
Control: block 1002901 by -1

Affected by rc bug #1002901 (yarnpkg no longer depend on this library 
from version 4.0.2 in unstable).


--
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#1058596: yarnpkg broken on bookworm - yarnpkg --help fails with TypeError: commander.on is not a function

[Pirate Praveen]

Package: yarnpkg
Version: 1.22.19+~cs24.27.18-2
severity: grave
justification: breaks any options passed to yarnpkg

yarnpkg install also fails with similar errors due to incompatible 
node-commander


We should backport the patches in unstable to bookworm as well.

# cat /usr/share/nodejs/yarn-error.log
Arguments:
  /usr/bin/node /usr/bin/yarnpkg --help

PATH:
  /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

Yarn version:
  1.22.19

Node version:
  18.13.0

Platform:
  linux x64

Trace:
  TypeError: commander.on is not a function
  at Object.run (/usr/share/nodejs/yarn/lib/cli/commands/help.js:75:13)
  at run (/usr/share/nodejs/yarn/lib/cli/index.js:494:30)
  at /usr/share/nodejs/yarn/lib/cli/index.js:732:24

npm manifest:
  No manifest

yarn manifest:
  No manifest

Lockfile:
  No lockfile


# yarnpkg --frozen-lockfile install
TypeError: _commander(...).default.optionFor is not a function
at /usr/share/nodejs/yarn/lib/cli/index.js:355:88
at Array.findIndex ()
at _callee$ (/usr/share/nodejs/yarn/lib/cli/index.js:352:38)
at tryCatch 
(/usr/share/nodejs/@babel/runtime/helpers/regeneratorRuntime.js:44:17)
at Generator. 
(/usr/share/nodejs/@babel/runtime/helpers/regeneratorRuntime.js:125:22)
at Generator.next 
(/usr/share/nodejs/@babel/runtime/helpers/regeneratorRuntime.js:69:21)
at asyncGeneratorStep 
(/usr/share/nodejs/@babel/runtime/helpers/asyncToGenerator.js:3:24)
at _next 
(/usr/share/nodejs/@babel/runtime/helpers/asyncToGenerator.js:22:9)

at /usr/share/nodejs/@babel/runtime/helpers/asyncToGenerator.js:27:7
at new Promise ()

--
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#940511: Bug#940511: Our mutual interest in /usr/bin/yarn

[Pirate Praveen]

On Mon, 21 Nov 2022 09:39:31 +0100 "Yadd"  wrote:

I don't think that "Provides: yarn" is a good thing here since "/usr/bin/yarn" isn't 
provided by yarnpkg. "Provides: node-yarn" seems enough here and without any consequences.


As a compromise, can we have a debconf prompt to notify users about this 
conflict and to run


sudo ln -s /usr/bin/yarnpkg /usr/bin/yarn

if they want to use yarn command.

Automating this via a postinst may be a good idea too, but not sure if 
that is allowed by policy. May be we can ask for an exception since this 
is a special case. This way people who want to use yarn command has a 
way to do it easily.


Prompting users is a bad idea in general if we can have good defaults, 
but we don't have much options left here.


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#980316: Update on packaging corepack

[Pirate Praveen]

On Tue, Mar 21 2023 at 09:06:41 PM +01:00:00 +01:00:00, Paul Gevers 
 wrote:

Hi Pirate,

Thanks for reaching out.

On 20-03-2023 16:44, Pirate Praveen wrote:

I request bookworm-ignore tags for these bugs (as such there is
no immediate breakage, just unmaintained upstreams for these 
packages).


> yarnpkg: 980316,958686, 1002902, 980316
> node-har-validator: 1024575
> node-request: 956423
> node-request-capture-har: 1002901

As the packages in question are key packages, we can't easily remove
them. Hence adding a bookworm-ignore tag doesn't really change the
situation in bookworm in any way. Hence, the question is whether 
fixing

it now and adding an exception is better or worse than letting the bug
ship in bookworm. If I understand correctly, than the required change
would mean a new complex package (corepack) which (again, if I
understand correctly) is considered also by you as inappropriate at 
this

time. If you confirm my understanding, I agree that those bugs can be
marked bookworm-ignore (I already marked them as bookworm-can-defer,
which is less strong and less official).


We won't be able to complete corepack in a few weeks or months. So we 
have to ship bookworm with these bugs and get this fixed in time for 
trixie.




Paul


--
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#1033250: Bug#1033250: Bug#1033250: node-request: CVE-2023-28155

[Pirate Praveen]

Control: block -1 by 956423

On Tue, Mar 21 2023 at 12:05:15 PM +05:30:00 +05:30:00, Pirate Praveen 
 wrote:

$ reverse-depends node-request

Reverse-Depends
===
* node-jsonld
* node-matrix-js-sdk
* yarnpkg

For yarnpkg, we are trying to remove the dependency to node-request, 
see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980316#43 
(hopefully we will be able to remove it for trixie).


Asking yarn upstream as well, if we can remove dependency on request
https://github.com/yarnpkg/yarn/issues/8935

--
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#1033250: Bug#1033250: node-request: CVE-2023-28155

[Pirate Praveen]

On Mon, Mar 20 2023 at 07:34:33 PM +01:00:00 +01:00:00, Moritz 
Mühlenhoff  wrote:

Source: node-request
X-Debbugs-CC: t...@security.debian.org
Severity: normal
Tags: security

Hi,

The following vulnerability was published for node-request.

CVE-2023-28155[0]:
| ** UNSUPPORTED WHEN ASSIGNED ** The Request package through 2.88.1 
for
| Node.js allows a bypass of SSRF mitigations via an 
attacker-controller
| server that does a cross-protocol redirect (HTTP to HTTPS, or HTTPS 
to

| HTTP). NOTE: This vulnerability only affects products that are no
| longer supported by the maintainer.

https://github.com/request/request/issues/3442 was reported, but seems
the module is EOLed, so maybe we should be looking into retiring it
for trixie?


$ reverse-depends node-request
Reverse-Depends
===
* node-jsonld
* node-matrix-js-sdk
* yarnpkg

For yarnpkg, we are trying to remove the dependency to node-request, 
see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980316#43 
(hopefully we will be able to remove it for trixie).



If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-28155
https://www.cve.org/CVERecord?id=CVE-2023-28155

Please adjust the affected versions in the BTS as needed.

--
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 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#980316: Update on packaging corepack

[Pirate Praveen]

On Thu, 16 Mar 2023 10:23:53 +0100 Israel Galadima 
 wrote:

> Hi,
>
> Michael and I have done some packaging work for corepack.
> Of note, we have updated clipanion and packaged some dependencies of
> proxy-agent.
>
> Although, some of our work is awaiting uploads because of the freeze.
>
> Regards.

We tried to update yarnpkg as part of an outreachy project (in two 
rounds), but we could not complete it in time for bookworm. As shared 
by Israel, we made some good progress and we hope to be able to do it 
in trixie. I request bookworm-ignore tags for these bugs (as such there 
is no immediate breakage, just unmaintained upstreams for these 
packages). Hopefully we can handle any security updates ourselves.


Additionally, even though yarnpkg itself is old, the presence of the 
package makes it easy to obtain a newer yarnpkg. In gitlab, I already 
use the packaged yarnpkg command to install a newer yarnpkg[1]. It is 
also very common in nodejs world to use specific version of yarnpkg for 
each project, these are typically installed in .yarn directory for each 
project.


yarnpkg: 980316,958686, 1002902, 980316
node-har-validator: 1024575
node-request: 956423
node-request-capture-har: 1002901

[1] 
https://salsa.debian.org/ruby-team/gitlab/-/blob/master/debian/rake-tasks.sh#L44

runuser -u ${gitlab_user} -- sh -c 'yarnpkg set version berry'

--
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#1033070: unblock: node-babel7/7.20.15+ds1+~cs214.269.168-2

[Pirate Praveen]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: node-bab...@packages.debian.org
Control: affects -1 + src:node-babel7

Please unblock package node-babel7

[ Reason ]
This prevents breaking partial upgrades by updating minimum version of 
node-regexpu-core


[ Impact ]
gitlab partial upgrade from bullseye to bookworm is found to break when 
node-regexpu-core is not upgraded.

https://git.fosscommunity.in/debian-ruby/TaskTracker/-/issues/192

[ Tests ]
No upstream code changed, only minimum version of dependency is updated.

[ Risks ]
No upstream code changed, only minimum version of dependency is updated.

[ Checklist ]
 [x] all changes are documented in the d/changelog
 [x] I reviewed all changes and I approve them
 [x] attach debdiff against the package in testing

[ Other info ]

unblock node-babel7/7.20.15+ds1+~cs214.269.168-2


diff -Nru node-babel7-7.20.15+ds1+~cs214.269.168/debian/changelog node-babel7-7.20.15+ds1+~cs214.269.168/debian/changelog
--- node-babel7-7.20.15+ds1+~cs214.269.168/debian/changelog	2023-02-17 13:35:54.0 +0530
+++ node-babel7-7.20.15+ds1+~cs214.269.168/debian/changelog	2023-03-16 17:52:46.0 +0530
@@ -1,3 +1,11 @@
+node-babel7 (7.20.15+ds1+~cs214.269.168-2) unstable; urgency=medium
+
+  * Update minimum version of node-regexpu-core to 5.2.1~.
+packages/babel-helper-create-regexp-features-plugin/package.json has
+"regexpu-core": "^5.2.1" and not adding it breaks partial upgrades.
+
+ -- Pirate Praveen   Thu, 16 Mar 2023 17:52:46 +0530
+
 node-babel7 (7.20.15+ds1+~cs214.269.168-1) unstable; urgency=medium
 
   * Team upload
diff -Nru node-babel7-7.20.15+ds1+~cs214.269.168/debian/control node-babel7-7.20.15+ds1+~cs214.269.168/debian/control
--- node-babel7-7.20.15+ds1+~cs214.269.168/debian/control	2023-02-17 13:35:54.0 +0530
+++ node-babel7-7.20.15+ds1+~cs214.269.168/debian/control	2023-03-16 17:52:20.0 +0530
@@ -108,7 +108,7 @@
  , node-make-dir
  , node-quick-lru
  , node-regenerator-transform (>= 0.14~)
- , node-regexpu-core
+ , node-regexpu-core (>= 5.2.1~)
  , node-resolve
  , node-semver (>= 7.0~)
  , node-slash
-- 
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#1032962: unblock: node-regexpu-core/5.2.2-3

[Pirate Praveen]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: node-regexpu-c...@packages.debian.org
Control: affects -1 + src:node-regexpu-core

Please unblock package node-regexpu-core

[ Reason ]
This ensure required node-unicode-match-property-ecmascript is used 
during upgrades

from bullseye.
This minimum version requirement is already mentioned in package.json 
by upstream

but missed when preparing the package.

[ Impact ]
This was noticed when testing gitlab upgrade from bullseye-fasttrack to
bookworm-fasttrack
https://git.fosscommunity.in/debian-ruby/TaskTracker/-/issues/192#note_9747
If this is not accepted, either gitlab will have to add this version 
constraint
or the user will have to update this package manually. Gitlab being 
very brittle
about its large dependency chains, directly running a dist-upgrade may 
not be the
best method of upgrade. So it is recommended to upgrade gitlab first 
and then do

the dist-upgrade.

[ Tests ]
No change in upstream code only and implicit dependency made explicit.

[ Risks ]
This only changes minimum version of a dependency which is already 
satisfied in

bookworm but not in bullseye.

[ Checklist ]
 [x] all changes are documented in the d/changelog
 [x] I reviewed all changes and I approve them
 [x] attach debdiff against the package in testing

[ Other info ]

unblock node-regexpu-core/5.2.2-3


diff -Nru node-regexpu-core-5.2.2/debian/changelog node-regexpu-core-5.2.2/debian/changelog
--- node-regexpu-core-5.2.2/debian/changelog	2022-11-30 22:02:03.0 +0530
+++ node-regexpu-core-5.2.2/debian/changelog	2023-03-14 15:01:43.0 +0530
@@ -1,3 +1,12 @@
+node-regexpu-core (5.2.2-3) unstable; urgency=medium
+
+  * Team upload
+  * Update node-unicode-match-property-ecmascript minimum version to (>= 2.0~)
+(This is required to fix breakage in babel-loader when upgrading from
+bullseye)
+
+ -- Pirate Praveen   Tue, 14 Mar 2023 15:01:43 +0530
+
 node-regexpu-core (5.2.2-2) unstable; urgency=medium
 
   [ Debian Janitor ]
diff -Nru node-regexpu-core-5.2.2/debian/control node-regexpu-core-5.2.2/debian/control
--- node-regexpu-core-5.2.2/debian/control	2022-11-30 22:02:03.0 +0530
+++ node-regexpu-core-5.2.2/debian/control	2023-03-14 15:01:43.0 +0530
@@ -13,7 +13,7 @@
node-regjsgen,
node-regjsparser (>= 0.6.4~),
node-unicode-15.0.0,
-   node-unicode-match-property-ecmascript,
+   node-unicode-match-property-ecmascript (>= 2.0~),
node-unicode-match-property-value-ecmascript (>= 2.1~),
dh-sequence-nodejs
 Standards-Version: 4.6.1
@@ -28,7 +28,7 @@
  node-regenerate-unicode-properties (>= 10.1~),
  node-regjsgen,
  node-regjsparser (>= 0.6.4~),
- node-unicode-match-property-ecmascript,
+ node-unicode-match-property-ecmascript (>= 2.0~),
  node-unicode-match-property-value-ecmascript (>= 2.1~),
  ${misc:Depends}
 Multi-Arch: foreign
-- 
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#1032048: d3-dsv-tools: Dangling symlinks in /usr/bin/

[Pirate Praveen]

On Mon, 27 Feb 2023 00:51:52 +0100 Axel Beckert  wrote:
> Package: d3-dsv-tools
> Version: 1.1.1-8
> Severity: grave
> Justification: renders package unusable
>
> $ symlinks -tv /usr/bin* | fgrep dangling
> dangling: /usr/bin/csv2json -> ../share/nodejs/d3-dsv/bin/dsv2json.js
> dangling: /usr/bin/csv2tsv -> ../share/nodejs/d3-dsv/bin/dsv2dsv.js
> dangling: /usr/bin/dsv2dsv -> ../share/nodejs/d3-dsv/bin/dsv2dsv.js
> dangling: /usr/bin/json2csv -> ../share/nodejs/d3-dsv/bin/json2dsv.js
> dangling: /usr/bin/json2dsv -> ../share/nodejs/d3-dsv/bin/json2dsv.js
> dangling: /usr/bin/tsv2csv -> ../share/nodejs/d3-dsv/bin/dsv2dsv.js
> dangling: /usr/bin/json2tsv -> ../share/nodejs/d3-dsv/bin/json2dsv.js
> dangling: /usr/bin/dsv2json -> ../share/nodejs/d3-dsv/bin/dsv2json.js
> dangling: /usr/bin/tsv2json -> ../share/nodejs/d3-dsv/bin/dsv2json.js
>
> Looking at where those files actually might be, I figured that the
> symlinks probably should point to the same target without the .js
> suffix — or that those files need to be renamed:
>
> /usr/share/nodejs/d3-dsv/bin/dsv2dsv
> /usr/share/nodejs/d3-dsv/bin/dsv2json
> /usr/share/nodejs/d3-dsv/bin/json2dsv

debian/nodejs/links should be modified to drop the .js suffix.



since master branch is used for experimental, a new branch for bookworm 
should be created from debian/1.1.1-8 tag


> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers testing
>   APT policy: (600, 'testing')
> merged-usr: yes
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 6.1.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
> Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not 
set

> Shell: /bin/sh linked to /bin/dash
> Init: sysvinit (via /sbin/init)
> LSM: AppArmor: enabled
>
> Versions of packages d3-dsv-tools depends on:
> ii  node-d3-dsv  1.1.1-8
> ii  nodejs   18.13.0+dfsg1-1
>
> d3-dsv-tools recommends no packages.
>
> d3-dsv-tools suggests no packages.
>
> -- no debconf information
>
>



-- 
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#1016732: Bug#1016732: Please help to reproduce (Was: shiny-server: server-function? don't run)

[Pirate Praveen]

On ഞാ, ഫെബ്രു 26 2023 at 02:33:31 രാവിലെ 
+05:30:00 +05:30:00, Pirate Praveen  wrote:



On ഞാ, ഫെബ്രു 26 2023 at 02:24:00 രാവിലെ 
+05:30:00 +05:30:00, Nilesh Patra  wrote:

On Sun, Feb 26, 2023 at 12:46:15AM +0530, Pirate Praveen wrote:
Thanks for the pointer. However, unfortunately even after propagating
the "-t" flag with coffee, the generated code does not work to fine 
(the

UI is not functional).

For now I have vendored coffee1 generated code itself. Do you have 
any

other ideas?


I can see we are using rollup to generate iife format files, which 
may not be what npm dist tarball ships.


https://salsa.debian.org/js-team/node-sockjs/-/blob/master/debian/rules#L8

Upstream directly uses the output from coffee 
https://salsa.debian.org/js-team/node-sockjs/-/blob/master/Makefile#L9


You could play around with rollup output format options I think. Try 
umd format or try using webpack. You will have to inspect the npm 
dist tarball to see what format it has. Copying Akshay if he has some 
ideas.


Since we are using only lib directory in node, ignore the rollup part 
above. In sockjs 0.4 rc1 they removed coffee script dependency, so one 
thing we can try is to see if sockjs 0.4 rc1 works with shiny-server, 
though getting a new upstream version to bookworm may be a hard thing, 
but it may be a better option that vendoring what we have right now.


--
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#1016732: Please help to reproduce (Was: shiny-server: server-function? don't run)

[Pirate Praveen]

On ഞാ, ഫെബ്രു 26 2023 at 02:24:00 രാവിലെ 
+05:30:00 +05:30:00, Nilesh Patra  wrote:

On Sun, Feb 26, 2023 at 12:46:15AM +0530, Pirate Praveen wrote:
Thanks for the pointer. However, unfortunately even after propagating
the "-t" flag with coffee, the generated code does not work to fine 
(the

UI is not functional).

For now I have vendored coffee1 generated code itself. Do you have any
other ideas?


I can see we are using rollup to generate iife format files, which may 
not be what npm dist tarball ships.


https://salsa.debian.org/js-team/node-sockjs/-/blob/master/debian/rules#L8

Upstream directly uses the output from coffee 
https://salsa.debian.org/js-team/node-sockjs/-/blob/master/Makefile#L9


You could play around with rollup output format options I think. Try 
umd format or try using webpack. You will have to inspect the npm dist 
tarball to see what format it has. Copying Akshay if he has some ideas.


--
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#1016732: Please help to reproduce (Was: shiny-server: server-function don't run)

[Pirate Praveen]

On Sun, 12 Feb 2023 23:16:06 +0530 Nilesh Patra  
wrote:
> Sorry for pinging you again, but would you be able to take a look at 
this please?

> I don't know enough coffeescript to be able to check this and it'd be
> awesome if you could consider taking a look.

Coffeescript 2 creates ESM format js by default, adding -t option to 
coffee command should give you the old ES5 javascript like coffeescript 
1.x


See 
https://salsa.debian.org/js-team/node-sockjs/-/blob/master/Makefile#L11


--
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-openpgp-web-stream-tools

[Pirate Praveen]

On 24/1/23 1:07 AM, Sandra Uwah wrote:

Hello,

Requesting sponsorship for the package node-openpgp-web-stream-tools.

Package details:

Package version: 0.0.13

Package repo: 
https://salsa.debian.org/sandra_uwah/node-openpgp-web-stream-tools 



I have made the package lintian clean and built in a clean environment 
with sbuild. Thanks


Sandra


Please add the copyright notice in LICENSE file to debian/copyright

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

[Pirate Praveen]

On 27/12/22 10:36 PM, Israel Galadima wrote:

Hello Debian JavaScript Team,

I'm writing this email to request for sponsorship for a new package I 
have worked on.

Here are the details of the package:

Package Name: node-socks
Package Version: 2.7.1
Debian Version: 2.7.1+dfsg-1
Package Repo: https://salsa.debian.org/izzygala/node-socks

I have built this package successfully using sbuild and it is lintian 
clean.

Thank you for your time.


Pushed to js-team and uploaded. Thanks for your contribution!


--
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] Suggestion: Replace all current and future @unicode packages with node-unicode-data

[Pirate Praveen]

On 27/12/22 3:47 PM, Israel Galadima wrote:

Hi,

I've found that the upstream author for @unicode packages 
uses node-unicode-data to generate the unicode data for all @unicode 
packages.


I was thinking that we could replace all current and future @unicode 
packages with node-unicode-data instead of having separate packages 
for them.


The workflow I am proposing is that we pass the unicode version as a 
parameter to node-unicode-data and it will download and generate the 
unicode data for that version.


Ideally we should be able to get these using watch file/uscan. I'm not 
commenting on the suitability of the whole approach (my comment is 
limited to getting orig.tar part), lets see if others have any comments.

node-unicode-data is not a published npm package so here is the git repo:
https://github.com/node-unicode/node-unicode-data. @unicode packages 
are only used as build dependencies.


I'd be happy to work on the package if the suggestion is agreed upon.

Regards.

-- 
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-file-uri-to-path

[Pirate Praveen]

On 21/12/22 11:32 PM, Israel Galadima wrote:

Hello Debian JavaScript Team,

I'm writing this email to request for sponsorship for a new package I 
have worked on.

Here are the details of the package:

Package Name: node-file-uri-to-path
Package Version: 2.0.0
Debian Version: 2.0.0-1
Package Repo: https://salsa.debian.org/izzygala/node-file-uri-to-path

I have built this package successfully using sbuild and it is lintian 
clean.

Thank you for your time.



Uploaded, thanks for your contribution. Next time for the first upload, 
we usually only add the initial release line, we don't have to add all 
the changes there.



--
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#1026974: Bug#1026974: Bug#1026974: Cannot exclude a component from consideration using !

[Pirate Praveen]

On 26/12/22 1:31 AM, Julian Gilbey wrote:

Yes, these components are C++ code, not Javascript, so I want the
dh-nodejs scripts to completely ignore them.
Then it may be better to package these two separately. Currently I think 
the components are designed work with nodejs only modules I think.


--
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] Request to join the Debian JavaScript Maintainers group

[Pirate Praveen]

On Sun, Dec 11 2022 at 05:45:04 PM +01:00:00 +01:00:00, Yadd 
 wrote:

More simple:

$ pkgjs-depends @mdi/font-build
# @mdi/font-build@1.8.10
# 12 missing npm module(s)
DEPENDENCIES:
  node-argparse (argparse)
  node-commander (commander)
  node-cosmiconfig (cosmiconfig)
  node-deep-equal (call-bind)
  node-deepmerge (deepmerge)
  node-define-properties (define-properties)
  node-es-abstract (es-abstract)
  node-fs-extra (fs-extra)
  node-function-bind (function-bind)
  node-glob (glob)
  node-globby (globby)
  node-meow (meow)
  node-node-sass (node-sass)
  node-nunjucks (nunjucks)
  node-p-limit (p-limit)
  node-pako (pako)
  node-readable-stream (readable-stream)
  node-resolve-from (resolve-from)
  node-sax (sax)
  node-string.prototype.codepointat (string.prototype.codepointat)
  node-svg2ttf (svg2ttf)
  node-xml2js (xml2js)
  node-yargs (yargs)

MISSING:
@mdi/font-build@1.8.10
 └── webfont (9.0.0)
 └── svgicons2svgfont (9.2.0)
 └── array.prototype.flatmap (1.2.4)
 └── geometry-interfaces (1.1.4)
 └── neatequal (1.0.0)
 └── varstream (0.3.2)
 └── string.fromcodepoint (0.2.1)
 └── svg-pathdata (5.0.5)
 └── ttf2eot (2.0.0)
 └── microbuffer (1.0.0)
 └── ttf2woff (2.0.2)
 └── (^) microbuffer (1.0.0)
 └── wawoff2 (1.0.2)


Maybe create just a node-webfont package with embedded dependencies



I have attempted to package this earlier, you can see the existing work 
here

https://salsa.debian.org/js-team/node-webfont

You can try to continue from there.


On 11/12/2022 16:13, Julian Gilbey wrote:

On Sun, Dec 11, 2022 at 11:19:44AM +0100, Yadd wrote:

On 11/12/2022 11:16, Debian GitLab wrote:
Julian Gilbey  requested Developer 
access

to the Debian JavaScript Maintainers
 group.


Hi,

welcome to JS Team, please follow our doc & policy:
  * https://wiki.debian.org/Javascript
  * https://wiki.debian.org/Javascript/Tutorial
  * https://wiki.debian.org/Javascript/GroupSourcesTutorial

Cheers,
Yadd


Thanks Yadd!

I'm just a beginner, but I'm having a look at the
fonts-materialdesignicons-webfont package and trying to update it.  
To

actually build it from source requires 7 as-yet-unpackaged JavaScript
(node) packages (see below).

I'm reading the JavaScript team policy and tutorial.  Once I've
packaged them, would someone with more Debian JavaScript experience 
be

willing to glance over them before I upload them?

One specific point: @mdi/font-build creates a binary called
"font-build", which seems to me perhaps overly generic; though there
doesn't yet exist a binary with that name in the Debian archive, I
wonder whether I should rename it to mdi-font-build instead.

Best wishes,

Julian

The packages needed to build fonts-materialdesignicons-webfont from
source:

* @mdi/font-build
   depends on:
   node-sass [already packaged]
   webfont
   yargs [already packaged]

   * webfont
 depends on:
 cosmiconfig [already packaged]
 deepmerge [already packaged]
 globby [already packaged]
 meow [already packaged]
 nunjucks [already packaged]
 p-limit [already packaged]
 parse-json [already packaged]
 resolve-from [already packaged]
 svg2ttf [already packaged]
 svgicons2svgfont
 ttf2eot
 ttf2woff
 wawoff2
 xml2js [already packaged]

 * svgicons2svgfont
   depends on:
   commander [already packaged]
   glob [already packaged]
   sax [already packaged]
   svg-pathdata
  * ttf2eot
   depends on:
   argparse [already packaged]
    * ttf2woff
   depends on:
   argparse [already packaged]
   pako [already packaged]
    * wawoff2
   depends on:
   argparse [already packaged]

   * svg-pathdata
   no dependencies


--
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 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#1024901: Bug#1024901: node-ts-loader needs chalk4

[Pirate Praveen]

On ഞാ, നവം 27 2022 at 07:40:31 വൈകു +01:00:00 
+01:00:00, Israel Galadima  wrote:

Package: node-ts-loader
Version: 9.4.1-1
Severity: important
X-Debbugs-Cc: izzygalad...@gmail.com , 
pkg-javascript-devel@alioth-lists.debian.net 



While packaging corepack for Debian, I uencountered this error from 
its dependency node-ts-loader:


--
ERROR in ./sources/_entryPoint.ts
Module build failed (from 
../../../../../usr/share/nodejs/ts-loader/index.js):

TypeError: chalk.Instance is not a constructor
at getTypeScriptInstance 
(/usr/share/nodejs/ts-loader/dist/instances.js:34:20)

at Object.loader (/usr/share/nodejs/ts-loader/dist/index.js:15:67)

webpack 5.75.0 compiled with 1 error in 271 ms
---

The error is caused because we are trying to access Instance property 
from the chalk object.
The Instance property is available in only chalk4 and Debian has 
chalk5.
In package.json for node-ts-loader, the chalk version specified is 
chalk4.

I believe we should embed chalk4 inside node-ts-loader.

The preferred way is to update node-ts-loader to use chalk 5 and 
forward patch upstream. If that is too much work, then only embed it.



-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.102.1-microsoft-standard-WSL2 (SMP w/4 CPU threads)
Locale: LANG=en_NG.utf8, LC_CTYPE=en_NG.utf8 (charmap=UTF-8) 
(ignored: LC_ALL set to en_NG.utf8), LANGUAGE=en_NG.utf8

Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages node-ts-loader depends on:
ii  node-chalk  5.1.2-1
ii  node-enhanced-resolve   5.10.0-1
ii  node-micromatch 4.0.5+~4.0.2-1
ii  node-semver 7.3.5+~7.3.9-1
ii  webpack [node-webpack]  5.75.0+dfsg+~cs17.16.14-1

node-ts-loader recommends no packages.

node-ts-loader suggests no packages.

-- no debconf information


-- 
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] Updating and Upgrading debian:dev for docker fails and account is locked (Outreachy Account)

[Pirate Praveen]

On Fri, Oct 21 2022 at 08:28:56 AM +03:00:00 +03:00:00, Joshua Nsereko 
 wrote:
> Could there be any way we could meet synchronously via video or 
audio call at your convenience?
I mean could there be any chance that the Community has weekly, 
monthly or daily scrums?  I would like to join.


We usually work over email and irc. Once a year there is DebConf for in 
person meetups. But we could have one video/audio call for outreachy 
applicants. How about coming Sunday? I'm in GMT+5.30 time zone and 
after noon, evening or night/late night works for me.


https://framadate.org/uX89LBMMKifIPQpX please choose a convenient time 
for the meeting. We can use https://8x8.vc/debian-js-outreachy-22 for 
the meeting at the most convenient time slot.




--
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] Updating and Upgrading debian:dev for docker fails and account is locked (Outreachy Account)

[Pirate Praveen]

On Thu, Oct 20 2022 at 06:16:34 AM +03:00:00 +03:00:00, Joshua Nsereko 
 wrote:
i have set up my environment using docker because am running mac (i 
will change OS after the Contribution Period if need rises) so i used 
docker to setup the unstable debian environment via 
https://gitlab.com/fsci/resources.


As everything seems to work fine, but after running sudo apt-get 
update && sudo apt-get dist-upgradei get the following error and 
using sudo again fails as the account seams broken.


Setting up libc6:amd64 (2.35-3) ...
/usr/bin/perl: error while loading shared libraries: libcrypt.so.1: 
cannot open shared object file: No such file or directory


dpkg: error processing package libc6:amd64 (--configure):

 installed libc6:amd64 package post-installation script subprocess 
returned error exit status 127


Errors were encountered while processing:

 libc6:amd64

E: Sub-process /usr/bin/dpkg returned an error code (1)

root@2ffe435c51e9:/#sudo apt-get update && sudo apt-get dist-upgrade

sudo: account validation failure, is your account locked?



You can try
sudo aptitude safe-upgrade
until the perl transition settled down, and since you seem to be 
running apt-get as root already (# prompt instaed of $) you don't need 
to run sudo again.




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

[Pirate Praveen]

On Wed, Oct 19 2022 at 02:16:42 AM +05:30:00 +05:30:00, Pirate Praveen 
 wrote:



On Mon, Oct 17 2022 at 10:35:41 PM +01:00:00 +01:00:00, Sandra Uwah 
 wrote:

Hello,

Requesting sponsorship for the package : node-d3-array.
Current version: 3.2.0+~cs5.0.6
I have made sure the package is lintian clean and build in a clean 
environment in debspawn .

My salsa  repo: https://salsa.debian.org/sandra_uwah/node-d3-array.


There is still one lintian warning
W: node-d3-array source: mismatched-override 
very-long-line-length-in-source-file *.md line * 
[debian/source/lintian-overrides:2]

please fix it.


Uploaded after this was fixed in salsa. Thanks for your contribution.





--
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] setting up "debian:dev" with docker has default developer account with password unknown (Outreachy Applicant)

[Pirate Praveen]

On Thu, Oct 20 2022 at 02:13:18 AM +03:00:00 +03:00:00, Joshua Nsereko 
 wrote:

I have sent an email at ad...@debian.org w...@debian.org
I have also sent a copy to you so that you are informed of the 
progress.


I hope those are the right people this concern had to go to..

Meanwhile, as I am waiting for their responce, would there be 
something you would recommend me to be doing?  I can even be 
referring me to some docs and/or introducing me to some tool, 
technology that is vital in my budding process.


You can follow the steps mentioned in 
https://wiki.debian.org/Packaging/Learn





--
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] Updating and Upgrading debian:dev for docker fails and account is locked (Outreachy Account)

[Pirate Praveen]

On Thu, Oct 20 2022 at 06:16:34 AM +03:00:00 +03:00:00, Joshua Nsereko 
 wrote:
How do most devs here set up their unstable environment?  Do you run 
a Debian unstable distribution locally on the machine?




I have debian sid on my bare metal laptop. I also use schroot, lxc and 
systemd nspawn for different tasks.




--
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] Updating and Upgrading debian:dev for docker fails and account is locked (Outreachy Account)

[Pirate Praveen]

On Thu, Oct 20 2022 at 06:16:34 AM +03:00:00 +03:00:00, Joshua Nsereko 
 wrote:
i have set up my environment using docker because am running mac (i 
will change OS after the Contribution Period if need rises) so i used 
docker to setup the unstable debian environment via 
https://gitlab.com/fsci/resources.


As everything seems to work fine, but after running sudo apt-get 
update && sudo apt-get dist-upgradei get the following error and 
using sudo again fails as the account seams broken.


Setting up libc6:amd64 (2.35-3) ...
/usr/bin/perl: error while loading shared libraries: libcrypt.so.1: 
cannot open shared object file: No such file or directory


dpkg: error processing package libc6:amd64 (--configure):

 installed libc6:amd64 package post-installation script subprocess 
returned error exit status 127


Errors were encountered while processing:

 libc6:amd64

E: Sub-process /usr/bin/dpkg returned an error code (1)

root@2ffe435c51e9:/#sudo apt-get update && sudo apt-get dist-upgrade

sudo: account validation failure, is your account locked?



How do most devs here set up their unstable environment?  Do you run 
a Debian unstable distribution locally on the machine?




This is very likely to be related to the perl transition
https://lists.debian.org/debian-devel-announce/2022/10/msg5.html 
You can try again after a day or two. Meanwhile you can go through the 
links I shared earlier.




--
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] setting up "debian:dev" with docker has default developer account with password unknown (Outreachy Applicant)

[Pirate Praveen]

On Wed, Oct 19 2022 at 11:32:53 AM +03:00:00 +03:00:00, Joshua Nsereko 
 wrote:
Thanks a lot Pirate.  I have finished setting up the environment.  
Thanks for https://gitlab.com/fsci/resources, which shows the source 
of the image.


Indeed there are a couple of things to change on the wiki 
(https://wiki.debian.org/Packaging/Pre-Requisites/Docker)


It will be my pleasure to update it.  I have tried creating an 
account so that I get editing access but I haven't been successful 
till now.


Actually clicking on the "login" returns forbidden ):


Currently signups needs manual approval. So follow the instructions 
given in the error message you got when you try to sign up. Basically 
you have to send an email telling the admins why you need an account. 
You can mention you are interested in outreachy and want to edit that 
page. Wiki admins will add your email to allow list and then your will 
be able to sign up. Once you get a reply, try signing up again.




--
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] Outreachy applicant RFS

[Pirate Praveen]

On Tue, Oct 18 2022 at 06:33:52 PM +01:00:00 +01:00:00, Lydia Ojoawo 
 wrote:

Hello,

Requesting sponsorship for the package node-follow-redirects

Current version:1.15.1+~1.14.1-3

I have made sure the package is lintian clean and build in a clean a 
environment using debspawn.


My salsa repo:
https://salsa.debian.org/Lydia02/node-follow-redirects



I have left some comments in salsa, please fix them and squash related 
commits for a clean git history. See 
https://www.git-tower.com/learn/git/faq/git-squash for squashing 
commits.



Best regards
Lydia Ojoawo




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

[Pirate Praveen]

On Mon, Oct 17 2022 at 10:35:41 PM +01:00:00 +01:00:00, Sandra Uwah 
 wrote:

Hello,

Requesting sponsorship for the package : node-d3-array.
Current version: 3.2.0+~cs5.0.6
I have made sure the package is lintian clean and build in a clean 
environment in debspawn .

My salsa  repo: https://salsa.debian.org/sandra_uwah/node-d3-array.


There is still one lintian warning
W: node-d3-array source: mismatched-override 
very-long-line-length-in-source-file *.md line * 
[debian/source/lintian-overrides:2]

please fix it.



--
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] setting up "debian:dev" with docker has default developer account with password unknown (Outreachy Applicant)

[Pirate Praveen]

On Tue, Oct 18 2022 at 05:16:38 PM +03:00:00 +03:00:00, Joshua Nsereko 
 wrote:

Reason for mail
After running
docker pull registry.gitlab.com/fsci/resources:debian-dev docker run 
--privileged --name "sid" -it 
registry.gitlab.com/fsci/resources:debian-dev bash
I was prompted to enter the developer password while trying "sudo apt 
update" which i don't even know where to find it from.


Hi Joshua,

This image was created from https://gitlab.com/fsci/resources (I have 
added this link in the wiki now) and README file there has the password 
which is "developer" itself.


May be we need to update that page with changes in the image and also 
may be update the image itself once. You can try both later after you 
get things working.


Thanks
Praveen



--
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] Outreachy applicant RFS

[Pirate Praveen]

On Sat, Oct 15 2022 at 03:13:14 PM +01:00:00 +01:00:00, Lydia Ojoawo 
 wrote:

Hello,

Requesting sponsorship for the package node-npm-package-arg

Current version:9.1.0+~2.0.1-2

I have made sure the package is lintian clean and build in clean 
chroot in debspawn.


My salsa repo: 
https://salsa.debian.org/Lydia02/node-npm-package-arg.git




Uploaded with a small change. You had added one extra blank line in 
changelog entries, which I removed.


Thanks for your contribution to Debian!


Best regards
Lydia Ojoawo


On Sat, 15 Oct 2022, 3:11 pm Lydia Ojoawo,  
wrote:

Hello,

Requesting sponsorship for the package node-npm-package-arg

Current version:9.1.0+~2.0.1-2

I have made sure the package is lintian clean and build in clean 
chroot in debspawn.


My salsa repo: 
https://salsa.debian.org/Lydia02/node-npm-package-arg.git


Best regards




--
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] JS roadmap for Debian 12

[Pirate Praveen]

On Sun, Oct 16 2022 at 09:37:31 AM +02:00:00 +02:00:00, Yadd 
 wrote:

On 16/10/2022 09:13, julien.pu...@gmail.com wrote:

Hi,

Le jeudi 13 octobre 2022 à 15:06 +0200, Yadd a écrit :

there are some pending changes (typescript 4.8, rollup 3,
ajv/schema-utils,...). IMO, the more important is Typescript update
(rollup 2.19.1 looks able to build rollup-3 packages, schema-utils
update may break many things).

Are you OK ? Is someone able to launch a massive rebuild for
typescript reverse dependencies ?



Concerning node-typescript, I haven't updated it in unstable for a
while:
(1) a few of depending packages are broken even without updating it ;
(2) updating it would break a bunch of others ;
(3) I'm a bit short on time for JS packages these days to fix all of
those.

I still pushed to experimental, explaining what I had seen broken.

I'll do a test-run locally to write new lists of (1) and (2): it
doesn't take that much time. [Or more precisely, much of my time! My
box does work for hours...]

I get the initial list of packages using:
   ssh mirror.ftp-master.debian.org "dak rm -Rn node-typescript"
so hopefully the above lists are complete.

Cheers,

J.Puydt


Hi,

I fixed a lot of previously broken things this month. I thinks JS 
packages are now in a good state and we can update typescript and see 
what is broken on next massive rebuild.

So if Team agrees, let's upload typescript 4.8 to unstable.


I don't agree that is a good idea. We should first get a list of things 
broken and evaluate if we can fix or ignore the failures before we 
proceed. This is the standard transition procedure followed for all the 
breaking changes.




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

[Pirate Praveen]

On ഞാ, ഒക്ടോ 24 2021 at 04:19:04 വൈകു +0100 
+0100, Ayoyimika Ajibade  wrote:

Hi There!

I have updated node-xml2js from version (0.2.8 => 0.4.23) The package 
is

available at https://salsa.debian.org/Ayoyimika/node-xml2js/ and i am
requesting for sponsorship and i ensured all tests passed, also tested
all reverse dependencies and there was no failure. , it's lintian 
clean

and built it in a clean chroot with sbuild.



When you upload a new version to the archive, you cannot reuse the same 
version or changelog entry. You have to add a new changelog entry and 
bump the debian revision. Also please push directly to js-team repo 
(please don't force push, only ad new commits to team repo).




--
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-rollup-plugin-sass_1.2.2-1_amd64.changes REJECTED

[Pirate Praveen]

On 23/10/21 11:30 PM, Thorsten Alteholz wrote:
> Hi,
>
> according to LICENSE.md the copyright holder is Thomas Ghysels ...
Fixed and reuploaded.
>
>   Thorsten
>
>
>
> ===
>
> Please feel free to respond to this email if you don't understand why
> your files were rejected, or if you upload new files which address our
> concerns.
>



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

Re: [Pkg-javascript-devel] [RFS] node-xml2js

[Pirate Praveen]

On ബു, ഒക്ടോ 13 2021 at 11:37:55 രാവിലെ +0100 
+0100, Ayoyimika Ajibade  wrote:

Hello!
For the node-xml2js i have reuploaded to experimental. Here is the 
link https://salsa.debian.org/Ayoyimika/node-xml2js




Thanks for your patience in fixing all the issues. I have uploaded it. 
Did you check if any reverse dependency breaks with the new version?


node-carto is removed so we don't have to check it.

On Mon, Sep 27, 2021 at 11:08 PM Pirate Praveen 
 wrote:



 On തി, സെപ്റ്റം 27 2021 at 07:20:42 വൈകു
 +0100 +0100, Ayoyimika Ajibade  wrote:
 > Hi there,
 >
 > I have updated the node-xml2js  from version ( 0.2.8 -> 0.4.23)  
The

 > package is
 >
 >  available at https://salsa.debian.org/Ayoyimika/node-xml2js/ and 
I

 > am requesting
 >
 > for sponsorship and I ensured all tests passed, it's lintian clean
 > and also built it in
 >
 > a clean chroot with sbuild.Thanks
 >

 Since this is a 0.x version package, this could be a breaking 
change.

 See
https://wiki.debian.org/UpdatingaPackagetoNewUpstreamVersion#Breaking_changes

 and target experimental and see if any reverse dependencies break 
with

 the update.

 $ reverse-depends node-xml2js
 Reverse-Depends
 * node-carto
 * node-node-rest-client
 * node-webfinger

 $ reverse-depends -b node-xml2js
 Reverse-Build-Depends
 * node-handlebars
 * node-node-rest-client

 If any of them break with the new version, follow the guidelines in 
the

 link I shared and try fixing those or at least report bugs.



 --
 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 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#995722: Not running tests because tests miss source code is not useful

[Pirate Praveen]

On വെ, ഒക്ടോ 8 2021 at 10:31:16 രാവിലെ +0200 
+0200, Thomas Goirand  wrote:

On 10/7/21 11:40 AM, Pirate Praveen wrote:



 On 7 October 2021 3:02:55 am IST, Thomas Goirand  
wrote:

 On 10/6/21 6:53 PM, Pirate Praveen wrote:

 [adding -devel]

 On ബു, ഒക്ടോ 6 2021 at 12:16:07 വൈകു +0200 
+0200, Jonas Smedegaard

  wrote:

 Quoting Yadd (2021-10-06 11:43:40)

  On Lu, 04 oct 21, 16:40:48, Bastien Roucari�s wrote:
  > Source: src:node-lodash
  > Version: 4.17.21+dfsg+~cs8.31.173-1
  > Severity: serious
  > Justification: do not compile from source
  >
  > Dear Maintainer,
  >
  > The vendor directory should be emptied
  >
  > The debug version is compiled without source (lintian warn) 
and

 moreover the
  > rest of file are already packaged
  >
  > grep -R vendor * gives only a few hit that could be cured by
 symlinking
  >
  > Bastien
  Hi,

  this files are used for test only, maybe severity could be 
decreased.


 I find the severity accurate: Relying on non-source code is a 
severe
 violation of Debian Policy, not matter the purpose of relying on 
it.


 I think we should change the policy here. Running tests helps 
improve
 the quality of the software we ship. Many times the vendored code 
is
 used to ensure the code does not break in a specific situation. I 
don't

 think reducing test coverage in such situations is really helpful.


 Right, running tests helps improve the quality of software we ship.
 Which is why you probably need to test using what's shipped in 
Debian

 rather than using a vendored source-less code.


 We are not shipping the source less code.


You are: Debian also ships source code.


I meant, not shipping in any binary package. Though as Russ mentioned 
in his reply. I will propose a GR.


 This is used only during tests. I don't think we are not gaining 
anything by removing tests here. Just making it harder for the 
package maintainer to run tests.


You would not gain anything by removing tests, but you would win by
making these tests completely free software.


I am just saying it increases the work required to run tests and when 
disabling tests is an option, the incentive is to disable tests.


 If we rely on non-free code for tests, that's really bad too, and 
that
 must be avoided just like we're avoiding source-less code 
everywhere

 else in Debian. The policy shall not change, please.



 The code is not non-free here, just a specific version of a Free 
Software code built outside Debian.


We build from source...


We build the binary packages from source. I don't think it is useful to 
extend that to tests without considering the tradeoffs involved.


 I think tools required for tests should be considered separately 
from tools required to compile. I think it should be treated similar 
to test data.


I don't agree.


ok, lets see how the whole project feels via a GR and settle it. I just 
expressed my opinion, you expressed yours and we need to make a 
decision now.


 What you are proposing would require the package maintainer to 
adapt these tests to versions available (many times with different 
API versions) in Debian and the easier choice is disabling tests.


No. I believe it's ok to have an embedded version of the JS files in 
the
upstream code. This is a *very* different issue, please do not mix 
them.

What I don't like is using a minified version of the JS files. That's
*very* easy (hum... trivial?) to add a non-minified version in your
Debian folder, and use that for tests. You don't care if running the
tests is a little bit slower (because using a source-full version), 
do you?


I don't think you really understand the complexities here. Building the 
minified version is not just running the minifier against the non 
minified code. The non minified code itself is generated using many 
other tools (typescript, transpiled using babel, bundled using rollup 
or webpack etc - many times the versions of these tools are very much 
different versions as well).




However, there's this:

On 10/7/21 6:17 PM, Richard Laager wrote:
 Running tests against vendored dependencies one isn't going to use 
at

 run-time is of limited usefulness.


Best is, if you can, use the library packaged separately, in Debian,
both for tests, and runtime. This way, you do ensure that:
- patching Debian for security is still a thing
- the package can run with the Debian version of the lib



You are completely missing the reality here as well. The runtime 
dependencies are already used from the packaged versions. These 
vendored libraries are used only to create specific test cases or 
sometimes using alternative implementations to test the shipped code.


I think it's less grave than just saying "oh, we don't care about 
these

binary blobs, there's just for tests...". It's even worse, because by
using a different version for tests and runtime, you're faking 
tests...




See above. All runtime dependencies are packaged a

[Pkg-javascript-devel] Bug#995722: Not running tests because tests miss source code is not useful

[Pirate Praveen]

On 7 October 2021 3:02:55 am IST, Thomas Goirand  wrote:
>On 10/6/21 6:53 PM, Pirate Praveen wrote:
>> [adding -devel]
>> 
>> On ബു, ഒക്ടോ 6 2021 at 12:16:07 വൈകു +0200 +0200, Jonas Smedegaard
>>  wrote:
>>> Quoting Yadd (2021-10-06 11:43:40)
>>>>  On Lu, 04 oct 21, 16:40:48, Bastien Roucari�s wrote:
>>>>  > Source: src:node-lodash
>>>>  > Version: 4.17.21+dfsg+~cs8.31.173-1
>>>>  > Severity: serious
>>>>  > Justification: do not compile from source
>>>>  >
>>>>  > Dear Maintainer,
>>>>  >
>>>>  > The vendor directory should be emptied
>>>>  >
>>>>  > The debug version is compiled without source (lintian warn) and
>>>> moreover the
>>>>  > rest of file are already packaged
>>>>  >
>>>>  > grep -R vendor * gives only a few hit that could be cured by
>>>> symlinking
>>>>  >
>>>>  > Bastien
>>>>  Hi,
>>>>
>>>>  this files are used for test only, maybe severity could be decreased.
>>>
>>> I find the severity accurate: Relying on non-source code is a severe
>>> violation of Debian Policy, not matter the purpose of relying on it.
>> 
>> I think we should change the policy here. Running tests helps improve
>> the quality of the software we ship. Many times the vendored code is
>> used to ensure the code does not break in a specific situation. I don't
>> think reducing test coverage in such situations is really helpful.
>
>Right, running tests helps improve the quality of software we ship.
>Which is why you probably need to test using what's shipped in Debian
>rather than using a vendored source-less code.

We are not shipping the source less code. This is used only during tests. I 
don't think we are not gaining anything by removing tests here. Just making it 
harder for the package maintainer to run tests.

>If we rely on non-free code for tests, that's really bad too, and that
>must be avoided just like we're avoiding source-less code everywhere
>else in Debian. The policy shall not change, please.
>

The code is not non-free here, just a specific version of a Free Software code 
built outside Debian.

I think tools required for tests should be considered separately from tools 
required to compile. I think it should be treated similar to test data.

What you are proposing would require the package maintainer to adapt these 
tests to versions available (many times with different API versions) in Debian 
and the easier choice is disabling tests.

I think blindly applying a rule without thinking of any consequences is bad 
too. Just because it is bad in one situation does not mean it will be bad in 
every situation. We should evaluate pros and cons of each situation before 
making a decision. Blind faith is more suitable for religions and not for a 
project like ours.

I think a nocheck build profile which excludes these files from build is 
sufficient to ensure we are not using these to create binary package. This way 
we guarantee only packages in main is used to generate the binary, but still 
allows to run tests optionally making it easy to find problems, especially 
during transitions. Currently when tests are missing transitions are harder 
because we can't find breakages easily since tests are disabled.

The current policy is not making Debian better.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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#995722: Not running tests because tests miss source code is not useful

[Pirate Praveen]

[adding -devel]

On ബു, ഒക്ടോ 6 2021 at 12:16:07 വൈകു +0200 +0200, 
Jonas Smedegaard  wrote:

Quoting Yadd (2021-10-06 11:43:40)

 On Lu, 04 oct 21, 16:40:48, Bastien Roucari�s wrote:
 > Source: src:node-lodash
 > Version: 4.17.21+dfsg+~cs8.31.173-1
 > Severity: serious
 > Justification: do not compile from source
 >
 > Dear Maintainer,
 >
 > The vendor directory should be emptied
 >
 > The debug version is compiled without source (lintian warn) and 
moreover the

 > rest of file are already packaged
 >
 > grep -R vendor * gives only a few hit that could be cured by 
symlinking

 >
 > Bastien
 Hi,

 this files are used for test only, maybe severity could be 
decreased.


I find the severity accurate: Relying on non-source code is a severe
violation of Debian Policy, not matter the purpose of relying on it.


I think we should change the policy here. Running tests helps improve 
the quality of the software we ship. Many times the vendored code is 
used to ensure the code does not break in a specific situation. I don't 
think reducing test coverage in such situations is really helpful.


--
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#995702: Updating caniuse-lite (was: Re: TypeError: Cannot read property 'prefix_exceptions' of undefined)

[Pirate Praveen]

On തി, ഒക്ടോ 4 2021 at 03:17:03 വൈകു +0200 +0200, 
Dominik George  wrote:

Hi,

concerning the update of node-caniuse-lite, I fixed upstream's
deployment script, so that uscan will find new upstream versions
again:

  https://github.com/browserslist/caniuse-lite/issues/84

Shall I update caniuse-lite and upload the new version once uscan is
satisfied again?



Yes, please. You can take a snapshot of the git commit manually (the 
commit logs have version in comments) if you don't want to wait for 
next version. From next version we can continue using uscan.



Cheers,
Nik


--
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] TypeError: Cannot read property 'prefix_exceptions' of undefined

[Pirate Praveen]

On 4 October 2021 6:02:19 pm IST, Dominik George  
wrote:
>>   - let autoprefixerData = { browsers: agents, prefixes: dataPrefixes }
>>   + let autoprefixerData = { browsers: agents.agents, prefixes: dataPrefixes 
>> }
>
>It's
>https://github.com/browserslist/caniuse-lite/commit/fde289588b2ccb129ba3d1552134be2c78fee8b7
>
>So, this happened with a recent update of node-autoprefixer, because
>the new autoprefixer relies on the new API of caniuse-lite.
>
>caniuse-lite should, and will at some point, be updated in Debian as
>well. However, this will break node-browserslist, because that relies
>on the old API. Oh the joy!

Is there a new version of browserslist that uses the new API?

>Proposal:
>
> 1. Add a patch to node-autoprefixer to use the old API
> 2. Add a version constraint to the node-caniuse-lite dependency in
>node-autoprefixer (<< 1.0.30001226~)
> 3. Report a bug against node-caniuse-lite to update to the current
>upstream version, with a gentle hint on what will break if updated
> 4. Once updated, drop the patch, and remove the version constraint
>
>@ JavaScript team, shall I proceed with that?

I think updating node-caniuse-lite and patching node-browserslist may be 
better. But if that is difficult, you can go ahead with this.

BTW I had noticed the breakage while updating gitlab and filed a bug, but did 
not get time to dig deeper. Thanks for these details.

>-nik

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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#995487: ruby-autoprefixer-rails: broken build, breaks gitlab

[Pirate Praveen]

Package: ruby-autoprefixer-rails
version:10.3.1.0+dfsg1+~cs14.6.19-1
Severity: grave

gitlab 14.1 installation fails when using this version. Exact error message 
will be shared after reproducing the error (filing rc bug to block migration to 
testing), downgrading to 10.2 worked.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.-- 
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#995478: node-jsdom: update embedded whatwg-url to 9.x

[Pirate Praveen]

Package: node-jsdom
Version: 16.4.0+~cs77.17.35-4
Severity: important
Control: affects -1 node-autoprefixer

node-autoprefixer needs whatwg-url 9.x, the build is passing with 8.x 
for now, but it is safer to have 9.x version. So please update the 
embedded version.


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

[Pirate Praveen]

On തി, സെപ്റ്റം 27 2021 at 07:20:42 വൈകു 
+0100 +0100, Ayoyimika Ajibade  wrote:

Hi there,

I have updated the node-xml2js  from version ( 0.2.8 -> 0.4.23)  The 
package is


 available at https://salsa.debian.org/Ayoyimika/node-xml2js/ and I 
am requesting


for sponsorship and I ensured all tests passed, it's lintian clean 
and also built it in


a clean chroot with sbuild.Thanks



Since this is a 0.x version package, this could be a breaking change. 
See

https://wiki.debian.org/UpdatingaPackagetoNewUpstreamVersion#Breaking_changes

and target experimental and see if any reverse dependencies break with 
the update.


$ reverse-depends node-xml2js
Reverse-Depends
* node-carto
* node-node-rest-client
* node-webfinger

$ reverse-depends -b node-xml2js
Reverse-Build-Depends
* node-handlebars
* node-node-rest-client

If any of them break with the new version, follow the guidelines in the 
link I shared and try fixing those or at least report bugs.




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

[Pirate Praveen]

On തി, സെപ്റ്റം 27 2021 at 07:13:52 വൈകു 
+0100 +0100, Ayoyimika Ajibade  wrote:
i have updated it pls check 
https://salsa.debian.org/js-team/node-qs/-/branches




Thanks, I have uploaded it now. Thanks for your patience and continuing 
to imrpove the packaging with each comments.


On Mon, Sep 27, 2021 at 11:30 AM Pirate Praveen 
 wrote:



 On 27 September 2021 6:57:12 am IST, Ayoyimika Ajibade 
 wrote:

 >strange which is the command i always use. should i re-push it?

 Yes, and verify the branches are visible on salsa web interface. 
You can try pushing each branch and tags separately too.


 >
 >On Thu, Sep 23, 2021 at 5:57 PM Pirate Praveen 


 >wrote:
 >
 >>
 >>
 >> On വ്യാ, സെപ്റ്റം 23 2021 at 11:46:55
 >> രാവിലെ +0100 +0100, Ayoyimika Ajibade
 >>  wrote:
 >> > Hello!
 >> > I have done so.
 >> > Thanks
 >> >>
 >>
 >> For new upstream versions, you need to push, upstream and 
pristine-tar

 >> branches as well. Also new upstream tag should be pushed as well
 >>
 >> git push -u --all --follow-tags
 >>
 >> is useful command that does all of it.
 >>
 >> > On Mon, Sep 20, 2021 at 8:21 PM Pirate Praveen
 >> >  wrote:
 >> >>
 >> >>
 >> >>  On വ്യാ, സെപ്റ്റം 9, 2021 at 17:03,
 >> >> Ayoyimika
 >> >>  Ajibade  wrote:
 >> >>  > Hi there,
 >> >>  >
 >> >>  > I have updated the node-qs  from version
 >> >>  >
 >> >>  > (6.9.4+ds-1 to 6.10.1)  The package is available at
 >> >>  > https://salsa.debian.org/Ayoyimika/node-qs/ and I am 
requesting

 >> >> for
 >> >>  > sponsorship and I ensured all tests passed, it's lintian 
clean and

 >> >>  > also built it in a clean chroot with sbuild.Thanks
 >> >>  >
 >> >>  Looks good, please push to js-team. if you don't have 
access, please

 >> >>  request access in salsa.
 >> >>
 >> >>
 >>
 >>
 >>

 --
 Sent from my Android device with K-9 Mail. Please excuse my brevity.




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

[Pirate Praveen]

On തി, സെപ്റ്റം 27 2021 at 04:35:44 വൈകു 
+0100 +0100, 'Tunji  wrote:

Hi there,

I earlier updated the node module node-boom from version 9.1.0+~2.0.0 
to 9.1.2+~2.0.0 to be available in experimental, now I have revised 
it to enable auto package test and to be available in unstable. The 
package is available at  
https://salsa.debian.org/thegodtune/node-boom and I am requesting 
that you kindly check if it is clean and fit for sponsorship.


This makes the autopkgtest to pass. But the ideal way is to test 
node-hapi-bounce can be found from the installed location and not from 
the source tree.


So you can run conditional tests, the current tests are good for build 
time tests. For autopkgtest, you can add a condition


if AUTOPKGTEST_TMP variable is defined, then run require ("boom") and 
require("node-hapi-bounce"). Or even better just use the 
autopkgtest-pkg-js option which will test these automatically.


See 
https://wiki.debian.org/Javascript/Tutorial#Switch_test_and_install_to_pkg-js-tools




--
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] how to best handle uglifyjs.terser -> terser migration

[Pirate Praveen]

On 27 September 2021 5:10:59 am IST, Jonas Smedegaard  wrote:
>Package node-terser provides binary package uglifyjs.terser containing a 
>command-line tool by the same name.
>
>Upstream has dropped that and instead provides command-line tool terser.
>
>This change has been prepared in experimental, with a "Breaks" in place.
>
>Problem is: 45 packages build-depends on uglifyjs.terser :-(
>
>How to most sensibly handle a transition?
>
>I cannot File 45 bugreports requesting packages to change at their own 
>pace, because it needs to happen at once.
>
>Any thoughts?

Is all packages maintained by js team? File bugs against packages not 
maintained by js team and give them a heads up when this be uploaded to 
unstable.

We can request a transition tracker from release team.

If we fix a day for uploading to unstable, more people can join and help with 
fixing packages. We can coordinate on irc/pad and upload. I can volunteer. If 
some more join, we can do it in a few days.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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] autopkgtest fails on some packages

[Pirate Praveen]

On വ്യാ, സെപ്റ്റം 23 2021 at 11:41:31 
രാവിലെ -0400 -0400, Nicolas Mora  
wrote:

Hello,

Le 2021-09-23 à 10 h 06, Yadd a écrit :


"pkg-js-autopkgtest-require" tries to use "require(foo)". If your
package isn't a node module, you can:

   echo "require" >debian/tests/pkg-js/SKIP

Be careful to upstream changes. Some updates declares "type: module" 
in

package.json which isn't compatible with our current nodejs


Thanks, I uploaded a new package which skips the tests

What is the issue when a package has "type: module"?
node-i18next-http-backend has it
Is it a concern somehow?


That indicates it is an ES module and only newer versions of nodejs has 
support for it. I think nodejs 14 in experimental supports it, so it 
may be fine to upload to experimental.




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

[Pirate Praveen]

On തി, സെപ്റ്റം 20, 2021 at 12:41, 'Tunji 
 wrote:

Hi there,

I earlier updated the node module node-boom from version 
9.1.0+~2.0.0-1to 9.1.2+~2.0.0 to be available in experimental, now I 
have updated it to enable auto package test and to be available in 
unstable. The package is available at  
https://salsa.debian.org/thegodtune/node-boom and I am requesting 
that you kindly check if it is clean and fit for sponsorship.




This commit looks like you disabled some autopkgtests

https://salsa.debian.org/thegodtune/node-boom/-/commit/1b22eb67601a93298cf0dcc6defe3165e2dbee0f

Thank you.



Olatunji Ajayi







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

[Pirate Praveen]

On വ്യാ, സെപ്റ്റം 9, 2021 at 17:03, Ayoyimika 
Ajibade  wrote:

Hi there,

I have updated the node-qs  from version

(6.9.4+ds-1 to 6.10.1)  The package is available at 
https://salsa.debian.org/Ayoyimika/node-qs/ and I am requesting for 
sponsorship and I ensured all tests passed, it's lintian clean and 
also built it in a clean chroot with sbuild.Thanks


Looks good, please push to js-team. if you don't have access, please 
request access in salsa.




--
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-enhanced-resolve

[Pirate Praveen]

On തി, സെപ്റ്റം 20 2021 at 05:18:35 വൈകു 
+0100 +0100, 'Tunji  wrote:

Hi there,

I have updated the node module node-enhanced-resolve from version 
4.1.0 to version 5.8.2. The package is available at  
https://salsa.debian.org/thegodtune/node-enhanced-resolve and I am 
requesting that you kindly check if it is clean and fit for 
sponsorship.


Please follow https://wiki.debian.org/Javascript/Transitions/Policy 
when uploading breaking changes. Also see https://semver.org for 
determining breaking changes from version numbers.








--
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#994767: rails ftbfs in experimental with The following packages have unmet dependencies: node-debbundle-acorn : Depends: nodejs:any (>= 10.12.0~dfsg~)

[Pirate Praveen]

Package: apt-cudf
Version: 6.0.1-2
Severity: important
X-debbugs-cc: pkg-javascript-de...@lists.alioth.debian.org
Control: affected -1 rails

The following command fails to build rails from experimental (salsa 
master),


DEB_BUILD_PROFILES=nocheck DEB_BUILD_OPTIONS=nocheck sbuild 
--extra-repository='deb http://deb.debian.org/debian experimental main' 
--extra-repository='deb http://incoming.debian.org/debian-buildd/ 
buildd-unstable main' --extra-repository='deb 
http://incoming.debian.org/debian-buildd/ buildd-experimental main' 
--build-dep-resolver=aspcud -d experimental -s


This was working till a few days ago and aptitude does not have this 
problem (replace aspcud with aptitude and build succeeds). There was a 
recent change in how nodejs dependencies are declared and I think this 
is related.


sbuild (Debian sbuild) 0.79.1 (22 April 2020) on mahishi

+==+
| rails 2:6.1.4.1+dfsg-2 (amd64)   Mon, 20 Sep 2021 15:49:27 + |
+==+

Package: rails
Version: 2:6.1.4.1+dfsg-2
Source Version: 2:6.1.4.1+dfsg-2
Distribution: experimental
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Profiles: nocheck
Build Type: full

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/unstable-amd64-sbuild-ce82beed-bc1c-4ff9-a875-c9f3ddbec389'
 with '<>'
I: NOTICE: Log filtering will replace 'build/rails-j7z2gu/resolver-vzgvXO' with 
'<>'

+--+
| Update chroot|
+--+

Hit:1 http://deb.debian.org/debian unstable InRelease
Get:2 http://deb.debian.org/debian experimental InRelease [75.4 kB]
Get:3 http://deb.debian.org/debian experimental/main amd64 Packages [521 kB]
Get:4 http://incoming.debian.org/debian-buildd buildd-unstable InRelease [39.7 
kB]
Get:5 http://incoming.debian.org/debian-buildd buildd-experimental InRelease 
[39.8 kB]
Get:6 http://incoming.debian.org/debian-buildd buildd-unstable/main amd64 
Packages [176 kB]
Get:7 http://incoming.debian.org/debian-buildd buildd-experimental/main amd64 
Packages [32.1 kB]
Fetched 884 kB in 15s (59.0 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages were automatically installed and are no longer required:
  bsdextrautils fontconfig-config fonts-dejavu-core krb5-locales libbrotli1
  libbsd0 libc-devtools libdeflate0 libexpat1 libfontconfig1 libfreetype6
  libgd3 libjbig0 libjpeg62-turbo libmd0 libnss-nis libnss-nisplus libpng16-16
  libtiff5 libwebp6 libx11-6 libx11-data libxau6 libxcb1 libxdmcp6 libxpm4
  manpages manpages-dev sensible-utils ucf
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

+--+
| Fetch source files   |
+--+


Local sources
-

/home/pravi/forge/ruby-team/rails_6.1.4.1+dfsg-2.dsc exists in 
/home/pravi/forge/ruby-team; copying to chroot
I: NOTICE: Log filtering will replace 'build/rails-j7z2gu/rails-6.1.4.1+dfsg' 
with '<>'
I: NOTICE: Log filtering will replace 'build/rails-j7z2gu' with '<>'

+--+
| Install package build dependencies   |
+--+


Setup apt archive
-

Merged Build-Depends: debhelper-compat (= 13), gem2deb, rollup, 
node-rollup-plugin-node-resolve (>= 11~), node-rollup-plugin-commonjs (>= 15~), 
node-rollup-plugin-babel (>= 5.2~), node-babel7, webpack, ruby-byebug, puma (>= 
4.1~), racc, rake (>= 11.1), ruby-bcrypt (<< 3.2), ruby-bcrypt (>= 3.1.11), 
ruby-benchmark-ips, ruby-blade, ruby-blade-sauce-labs-plugin, ruby-capybara (>= 
2.15), ruby-chromedriver-helper, ruby-connection-pool, ruby-dalli, 
ruby-delayed-job, ruby-delayed-job-active-record, ruby-hiredis, 
ruby-image-processing (<< 2.0), ruby-json (>= 2.0.0), ruby-libxml, ruby-listen 
(>= 3.2~), ruby-minitest-reporters, ruby-mysql2 (>= 0.4.10), ruby-pg (>= 
0.18.0), ruby-rack-cache (<< 2.0), ruby-redis (<< 5.0), ruby-redis (>= 4.0), 
ruby-redis-namespace, ruby-sass-rails (>= 6.0~), ruby-sdoc, 
ruby-selenium-webdriver, ruby-sequel, ruby-sidekiq, ruby-sprockets-export, 
ruby-sqlite3, ruby-turbolinks (>= 5.0), ruby-uglifier, ruby-webmock, 
build-essential, fakeroot
Filtered Build-Depends: debhelper-compat (= 13), gem2deb, rollup, 
node-rollup-plugin-node-resolve (>= 11~), 

Re: [Pkg-javascript-devel] Export both ESM and CommonJS modules

[Pirate Praveen]

On 13 September 2021 1:35:57 pm IST, Julien Puydt  
wrote:
>Le dimanche 12 septembre 2021 à 20:30 +0200, Yadd a écrit :
>> You'll notice that I didn't fault anyone, I just tried not to let
>> other groups get stuck with our updates. I think I did something
>> clean that avoids breaking other packages until nodejs is updated 
>> and keeps the upstream format.
>
>Well, I still felt blamed, and it's only partly justified.
>
>In that particular case, I saw the problem, produced a -1 with a patch
>to avoid breaking deps, but asked around because it was somehow not
>satisfying, with mostly two questions:
>1. if what I did was a good idea?
>2. how to do something clean?
>
>The summary of the answers is that it was a bad idea (don't diverge
>from upstream unless you're ready to take matters on your shoulders),
>but there was no clean solution.
>
>I hence broke things with -2: that's just the first occurrence of an
>emerging matter, so waiting won't make it go away. Bite the bullet
>rather sooner than later, one may say.

We still has the option to use experimental for understanding breaking changes 
and giving more time to fix reverse dependencies. I suggested this option too 
in the earlier thread.

I don't think breaking unstable directly is a good idea, we have well 
established process for dealing with breaking changes properly - using 
experimental and giving warning bugs to affected packages before the breaking 
change goes to unstable. Giving people time to fix is important as scrambling 
to fix an rc bug is more painful, especially if it is not clear which update 
broke your package.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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] Export both ESM and CommonJS modules

[Pirate Praveen]

On ഞാ, സെപ്റ്റം 12, 2021 at 18:29, Yadd 
 wrote:

Hi all,

some recent updates switched from CommonJS to ESM ("type: module"). I
found a way for node-strip-json-comments which can be applied to most 
of

Sindre Sorhus modules:

 1. build a commonjs file:

babeljs -o index.cjs index.js
perl -i -pe 's/^export default/module.exports =/' index.cjs

 2. adapt package.json:

--- a/package.json
+++ b/package.json
@@ -11,7 +11,12 @@
"url": "https://sindresorhus.com;
},
"type": "module",
-   "exports": "./index.js",
+   "exports": {
+   "import": "./index.js",
+   "require": "./index.cjs"
+   },
+   "main": "./index.cjs",
+   "module": "./index.js",
"engines": {
"node": "^12.20.0 || ^14.13.1 || >=16.0.0"
},
@@ -20,6 +25,7 @@
"bench": "matcha benchmark.js"
},
"files": [
+   "index.cjs",
"index.js",
"index.d.ts"
],

For more complex packages, see
https://www.sensedeep.com/blog/posts/2021/how-to-create-single-source-npm-module.html


I don't think this approach (tryng to support two versions of 
everything) is really sustainable, for one or two packages it would be 
fine. We should look at it like any breaking major version update and 
try to update reverse dependencies to new APIs (switch to import from 
require) and only if that is too much work, we should try to support 
both versions.


With nodejs supporting ESM natively, we should try to avoid as much of 
build steps as possible.




--
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-tslib 2.3.1

[Pirate Praveen]

On ബു, സെപ്റ്റം 8 2021 at 10:21:02 വൈകു 
+0530 +0530, Vivek K J  wrote:
I just tried building reverse dependencies using the latest 
node-tslib. Lumino[1], node-ast-types[2] and node-recast[3] returned 
FAIL status. unfortunately I can't build 
node-rollup-plugin-typescript using the same script. (Waited over 2 
hrs. :( ). So what's next ?


You can upload this to experimental and file bugs against these 
packages with severity important. Wait 2-3 weeks if they want to fix it 
(helping to fix them is welcome too).


See https://wiki.debian.org/Javascript/Transitions/Policy



--
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] Proposal for next round of outreachy - looking for interested mentors

[Pirate Praveen]

Hi,

I think this round of outreachy was very good for the js team (we got 3 
new contributor who are still active in the team and I am asking them 
to apply as DMs).


I was thinking of proposing nodejs 16 and webpack 5 transitions as 
possible project ideas for this round of outreachy.


Anyone would like to join as co-mentors?

Thanks
Praveen



--
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] Issues with node-rollup-plugin-node-resolve

[Pirate Praveen]

On തി, സെപ്റ്റം 6, 2021 at 08:42, Julien Puydt 
 wrote:

Hi,

I tried to update the above-mentioned package and pushed quite a few
changes but:

- it looks like the orig tarball generation is quite strange, with a
succession of "Files-Excluded: *" and "Files-Included: very short 
list"

which confuses both dpkg-source and lintian -- and there's no +dfsg or
+ds or +repack suffix...

Because upstream uses a mono repo for all plugins and we need to pick 
only the required plugin in our orig tar. Since each plugin is released 
independantly, we can have a single source package to build all plugins 
in one source package.


uscan will handle this instructions.


- I still have a failing test in the upstream test suite (heavily
patched to use tape instead of ava... will have to check for a RFP),
with little clue as to why it is failing.

If you have insight or ideas about those matters, don't hesitate: I
won't touch the package in the coming days...

Cheers,

J.Puydt


--
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 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] OUTREACHY INTERN FINAL BLOG POST

[Pirate Praveen]

2021, സെപ്റ്റംബർ 3 5:05:33 AM IST, Tunji ൽ എഴുതി
>Hi everyone.
>
>I'm glad to share the summary of my Outreachy internship period with
>you all in this final blog post.
>
>The internship which spanned from May to August'21 was primarily with
>the js-team.
>
>The blog is written to basically summarize so there are no in-depth
>definitions for the sake of future internship applicants that may
>stumble on it.(reason being that blogs like that helped during my
>applicantion period)
>
>Find it here: https://thegodtune.hashnode.dev/wrap-up

Thanks for the blog post and your work!

Hoping to see you around in Debian.

>I hope you have a good read.
>
>Thank you. ♥️

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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] OUTREACHY INTER FINAL INTERNSHIP BLOG POST

[Pirate Praveen]

2021, ഓഗസ്റ്റ് 30 4:02:57 AM IST, Nkwuda Sunday ൽ എഴുതി
>Hi folks.
>
>I'm super excited to share my final internship blog post for the May'21 
>Outreachy Internships with the js-team.
>
>This blog is a summary of my my experiences throughout the internship, 
>what I've been working on, things I have learnt and the next steps 
>forward for me.
>
>Please check it out -> 
>https://sonnie.hashnode.dev/outreachy-internship-wrap-up

Thanks for the blog post and your contributions. Looking forward to seeing you 
in Debian.

Praveen
>
>Regards,
>
>Sunday
>
>
>

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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 fixing test failures in node-es-abstract

[Pirate Praveen]

On ശ, ഓഗ 28, 2021 at 00:20, Ayoyimika Ajibade 
 wrote:

Hi there,
I have updated the node-es-abstract  from version 
1.18.0~next~2+~cs13.20.17-1 to 1.18.5+~cs22.23.45-1 The package is 
available at
https://salsa.debian.org/Ayoyimika/node-es-abstract/ and I am 
requesting for help to fix test failures with autopkgtest, it's 
lintian clean and also built it in a clean chroot with sbuild.Thanks


See the failed log
https://salsa.debian.org/Ayoyimika/node-es-abstract/-/jobs/1868103#L2231

Looks like node-deep-equal is conflicting with some other package (may 
be two packages embedding same module).




--
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-strip-json-comments: a dirty patch

[Pirate Praveen]

2021, ഓഗസ്റ്റ് 27 6:47:50 PM IST, Julien Puydt ൽ എഴുതി
>Le vendredi 27 août 2021 à 12:20 +0200, Yadd a écrit :
>> use `echo require > debian/tests/pkg-js/SKIP` for such modules.
>
>That makes a node-something package not try to require itself as part
>of the autopkgtest-ing ; but I don't think that answers my question.
>
>The current upstream version of strip-json-comments declares it's a JS-
>module -- hence it can't be require'd. With my dirty patch, I made it
>possible again, so existing node-* packages work -- that was the goal:
>don't break deps.
>
>But of course, future packages (or future versions of existing ones)
>will probably work différently. Let's assume in the near future we end
>up with:
>(1) node-foo wants to import node-strip-json-comments ;
>(2) node-bar wants to require it.
>If I understand well, without my dirty patch, node-bar has a problem,
>and with it node-foo has a problem.
>
>So my question is: is it possible to handle things cleanly and how?
>
>[If not, I'll drop the patch and upload a breaking package immediately:
>the sooner broken, the sooner fixed...]

Please use experimental for breaking changes. Upload to unstable only after 
fixing all reverse dependencies or giving a reasonable notice with a important 
severity bug.

This is like a major version transition. All dependencies may also need updates 
to use import instead of require.

May be pkg-js-tools should skip require tests for modules which declare 
type=module in package.json
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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#992650: mocha: and node-ci-info provides is-unicode-supported

[Pirate Praveen]

Package: mocha,node-ci-info
severity: important

Package node-is-unicode-supported is a virtual package provided by:
 node-ci-info 3.2.0+~cs4.2.0-1
 mocha 9.0.3+ds1+~cs30.4.31-2
You should explicitly select one to install.

I propose we drop it from mocha as it is heavier dependency. I added 
is-unicode-supported in node-ci-info as a dependency of node-tsdx which 
is still in progress. Though we will need to upload node-ci-info to 
unstable first.


--
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] nodejs 16 in bookworm

[Pirate Praveen]

On Mon, Aug 16, 2021 at 12:32 pm, Jérémy Lal  
wrote:

Hi,
considering that nodejs 16 starts to be LTS the 10/2021 and 
maintenance ends 04/2024:

https://nodejs.org/en/about/releases/

I propose to jump directly from 12 to 16.
Plan: upload nodejs 16 to experimental (as soon as possible),
and when it builds fine on all architectures, to sid.


Sounds good to me.


Jérémy




--
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-es-abstract

[Pirate Praveen]

On Mon, Aug 2, 2021 at 20:00, Ayoyimika Ajibade 
 wrote:

Hi there,

I have updated the node-es-abstract  from version

( 1.18.0~next~2+~cs13.20.17   to 1.18.4+~cs13.21.21 )  The package is 
available at https://salsa.debian.org/Ayoyimika/node-es-abstract/ and 
I am requesting for sponsorship and I ensured all tests passed, it's 
lintian clean and also built it in a clean chroot with sbuild.Thanks



Please check autopkgtest as well, it is currently failing.



--
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#991651: twitter-bootstrap4: FTBFS: Browserslist: caniuse-lite is outdated. Please run: npx browserslist@latest --update-db

[Pirate Praveen]

Control: retitle -1 FTBFS: Replace Autoprefixer browsers option to 
Browserslist config


On Thu, 29 Jul 2021 17:19:34 +0200 Lucas Nussbaum  
wrote:

> Source: twitter-bootstrap4
> Version: 4.5.2+dfsg1-6
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20210728 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all packages in bullseye, your package failed to 
build

> on amd64.
>
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > mkdir -p dist/css dist/js dist/tmp
> > sassc --sourcemap=auto scss/bootstrap.scss dist/tmp/bootstrap.css
> > sassc --sourcemap=auto scss/bootstrap-grid.scss 
dist/tmp/bootstrap-grid.css
> > sassc --sourcemap=auto scss/bootstrap-reboot.scss 
dist/tmp/bootstrap-reboot.css

> > node debian/postcss.js
> >
> >   Replace Autoprefixer browsers option to Browserslist config.
> >   Use browserslist key in package.json or .browserslistrc file.
> >
> >   Using browsers option can cause errors. Browserslist config can
> >   be used for Babel, Autoprefixer, postcss-normalize and other 
tools.

> >
> >   If you really need to use option, rename it to 
overrideBrowserslist.

> >
> >   Learn more at:
> >   https://github.com/browserslist/browserslist#readme
> >   https://twitter.com/browserslist

Dropping this line should fix the bug I think,

https://salsa.debian.org/js-team/twitter-bootstrap4/-/blob/master/debian/postcss.js#L28

It already ships a .browserslistrc file 
https://salsa.debian.org/js-team/twitter-bootstrap4/-/blob/master/.browserslistrc


--
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#991656: node-superagent: FTBFS: Browserslist: caniuse-lite is outdated. Please run: npx browserslist@latest --update-db

[Pirate Praveen]

Control: retitle -1  Unknown browser query `> 1%`. Maybe you are using 
old Browserslist or made typo in query.


On Thu, 29 Jul 2021 17:14:42 +0200 Lucas Nussbaum  
wrote:

> Source: node-superagent
> Version: 6.1.0-3
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20210728 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all packages in bullseye, your package failed to 
build

> on amd64.
>
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > babeljs --config-file ./.lib.babelrc src --out-dir lib
> > Browserslist: caniuse-lite is outdated. Please run:
> > npx browserslist@latest --update-db
> >
> > Why you should do it regularly:
> > https://github.com/browserslist/browserslist#browsers-data-updating
> > Error [BrowserslistError]: [BABEL] 
/<>/src/agent-base.js: Unknown browser query `> 1%`. Maybe 
you are using old Browserslist or made typo in query. (While 
processing: "/usr/share/nodejs/@babel/preset-env/lib/index.js")


The actual error that caused failure is,
Unknown browser query `> 1%`. Maybe you are using old Browserslist or 
made typo in query.


This patch fixes the build failure, .browserslistrc already has these 
values and babel-preset-env recommends using this option as per 
https://babeljs.io/docs/en/babel-preset-env#browserslist-integration


--- a/.lib.babelrc
+++ b/.lib.babelrc
@@ -2,8 +2,7 @@
  "presets": [
["@babel/env", {
  "targets": {
- "node": "6.4.0",
- "browsers": [ "> 1%", "last 2 versions", "ie 9" ]
+ "node": "6.4.0"
  }
}]
  ],

But later down in the same doc it says,

By default @babel/preset-env will use browserslist config sources 
unless either the targets or ignoreBrowserslistConfig options are set.


and we have targets option set here. One option would be to drop 
targets entirely as we need to support only the nodejs version shipped 
with debian.


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

[Pirate Praveen]

On Wed, Jul 21, 2021 at 02:50, Ayoyimika Ajibade 
 wrote:

Hi there,

I have updated the node-qs  from version  6.9.4 to 
6.10.1+ds+_cs5.1.12 The package is available at 
https://salsa.debian.org/Ayoyimika/node-qs/ and I am requesting for 
sponsorship and I ensured all tests passed, it's lintian clean and 
also built it in a clean chroot with sbuild.Thanks



Hi Ayoyimika,

Thanks for your work. Some comments about the package.

1. See 
https://wiki.debian.org/Javascript/Nodejs/Npm2Deb#Update_copyright_file 
about different versions of MIT and modify your copyright file 
accordingly.
2. apt-file find get-intrinsic shows it is already embedded in 
node-es-abstract and node-webassemblyjs so can try to install 
get-intrinsic as a root_module in one of these packages and add a 
dependency for it. So please use apt-file find before you embed a 
package. I think providing it in node-es-abstract would be fine.

3. call-bind is also in the same situation as get-intrinsic
4. has-symbols is already available as a package, aptitude can be used 
to find out if any real package provides a given virtual package.

aptitude show node-has-symbols
No candidate version found for node-has-symbols
Package: node-has-symbols
State: not a real package
Provided by: node-debbundle-es-to-primitive (1.2.1+~cs9.7.15-2)
5. aptitude show node-has
No candidate version found for node-has
Package: node-has
State: not a real package
Provided by: node-function-bind (1.1.1+repack-1)
6. Simplify the changelog entry by keeping only the latest version of 
New Upstream version line and probably use a single entry for embedding 
modules, use coma to separate all embedded modules in a single entry.


Please fix these issues and reply to this mail.



--
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#990458: babel umd support is limited

[Pirate Praveen]

On Sat, 03 Jul 2021 23:01:35 +0530 Pirate Praveen 
 wrote:
> I switched to rollup for generating umd and removed 
add-module-exports
> plugin and it is working now. Possibly defining "autosize" global 
with

> @babel/plugin-transform-modules-umd without add-module-exports plugin
> would have worked as well.

I tried this option today and it did not work. Looks like this is a 
known limitaion of babel umd plugin. 
https://github.com/babel/babel/issues/10696 so we will stick with 
rollup.


--
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#990458: libjs-autosize is not fixed by node-babel-plugin-add-module exports update

[Pirate Praveen]

On Sat, 03 Jul 2021 18:11:20 +0530 Pirate Praveen 
 wrote:
> But this is babel 6 to babel 7 migration. The code transpiled by 
babel

> 6 works fine, but moving to babel 7 broke it.

One possibility is that the add-module-exports plugin is not compatible 
with babel 7's umd plugin (@babel/plugin-transform-modules-umd).


--
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#990458: libjs-autosize is not fixed by node-babel-plugin-add-module exports update

[Pirate Praveen]

On Sat, Jul 3, 2021 at 12:29 pm, Akshay S Dinesh  
wrote:

https://stackoverflow.com/questions/33505992/babel-6-changes-how-it-exports-default

But most importantly 
https://kentcdodds.com/blog/misunderstanding-es6-modules-upgrading-babel-tears-and-a-solution


But this is babel 6 to babel 7 migration. The code transpiled by babel 
6 works fine, but moving to babel 7 broke it.


and looks like autosize upstream moved their build system to 
microbundle (an absctraction of rollup and babel with a set of plugins) 
which is not packaged yet.


--
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#990458: libjs-autosize is not fixed by node-babel-plugin-add-module exports update

[Pirate Praveen]

Control: reopen -1

On Wed, 30 Jun 2021 22:40:13 +0530 Pirate Praveen 
 wrote:

> and this is working with diaspora. Thanks again for tracking down the
> issue.

Looks like I was wrong here and it is still failing with libjs-autosize 
built with latest node-babel-plugin-add-module-exports.


You can see this on browser console of 
https://diaspora.publicvm.com/statistics (setup by Rojin for testing).


--
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#990493: node-babel-plugin-add-module-exports broken with babel-preset-env 7

[Pirate Praveen]

On Wed, 30 Jun 2021 21:23:37 +0530 Pirate Praveen 
 wrote:

> $ reverse-depends -b node-babel-plugin-add-module-exports
> Reverse-Build-Depends
> * autosize.js
> * node-babel-plugin-lodash
> * node-colormin
> * node-css-loader
> * node-deep-for-each
> * node-es6-promise
> * node-handlebars
> * node-i18next-http-backend

Using
https://wiki.debian.org/Javascript/Nodejs/Transitions/Babel7#Reverse_build_dependencies_of_node-babel-plugin-add-module-exports 
to track status of reverse build dependencies. If you'd like to help, 
please pick one from the list and add your name in the wiki.


--
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#990493: node-babel-plugin-add-module-exports broken with babel-preset-env 7

[Pirate Praveen]

On Wed, Jun 30, 2021 at 6:02 pm, Yadd  wrote:

Le 30/06/2021 à 17:53, Pirate Praveen a écrit :

 Package: node-babel-plugin-add-module-exports
 Version: 0.2.1-3
 Severity: grave
 Justification: creates broken build output
 Control: forwarded -1
 https://github.com/59naga/babel-plugin-add-module-exports/issues/73
 Control: block 990458 by -1

 Upstream has released a fix in major update. Since we are in freeze 
I'm

 not sure how to proceed here. This affects many packages.


Try a pre-approval unblock


I think we will need to rebuild all reverse build dependencies and 
document the changes in build results before we ask release team. I 
already fixed autosize.js in experimental.


Help is welcome to rebuild and test others, since they are arch all, I 
think binNMU won't work.





 $ reverse-depends -b node-babel-plugin-add-module-exports
 Reverse-Build-Depends
 * autosize.js
 * node-babel-plugin-lodash
 * node-colormin
 * node-css-loader
 * node-deep-for-each
 * node-es6-promise
 * node-handlebars
 * node-i18next-http-backend



--
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 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#990458: Bug#990458: Bug#990458: Bug#990458: Attaching the files from buster vs bullseye

[Pirate Praveen]

On Wed, Jun 30, 2021 at 9:44 pm, Pirate Praveen 
 wrote:



On Wed, Jun 30, 2021 at 9:38 pm, Pirate Praveen 
 wrote:
Looks like we are already using the dist tarballs and does not 
involve any build, we can just take the latest 1.0.4 from npmjs.com.


Scratch that, the new versions use babel to build, so I think using 
https://github.com/lijunle/babel-plugin-add-module-exports/ is the 
best option, though the latest version tagged is 1.0.2 and latest npm 
release is 1.0.4 (basically completely messed up release workflow).


With babel-plugin-add-module-exports 1.0.4 from the above repo,

$ diff -u autosize-current.js autosize.js
--- autosize-current.js 2021-06-30 22:30:00.391798535 +0530
+++ autosize.js 2020-12-14 17:42:45.0 +0530
@@ -284,5 +284,5 @@

  var _default = autosize;
  _exports["default"] = _default;
-  module.exports = exports["default"];
+  module.exports = exports.default;
});
\ No newline at end of file

and this is working with diaspora. Thanks again for tracking down the 
issue.


--
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#990458: Bug#990458: Bug#990458: Attaching the files from buster vs bullseye

[Pirate Praveen]

On Wed, Jun 30, 2021 at 9:38 pm, Pirate Praveen 
 wrote:
Looks like we are already using the dist tarballs and does not 
involve any build, we can just take the latest 1.0.4 from npmjs.com.


Scratch that, the new versions use babel to build, so I think using 
https://github.com/lijunle/babel-plugin-add-module-exports/ is the best 
option, though the latest version tagged is 1.0.2 and latest npm 
release is 1.0.4 (basically completely messed up release workflow).


--
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#990458: Bug#990458: Attaching the files from buster vs bullseye

[Pirate Praveen]

On Wed, Jun 30, 2021 at 9:30 pm, Pirate Praveen 
 wrote:



On Wed, Jun 30, 2021 at 8:27 pm, Akshay S Dinesh 
 wrote:
Either, update this plugin in Debian to the fork that's pushed only 
to npm (or switch to 
https://github.com/lijunle/babel-plugin-add-module-exports/ I guess)




I think we can take the last tagged version 1.0.0 and apply a patch 
to make it 1.0.2.


Looks like we are already using the dist tarballs and does not involve 
any build, we can just take the latest 1.0.4 from npmjs.com.


--
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#990458: Attaching the files from buster vs bullseye

[Pirate Praveen]

On Wed, Jun 30, 2021 at 8:27 pm, Akshay S Dinesh  
wrote:
This is most likely due to babel-plugin-add-module-exports being 
broken.


See 
https://github.com/59naga/babel-plugin-add-module-exports/issues/72


and 
https://github.com/59naga/babel-plugin-add-module-exports/issues/80


and 
https://github.com/59naga/babel-plugin-add-module-exports/issues/73



That 73 points to a new version that's put only on npm and not on 
github. I'm not exactly sure how it works with fakeupstream at 
https://salsa.debian.org/js-team/node-babel-plugin-add-module-exports/-/tree/master/


Either way, the version in salsa seems to be 0.2.1 which is 
definitely outdated (as per the github description of 
babel-plugin-add-module-exports



Two ways I see are:

Either, update this plugin in Debian to the fork that's pushed only 
to npm (or switch to 
https://github.com/lijunle/babel-plugin-add-module-exports/ I guess)




I think we can take the last tagged version 1.0.0 and apply a patch to 
make it 1.0.2.




OR

Try removing this plugin altogether and changing the
"export default autosize" statement in the last line of autosize.js to
"module.exports = autosize"



It looks like many packages build depend on this module and those are 
also likely broken. I opened 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990493 to track this.



I'm NOT sure whether either of these will work.


Thanks for the pointers, at least we know what is broken and what the 
fix is. We just have to figure out the best way to include it.


--
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#990493: node-babel-plugin-add-module-exports broken with babel-preset-env 7

[Pirate Praveen]

Package: node-babel-plugin-add-module-exports
Version: 0.2.1-3
Severity: grave
Justification: creates broken build output
Control: forwarded -1 
https://github.com/59naga/babel-plugin-add-module-exports/issues/73

Control: block 990458 by -1

Upstream has released a fix in major update. Since we are in freeze I'm 
not sure how to proceed here. This affects many packages.


$ reverse-depends -b node-babel-plugin-add-module-exports
Reverse-Build-Depends
* autosize.js
* node-babel-plugin-lodash
* node-colormin
* node-css-loader
* node-deep-for-each
* node-es6-promise
* node-handlebars
* node-i18next-http-backend

--
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#990458: Attaching the files from buster vs bullseye

[Pirate Praveen]

On Tue, 29 Jun 2021 23:54:30 +0530 Pirate Praveen 
 wrote:

> I can confirm libjs-autosize from buster works fine with diaspora.

So workaround is to install the buster version from snapshot.debian.org

http://snapshot.debian.org/archive/debian/20190209T090056Z/pool/main/a/autosize.js/libjs-autosize_4.0.2~dfsg1-3_all.deb

--
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#990458: Attaching the files from buster vs bullseye

[Pirate Praveen]

On Tue, 29 Jun 2021 23:54:30 +0530 Pirate Praveen 
 wrote:

> I can confirm libjs-autosize from buster works fine with diaspora.
>
> Buster version has this,
>
> (function (global, factory) {
> if (typeof define === "function" && define.amd) {
>   define(['module', 'exports'], factory);
>
> But bullseye version is missing definition for module,
>
> (function (global, factory) {
> if (typeof define === "function" && define.amd) {
>   define(["exports"], factory);

Akshay,

Any ideas about this? Basically it is a behavior change from babel 6 to 
babel 7 and we'd like to restore the babel 6 behavior.


--
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#990458: autosize build is broken (throws error is diaspora web console)

[Pirate Praveen]

Package: libjs-autosize
Severity: grave
Version: 4.0.2~dfsg1-5
Control: affects -1 ruby-rails-assets-autosize,diaspora

I think during transition to babel7 something broke.

This causes diaspora ui to break,

Uncaught ReferenceError: module is not defined
   at 
main-e074888ae8b7a9cd9ffd9335b56c44872cea8212be3599667e8dd56947c37546.js:3
   at $.fn.charCount 
(main-e074888ae8b7a9cd9ffd9335b56c44872cea8212be3599667e8dd56947c37546.js:3)
   at 
main-e074888ae8b7a9cd9ffd9335b56c44872cea8212be3599667e8dd56947c37546.js:3


This leads to,

(t((t={exports:{}}).exports),e.autosize=t.exports)}("undefined"!=typeof 
globalThis?globalThis:"undefined"!=typeof 
self?self:this,function(e){"use strict";function n(a){function e(){var 
e=window.getComputedStyle(a,null);"vertical"===e.resize?a.style.resize="none":"both"===e.resize&&(a.style.resize="horizontal"),r="content-box"===e.boxSizing?-(parseFloat(e.paddingTop)+parseFloat(e.paddingBottom)):parseFloat(e.borderTopWidth)+parseFloat(e.borderBottomWidth),isNaN(r)&&(r=0),i()}function 
o(e){var 
t=a.style.width;a.style.width="0px",a.offsetWidth,a.style.width=t,a.style.overflowY=e}function 
n(e){for(var t=[];e&& instanceof 
Element;)e.parentNode.scrollTop&({node:e.parentNode,scrollTop:e.parentNode.scrollTop}),e=e.parentNode;return 
t}function s(){var 
e,t;0!==a.scrollHeight&&(e=n(a),t=document.documentElement&,a.style.height="",a.style.height=a.scrollHeight+r+"px",l=a.clientWidth,e.forEach(function(e){e.node.scrollTop=e.scrollTop}),t&&(document.documentElement.scrollTop=t))}function 
i(){s();var 
e=Math.round(parseFloat(a.style.height)),t=window.getComputedStyle(a,null),n="content-box"===t.boxSizing?Math.round(parseFloat(t.height)):a.offsetHeight;if(nr,l,c,u,d;a&&&"TEXTAREA"===a.nodeName&&!p.has(a)&&(c=l=r=null,u=function 
u(){a.clientWidth!==l&()},d=function(t){window.removeEventListener("resize",u,!1),a.removeEventListener("input",i,!1),a.removeEventListener("keyup",i,!1),a.removeEventListener("autosize:destroy",d,!1),a.removeEventListener("autosize:update",i,!1),Object.keys(t).forEach(function(e){a.style[e]=t[e]}),p["delete"](a)}.bind(a,{height:a.style.height,resize:a.style.resize,overflowY:a.style.overflowY,overflowX:a.style.overflowX,wordWrap:a.style.wordWrap}),a.addEventListener("autosize:destroy",d,!1),"onpropertychange"in 
a&&"oninput"in 
a&("keyup",i,!1),window.addEventListener("resize",u,!1),a.addEventListener("input",i,!1),a.addEventListener("autosize:update",i,!1),a.style.overflowX="hidden",a.style.wordWrap="break-word",p.set(a,{destroy:d,update:i}),e())}function 
t(e){e=p.get(e);e&()}function 
i(e){e=p.get(e);e&()}e["default"]=void 0;var 
a,o,p="function"==typeof Map?new Map:(a=[],o=[],{has:function 
r(e){return-1o[a.indexOf(e)]},set:function 
c(e,t){-1===a.indexOf(e)&&(a.push(e),o.push(t))},"delete":function 
u(e){e=a.indexOf(e);-1m(e){return new Event(e,{bubbles:!0})};try{new 
Event("test")}catch(d){m=function m(e){var 
t=document.createEvent("Event");return t.initEvent(e,!0,!1),t}}var 
s=null;"undefined"==typeof window||"function"!=typeof 
window.getComputedStyle?((s=function s(e){return 
e}).destroy=function(e){return e},s.update=function(e){return 
e}):((s=function s(e,t){return 
e&(e.length?e:[e],function(e){return 
n(e,t)}),e}).destroy=function(e){return 
e&(e.length?e:[e],t),e},s.update=function(e){return 
e&(e.length?e:[e],i),e}),e["default"]=s,module.exports=exports["default"]}),$.fn.charCount=function(i)


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

[Pirate Praveen]

I think we don't have to wait, we can upload -2 with the changes.

On 2021, ജൂൺ 23 5:09:12 PM IST, Yadd  wrote:
>Le 23/06/2021 à 13:34, Tunji a écrit :
>> Hi, in the first packaging of memfs I did, I realized that the
>embedded
>> package (fs-monkey) was not installable, so in this update I made I
>> fixed that problem by listing fs-monkey as a component to install in
>> nodejs root directory, I update changelog with commits and version
>> number.
>> Kindly inspect if package is fit for sponsorship.
>
>Hi,
>
>first, pkg-javascript-devel@alioth-lists.debian.net and
>pkg-javascript-de...@alioth-lists.debian.org are the same list, please
>stop double send.
>
>For node-memfs, we will wait for ftpmaster acceptance, then update what
>is needed (I already fixed autopkgtest). You can push your work to
>js-team/node-memfs
>
>Cheers,
>Yadd
>
>--
>Pkg-javascript-devel mailing list
>Pkg-javascript-devel@alioth-lists.debian.net
>https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

-- 
Sent from my p≡p for Android.
-- 
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#990052: Looks like this transition is not completed

[Pirate Praveen]

Control: forwarded -1 
https://github.com/DefinitelyTyped/DefinitelyTyped/pull/44365

Seems this transition is not completed.



pEpkey.asc
Description: application/pgp-keys
-- 
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#990052: Drop @types/jest, replaced by @jest/types

[Pirate Praveen]

Package: jest
Version: 26.6.3+repack+~cs64.44.39-3
Severity: important

@types/jest is now obsolete as jest itself provides type definitions in 
@jest/types module (already shipped in the package). When using 
@types/jest, it results in error finding dependencies, for example in 
node-memfs with fs-monkey as component.


--
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#986117: take ownership and mark as pending

[Pirate Praveen]

On Tue, 1 Jun 2021 16:41:51 +0200 Paolo Greppi  
wrote:

> owner 986117 Paolo Greppi 
> tag 986117 pending

Hi Paolo,

Can you upload it?

Thanks
Praveen

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

[Pirate Praveen]

On Sat, Jun 12, 2021 at 2:54 pm, Ayoyimika Ajibade 
 wrote:

Hi there,

I have updated the node-tar  from version 6.0.5+ds1+~cs11.3.9-1 to 
6.1.0+ds1+~cs11.3.9-1 The package is available at 
https://salsa.debian.org/Ayoyimika/node-tar/ and I am requesting for 
sponsorship and I ensured all tests passes, it's lintian clean and 
also built it in a clean chroot with sbuild.Thanks



Uploaded, thanks! Btw you don't need to add 'Uploaded to experimental' 
in changelog next time. Also you can request membership in js-team 
group in salsa.

Ayoyimika Ajibade





--
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#989733: webpack: Error: Cannot find module 'array-back'

[Pirate Praveen]

Package: webpack
Version: 5.6.0+~cs6.4.0-1~exp2
Severity: serious

With webpack from experimental,

webpack --help
(node:251750) UnhandledPromiseRejectionWarning: Error: Cannot find 
module 'array-back'

Require stack:
- /usr/share/nodejs/webpack/node_modules/command-line-usage/index.js
- /usr/share/nodejs/webpack-cli/lib/groups/runHelp.js
- /usr/share/nodejs/webpack-cli/lib/utils/arg-parser.js
- /usr/share/nodejs/webpack-cli/lib/webpack-cli.js
- /usr/share/nodejs/webpack-cli/lib/bootstrap.js
- /usr/share/nodejs/webpack-cli/bin/cli.js
- /usr/share/nodejs/webpack/bin/webpack.js
   at Function.Module._resolveFilename 
(internal/modules/cjs/loader.js:815:15)

   at Function.Module._load (internal/modules/cjs/loader.js:667:27)
   at Module.require (internal/modules/cjs/loader.js:887:19)
   at require 
(/usr/share/nodejs/webpack/node_modules/v8-compile-cache/v8-compile-cache.js:159:20)
   at commandLineUsage 
(/usr/share/nodejs/webpack/node_modules/command-line-usage/index.js:12:20)
   at printHelp 
(/usr/share/nodejs/webpack-cli/lib/groups/runHelp.js:71:12)
   at outputHelp 
(/usr/share/nodejs/webpack-cli/lib/groups/runHelp.js:111:20)
   at argParser 
(/usr/share/nodejs/webpack-cli/lib/utils/arg-parser.js:45:9)

   at runCLI (/usr/share/nodejs/webpack-cli/lib/bootstrap.js:11:24)
   at Object. 
(/usr/share/nodejs/webpack-cli/bin/cli.js:24:5)
(node:251750) UnhandledPromiseRejectionWarning: Unhandled promise 
rejection. This error originated either by throwing inside of an async 
function without a catch block, or by rejecting a promise which was not 
handled with .catch(). To terminate the node process on unhandled 
promise rejection, use the CLI flag `--unhandled-rejections=strict` 
(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). 
(rejection id: 1)
(node:251750) [DEP0018] DeprecationWarning: Unhandled promise 
rejections are deprecated. In the future, promise rejections that are 
not handled will terminate the Node.js process with a non-zero exit 
code.


--
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-lru-cache

[Pirate Praveen]

On Fri, Jun 11, 2021 at 4:49 pm, Harish  
wrote:

Hi,

I've just update node-lru-cache package to a  new upstream version 
(5.1.1 ->6.0.0) , the package is available at 
:https://salsa.debian.org/Harish1/node-lru-cache   I ensured all 
tests passes, it's Lintian clean and also built it in a clean Chroot 
with Sbuild.


Please consider to review and upload it .



This is a major version update, did you test if all reverse 
dependencies still work?


$ reverse-depends node-lru-cache
Reverse-Depends
* node-cacache
* node-hosted-git-info
* node-js-beautify
* node-jsonld
* node-semver

$ reverse-depends -b node-lru-cache
Reverse-Build-Depends
* node-cacache
* node-ejs
* node-hosted-git-info
* node-js-beautify
* node-jsonld
* node-semver


Regards,

harish.




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

[Pirate Praveen]

> Hi there 
> I've just packaged a new node module, node-clipanion 2.6.2, for 
Debian
> and I wish to find a sponsor to help upload it to salsa Debian 
js-team

> repository.

> I ensured all tests passes, it's lintian clean and also built it in a
> clean chroot with sbuild.Find it 
at:https://salsa.debian.org/sonnie/node-

> clipanion

> Please note: node-clipanion requires @types/chai-as-promised which is
> provided by the new update of node-chai-as-promised at:
> https://salsa.debian.org/sonnie/node-chai-as-promised

> Kindly upload this node-chai-as-promised update also, along with the 
new

> node-clipanion package
>Regards
> Sunday

Hi Sonnie,

I uploaded both packages. Thanks for your contribution!

Cheers
Praveen



--
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] Processed: BTS housekeeping and severity adjustments

[Pirate Praveen]

On 2021, ജൂൺ 1 1:23:22 PM IST, Paolo Greppi  wrote:
>Il 31/05/21 23:33, Debian Bug Tracking System ha scritto:
>> Processing commands for cont...@bugs.debian.org:
>> 
>>> severity 986117 serious
>> Bug #986117 [yarnpkg] yarnpkg is not compatible with node-proper-lockfile 
>> 3.0.0+
>> Severity set to 'serious' from 'normal'
>> ...
>
>Hu everybody, I have drafted a patch for this issue:
>https://salsa.debian.org/js-team/node-yarnpkg/-/blob/master/debian/patches/19-proper-lockfile.diff
>
>Any comments?

If the command that failed now works, that would be a good indicator, right?

>Paolo
>

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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#988884: libsass and node-node-sass is deprecated upstream

[Pirate Praveen]

Package: libsass, node-node-sass
Severity: important

libsass and node-sass seems deprecated by upstream in favor of dart 
sass.


https://sass-lang.com/blog/libsass-is-deprecated

I was trying to package rollup-plugin-sass and noticed it is using sass 
module and not node-sass module.


I tried a simple patch to replace sass with node-sass in 
rollup-plugin-sass, but build was failing when trying to bundle it.


I will try packaging dart-sass, but I have never touched a package 
written in dart yet.


--
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#988602: Include babel-plugin-module-resolver with node-babel7

[Pirate Praveen]

Package: node-babel7
Version: 7.12.12+~cs150.141.84-6
Severity: wishlist

babel-plugin-module-resolver is a build dependency of cssnano

--
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#988559: Bug#988559: Support reading from lerna.json to find components automatically

[Pirate Praveen]

On Sat, May 15, 2021 at 8:30 pm, Yadd  wrote:

Le 15/05/2021 à 20:18, Pirate Praveen a écrit :

 Package: pkg-js-tools
 Version: 0.9.65
 Severity: wishlist

 Example module @toast-ui/editor

 Read lerna.json and install these similar to entries in
 debian/nodejs/components

 {
 "packages": ["apps/*", "plugins/*", "libs/*"],
 "version": "2.1.0"
 }


Hi,

pkg-js-tools doesn't modify debian/* files for now. Maybe this is the
job of npm2deb ?


That will work too, or pkg-js-tools could read this directly, may be 
npm2deb is better option.


--
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#988559: Support reading from lerna.json to find components automatically

[Pirate Praveen]

Package: pkg-js-tools
Version: 0.9.65
Severity: wishlist

Example module @toast-ui/editor

Read lerna.json and install these similar to entries in 
debian/nodejs/components


{
 "packages": ["apps/*", "plugins/*", "libs/*"],
 "version": "2.1.0"
}

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

[Pirate Praveen]

On Sat, May 15, 2021 at 5:33 pm, Yadd  wrote:

Le 08/05/2021 à 02:08, Sonnie Nkwuda a écrit :

 Hi there 

 I've just packaged a new node module, node-typanion 3.3.1, for 
Debian

 and I wish to find a sponsor to help me upload it to salsa Debian
 js-team repository.
 I ensured it's lintian clean and also built it in a clean chroot 
with

 sbuild.

 Find it at:  https://salsa.debian.org/sonnie/node-typanion
  .

 Regards
 Sunday Nkwuda


Hi,

looks good, thanks. Build & autopkgtest & duck & lintian are OK. Just
some few things:

 * copyright is 2020, not 2021
 * in debian/tests/pkg-js/test:

 TS_NODE_TRANSPILE_ONLY=true

   has no effect, it should be removed or fixed:

 export TS_NODE_TRANSPILE_ONLY=true

 * in debian/control:
   * test-only build-dependencies should be marked with 
 (probably mocha and chai)
   * remove pkg-js-tools dependency: double with dh-sequence-nodejs

Sorry to not have look at this earlier, I'm hospitalized.


$ rmadison node-typanion
node-typanion | 3.3.1-1   | new| source, all

I had uploaded it already, these changes can be made as version 3.3.1-2.



--
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#988507: update node-terser to alteast version 4.8

[Pirate Praveen]

Package: node-terser
Version: 4.1.2-8
Severity: wishlist
Control: block 988506 by -1

terser-webpack-plugin needs terser at least version 4.8. Is there any 
known blockers I can help with?


--
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#987967: jade replaced by pug for ages, doesn't work anymore

[Pirate Praveen]

On Sun, 2 May 2021 23:24:36 +0200 =?UTF-8?Q?Stefan_B=c3=bchler?= 
 wrote:

> Package: node-jade
> Version: 1.11.0+~cs4.1.0-1
> Severity: grave
>
> Hi,
>
> https://www.npmjs.com/package/jade says last release was 6 years ago 
and

> it got replaced by pug.
>
> Also it doesn't work anymore in bullseye for two reasons:

I think we can request removal of node-jade from bullseye and if/when 
pug is packaged, remove it from unstable as well. Since isso is not in 
bullseye this should not affect any other package.


--
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-caniuse-lite

[Pirate Praveen]

> Hi there 
> I've just updated the node-caniuse-lite package to a new upstream 
version and I wish to find a sponsor to help me

> upload this changes to the Debian node-caniuse-lite repository.
> I ensured it's lintian clean and also built it in a clean chroot 
with sbuild.
> Find the changes at: 
https://salsa.debian.org/sonnie/node-caniuse-lite

> RegardsSunday Nkwuda

I have uploaded it, thanks for your work!



--
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-to-regex-range

[Pirate Praveen]

> Hi,
> I have made some changes for the node-to-regex-range package. I have 
fixed
> the github regex tags in the debian/watch file and also made it 
lintian

> free. Please find it at
> https://salsa.debian.org/saakshi_07/node-to-regex-range

Hi Saakshi,

I have uploaded it for now, but it'd be better to wait till bullseye 
release and upload directly to unstable as we will have to reupload it 
to unstable anyway.


If there are newer upstream releases, then we can upload that to 
experimental.


Thanks
Praveen



--
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#980316: starting with clipanion

[Pirate Praveen]

On Mon, 18 Jan 2021 00:19:59 +0530 Pirate Praveen 
 wrote:

> clipanion needs @wessberg/rollup-plugin-ts as build dependency

clipanion 3 has moved to @rollup/plugin-typescript which is already 
packaged.


https://www.npmjs.com/package/clipanion?activeTab=dependencies

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