[Pkg-javascript-devel] Bug#1058552: Bug#1058552: science.js: FTBFS: SyntaxError: Error parsing /<>/package.json: Unexpected end of JSON input
Quoting James Valleroy (2024-04-04 16:13:07) > On 3/28/24 4:08 AM, Petter Reinholdtsen wrote: > > [James Valleroy 2024-02-12] > >> Here is a patch that fixes the build: > > > > Thank you. Can you explain why changing the output from package.json to > > mktemp and then moving the result to package.json will solve the build > > problem? I fail to understand how this could change anything. > > The makefile receipe uses node to produce the content that will be > written to package.json. It seems that node is also trying to read in > and parse the contents of package.json. Apparently, writing the file is > not an atomic operation, so node is reading it before the write > operation has completed. So it reads some partially-written package.json > file, which is not yet valid JSON, and produces an error when trying to > parse it. > > I don't know enough about node to say why it does this (reading in > package.json after it has started running the src/package.js script). > > > Btw, did you mean TEMPFILE=$(shell mktemp) to get a random temp file > > name? > > > > I'm not sure. It may also work, but there is a difference in when a > shell command runs. Some people recommend not to use shell in a > makefile: https://stackoverflow.com/a/76121578 Each make target (i.e. each line indended by a tab) is executed within a shell. The point in the SO answer you reference is that calling the make function $(shell ...) *inside* a make target effectively spawns a shell within another shell, and *that* you rarely really want. What Petter is talking about above is that "TEMPFILE=mktemp", because it is a make target (i.e. on a TAB-indented line) is passed to a shell, which will *not* set TEMPFILE to the output of the shell command mktemp, but simply set TEMPFILE to the _string_ "mktemp" which is unlikely that you want. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1059461: RM: node-jsonld -- ROM; depends on node-request which is broken and abandoned upstream
Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: node-jso...@packages.debian.org Control: affects -1 + src:node-jsonld -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Ftpmasters, Please drop the package node-jsonld from unstable. It is blocking another package, node-request, from being kicked altogether from Debian (see bug#956423). node-jsonld is still needed in Debian, but is currently in experimental awaiting a replacement for node-request, node-ky, which has shown problematic to package. So please drop node-jsonld from unstable (and *only* from unstable). - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmWKj+0ACgkQLHwxRsGg ASE1mQ//fgLLl+aiNb+cojVd+vHqrB0barNHP6cttNlBrQC1go8ySdxUh7dIqL+G kJ4q2v8ntT2sbQeiS07pgNGaWbPz3I/+NS+LHzv5VU7YMxMN6Pwlf0Fk8EUsYZ5E n46e8VqniX1jw+LGAy2VRz2/GrjUy+OnZ3Bmn46K9eW9eWG12TsxBsig9vgtLDzI ovzHODjkhui8yAPzvH+nCWcRMqAf79rJwhRmRwiKPtRZOwfh2mzGno8/PeujCfYP FgsaF0oLOlwN+EQgFRhOkbuVr/Ik5zmGznSbOCny7ua2MvVxJtKNal1JxP5LK+Yf WEdLEQyEp0DjOI0QmIhjsxk9JzRMESVSteInVmT5YNUpmctvB/XTAmw4tE+rnPpJ +VJ4KMPYnZVdphY2K1OcIYcQyxh3aRNYdL5m30GB7++A0Jx7kWv7fwKZDj8cwFgJ 0+CsRTOfODzH+mwwx2AjEQ0MBbOcDltLqPZLW/SxLHwm0r7dNa34pzoAsTOwj9Tr aG3H+SPOrxaWkgN7HBPs6WqOLOZeexWFcvdkE47JvYKZ4m7P8NPhTAsxsPHS1mod 2exYTcqE4UsD1MIDAHQkD5bt7UAEgt9TDvADV2g6y0C8zABCINHl3AiEG6H69ebu l4quWtX54Wo4kO7aPJvFdQVAQZhFgQNxryc84nxGLbKrGC/uqUQ= =w4Xd -END PGP 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#958682: Bug#958682: node-jsonld: Remove dependency to node-request
Quoting Jérémy Lal (2023-12-23 20:45:21) > Le sam. 23 déc. 2023 à 20:15, Jonas Smedegaard a écrit : > > > Quoting Pirate Praveen (2023-12-22 20:53:46) > > > 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. > > > > You gave a second warning. Only 24 hours but I guess I should be > > thankful. > > > Hi Jonas, > > Is there some humor in this tone ? > This bug has been opened more than three years ago, and it's starting to > look as if you wanted to block it. There was sarcasm. No, I am not trying to obstruct. I genuinely wanted to address it but forgot, and last night I began look at doing a feverish stunt before I got involved in other stuff today. Then tonight I saw that the package apparently got dropped, so assumed that someone requested kicking node-jsonld as well. ...but as I double-checked now, I see that node-jsonld is still in Debian - great. I may then still have time for avoiding a revisit to NEW queue. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#958682: node-jsonld: Remove dependency to node-request
Quoting Pirate Praveen (2023-12-22 20:53:46) > 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. You gave a second warning. Only 24 hours but I guess I should be thankful. Hm. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1057707: Bug#1057707: Bug#1057707: eslint is incompatible with node-ajv >= 8
Quoting Yadd (2023-12-08 03:55:11) > On 12/8/23 03:59, Jonas Smedegaard wrote: >> Quoting Yadd (2023-12-07 14:37:31) >>> @Jonas, do you agree if I push this to experimental ? >> >> If it succeeds the testsuite then by all means, go for it. > > sure, all test passed now. Only error strings had to be updated Great! Thanks a lot for working on this. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1057707: Bug#1057707: eslint is incompatible with node-ajv >= 8
Quoting Yadd (2023-12-07 14:37:31) > Control: tags -1 + patch > > On 12/7/23 15:52, Jérémy Lal wrote: > > > > > > Le jeu. 7 déc. 2023 à 12:45, Yadd > <mailto:y...@debian.org>> a écrit : > > > > Package: eslint > > Version: 6.4.0~dfsg+~6.1.9-7 > > Severity: important > > Tags: ftbfs upstream > > > > Hi, > > > > eslint depends on node-ajv 6 and is incompatible with node-ajv 8 > > (available in exeprimental branch). All is in lib/shared/ajv.js: > > > > - eslint requires 'ajv/lib/refs/json-schema-draft-04.json' which is no > > more available > > - eslint tries to set `ajv._opts.defaultMeta` which is > > `ajv.opts.defaultMeta` in node-ajv 8. > > > > Changing "ajv/lib/refs/json-schema-draft-04.json" to > > "ajv/lib/refs/json-schema-draft-06.json" doesn't work. I tried this > > patch which looks to work but 27 tests fail (not the good error string). > > It uses default ajv schemas. > > > > Help needed here ;-) > > > > > > I suppose you tried > > https://github.com/eslint/eslint/pull/13911/commits > > <https://github.com/eslint/eslint/pull/13911/commits> > > ? > > Thanks a lot Jérémy! Based on your suggestion, I succeed to build a patch. > > @Jonas, do you agree if I push this to experimental ? If it succeeds the testsuite then by all means, go for it. But if not, then instead please let's look in more detail at the options, to avoid complicating matters for this delicate beast. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#958682: node-jsonld: Remove dependency to node-request
Quoting Praveen Arimbrathodiyil (2023-10-29 18:10:08) > On Fri, 31 Dec 2021 13:17:07 +0100 Yadd wrote: > > updating node-jsonld is enough to fix this issue: > > Hi Jonas, > > Are you planning to update node-jsonld? > > > Else we can simply remove this package from Debian since it seems > > useless (no reverse dependencies). > > This is blocking removal of deprecated node-request. Yes, I still want to work on node-jsonld - I will make time to look at this soon... - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1054259: Bug#1054259: Bug#1054259: nodejs: cannot bootstrap nodejs
Quoting Jérémy Lal (2023-10-20 10:42:58) > Le ven. 20 oct. 2023 à 10:33, Christopher Obbard > a écrit : > > > Control: retitle -1 nodejs: cannot bootstrap nodejs > > > > Hi Jérémy, > > > > On Fri, 2023-10-20 at 02:25 +0200, Jérémy Lal wrote: > > > https://salsa.debian.org/js-team/nodejs/-/blob/master- > > > 18.x/debian/README.source > > > > Thanks for your suggestion. I actually did follow those instructions to > > attempt to build nodejs 18.13.0+dfsg1-1. > > > > For nodejs 16.15.1+dfsg-1 following those instructions bootstraps the > > package > > just fine, I think because the "externalized builtin" JS files are present > > in > > the packaging. > > > > I have attached the three patches to debian/ to get _something_ bootstrap > > for > > 18x but it still fails with the error "Cannot load externalized builtin" > > when > > trying to launch bootstrapped node. > > > > Maybe the README.source isn't clear enough. > The node package built at first stage is just good enough to build the > second stage. > It is not feature-complete. Typically you can't run node REPL with it. > Once you have first stage, you install the resulting deb, and use that as a > build-dependency > to build second stage (which is a normal build). Perhaps updating that text to point the the Debian wiki page on staged builds would be a helpful hint. (on weak internet right now, so haven't checked if that is already done) - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1051238: ITP: biome -- formatter and linter for web languages
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-de...@lists.debian.org, Debian Javascript Maintainers -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: biome Version : 1.0.0 Upstream Contact: Rome Tools is Rome Tools, Inc. * URL : https://biomejs.dev/ * License : Expat Programming Lang: Rust, Node.js Description : formatter and linter for web languages Biome formats and lints your code in a fraction of a second. . Biome supports JavaScript, TypeScript, JSON, and CSS. It aims to support all main languages of modern web development. . Biome has sane defaults and requires minimal configuration. Biome helps you as much as possible by displaying detailed and contextualized diagnostics. . Biome unifies functionality that has previously been separate tools. Building upon a shared base allows us to provide a cohesive experience for processing code, displaying errors, parallelizing work, caching, and configuration. . Biome is designed to eventually replace Babel, ESLint, webpack, Prettier, Jest, and others. This package will be maintained in the collaborative debian section of salsa, at https://salsa.debian.org/debian/biome -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmT2P20ACgkQLHwxRsGg ASEZWg//TeQDd1oBh1KOyQvlEQkq6aducgElCNp/fas9oXJt+wIbw2E5o62c74Iw 4fqYiHJp7+hwA9Ld87G0llqdokhAPsq4+bwH21x4EDoNSaWBlcBjc1V6q8g22g/b xm0cI2cQKC15MhVls+WuDKpdHeGZHqxp4F3dWoCXbmJtFK82nMkWJkXZOh3UiJ+P /dPV5mI1Y/uexZZZmww+LKdt51ma100kZbAf+P4XgQOo43zKiiguE3RSVYd5CKgv 3i5i0V5OCFeoYr1vsXL2G1G0vrNZHDygJ6V88F2VpMe/AxHShLpnhL5PaQgAEFeq scKmLpV7blYU4qDXp3im3OP9mJsetovNLhvr0b9HuLn8U3QhmJoOZ4CoydmMAoNJ Kj8crKndk+ioZa3ct15SdUjOmQCrrQ5w47VjDvlyIpx7BrKeA7jquVLC367/LcZQ H0MyMu4Gy6YvHYKXB6OvWO8GJPJo/63vVz/AJYYuR7NT3Q0C3eBKr/VW1p555Yyd k/12Qv5p+QmlN0u0vniLX3i4Ftr3sGNhcjxCVAgYqsRZyTUR1rtdRgY9Bf9qTkFC jbdUrxrUfiyuunQimUlTDbsAIykZQac5f4cHViDWiGdCv6niAJaVQOatwFHslM4B SffnPOG3kdMjZpgIwlpGhVhxLEjETlPKcfE22EsOKmPiKtkzCaE= =fldg -END PGP 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#1036863: ITP: perlnavigator -- language server (LSP) for Perl
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard X-Debbugs-Cc: debian-de...@lists.debian.org, Debian Javascript Maintainers , Debian Perl Group -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: perlnavigator Version : 0.5.5 Upstream Contact: bscan * URL : https://github.com/bscan/PerlNavigator * License : Expat Programming Lang: JavaScript, Perl Description : language server (LSP) for Perl Perl Navigator Language Server provides syntax checking, autocompletion, perlcritic, code navigation and hover for Perl. . Implemented as a Language Server in NodeJS using the Microsoft LSP libraries along with Perl doing the syntax checking and parsing. This package will be maintained collaboratively in the JavaScript team (since build framework is NodeJS), but with conventional "node-" prefix only in provided virtual package name as it is mainly an application. Cc'ing Perl team since its use relates there. It will be maintained at Salsa, here: https://salsa.debian.org/js-team/perlnavigator -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmRy+yAACgkQLHwxRsGg ASGsmhAAiDJ/2pYjjJhsUPly4nl3vracp7pIECwiq+mhVoHqbjyQc54BFm+kSznn ijDmdbpYWcSMkW5esQkAwNj6c6DFLQqDgVcDSHSPr6NJrh0yLMSBg5uveXsO11Aj a3N/uHt6Iq9m1yppS2B/yqffWfqFCn6CAWHV7Kfb+LIDniczExA0Kq5Gpk+v+/Y+ /gYj+qP0Y6dLrRt/DGVbH2dPuWiQb89EBShha3VZHE106REr4Xin5sqm0LRWvk3O TcDg/3bq1xkYcyMX3pi/mXiue1ewF2Udi3sKlHbH3NWwMF8S0TAzaNlF6ZhmKJlJ w+nRXGp83EqOrrsWRxhDh7pfWE2+y0p6PM+03Iq8eH9JDFRx8+dgUoOG6fUF6un1 Oa+i6uqCt15HHkENlf/iH8ChsIQxgaUM664AGe2MyqhTLIkaYX3VJd8WaptZ+x1h eODF4VZaS/27V4gaBMKiHnr+ugEVXQWQsxv6QmzmxedNAXdY6aeqEDFkL0PhBdL8 Fn4C3kG+I2mPnxa/GhFu/D1i/k1Xw+HLc+sDu02zBYzvxKOn3HddUvyr5UFjqN8s 7r6nPYGSbpAJs5dqYZvWPCUhqsrFmi3BGkVa6ZoFjrBln6VBWguhrGFWBmw+uZL8 hBbPgci53rA3jEgdZ8Pj/RgpExHCCBivKeYp1/sl0XrClKcQGJU= =hcck -END PGP 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#1034969: Bug#1034969: Fwd: Bug#1034969: terser: missing Breaks+Replaces for uglifyjs.terser when upgrading from bullseye
Quoting Yadd (2023-05-02 08:58:06) > For the record, unblock issue is #1035368 Looks excellent - thanks for your work on this, Yadd! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1034969: Fwd: Bug#1034969: terser: missing Breaks+Replaces for uglifyjs.terser when upgrading from bullseye
Quoting Yadd (2023-05-02 04:58:47) > a previous "unblock" was missing here: unstable version is 5.16.5-1 > while testing version is 5.16.4-1. What do you want to do, fix only this > bug with a 5.16.5-really-5.16.4-1 or a full update ? It is a bugfix release, and as such I would consider it relevant for stable, but I get exhausted just thinking about the need for "defending" changes against the release team: If you do it, you can desice if you want to try get all of it in or only a (arguably too) minimal patch. Thanks! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1034969: Fwd: Bug#1034969: terser: missing Breaks+Replaces for uglifyjs.terser when upgrading from bullseye
Thanks for the patch, Yadd - and for the bugreport, Helmut. I am quite busy elsewhere currently - if you have the time then I would appreciate if you would handle this issue. Otherwise I'll try make time for it the upcoming weekend. - Jonas Quoting Yadd (2023-04-28 05:38:56) > Hi Jonas, > > it seems that "Breaks" fields needs to be duplicated in "Replaces": > > diff --git a/debian/control b/debian/control > index 6772ac76..3d8f1174 100644 > --- a/debian/control > +++ b/debian/control > @@ -34,6 +34,9 @@ Depends: > Breaks: >uglifyjs.terser (<< 4.8.0-1~), >node-rollup-plugin-terser (<< 7.0.2+~5.0.1-3~) > +Replaces: > + uglifyjs.terser (<< 4.8.0-1~), > + node-rollup-plugin-terser (<< 7.0.2+~5.0.1-3~) > Suggests: >terser, > Multi-Arch: foreign > @@ -87,6 +90,8 @@ Recommends: >node-source-map-support, > Breaks: >uglifyjs.terser (<< 4.8.0-1~), > +Replaces: > + uglifyjs.terser (<< 4.8.0-1~), > Suggests: >node-acorn, > Multi-Arch: foreign > > Cheers, > Yadd > > Forwarded Message > Subject: [Pkg-javascript-devel] Bug#1034969: terser: missing > Breaks+Replaces for uglifyjs.terser when upgrading from bullseye > Resent-Date: Thu, 27 Apr 2023 13:11:12 + > Resent-From: Helmut Grohne > Resent-To: debian-bugs-d...@lists.debian.org > Resent-CC: Debian Javascript Maintainers > > Date: Thu, 27 Apr 2023 14:59:55 +0200 > From: Helmut Grohne > Reply-To: Helmut Grohne , 1034...@bugs.debian.org > To: sub...@bugs.debian.org > > Package: terser > Version: 5.16.4-1 > Severity: serious > Justification: dpkg unpack error > > Attempting to unpack terser/5.16.4-1 from Debian bookworm > on a minimal Debian bullseye with uglifyjs.terser/4.1.2-8 > installed, causes an unpack error from dpkg due to > /usr/share/nodejs/terser/bin/uglifyjs being contained in both packages. > > | Selecting previously unselected package terser. > | dpkg: considering deconfiguration of uglifyjs.terser, which would be > broken by installation of terser ... > | dpkg: yes, will deconfigure uglifyjs.terser (broken by terser) > | (Reading database ... 4922 files and directories currently installed.) > | Preparing to unpack ./terser_5.16.4-1_all.deb ... > | De-configuring uglifyjs.terser (4.1.2-8) ... > | Unpacking terser (5.16.4-1) ... > | dpkg: error processing archive ./terser_5.16.4-1_all.deb (--unpack): > | trying to overwrite '/usr/share/nodejs/terser/bin/uglifyjs', which is > also in package uglifyjs.terser 4.1.2-8 > | Errors were encountered while processing: > | ./terser_5.16.4-1_all.deb > > > Please ensure that terser has sufficient Breaks and Replaces declarations. > > Helmut > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private -- 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-xregexp_3.1.1+dfsg-1_amd64.changes REJECTED
Hi Israel,
Quoting Israel Galadima (2023-02-15 12:14:28)
> Would it be possible for you to give this another look?
>
> The file tools/generate-unicode.sh shows that the unicode data in
> tools/data folder were downloaded from
> https://unicode.org/Public/8.0.0/ucd/*
>
> Looking at this webpage https://www.unicode.org/copyright.html under
> section B, they define all unicode files under
> https://www.unicode.org/Public/
> as Unicode Data Files ("DATA FILES")
>
> Looking at the same webpage under section C.3, they mention that all
> Unicode Data Files ("DATA FILES") are covered by the license found here
> https://www.unicode.org/license.txt
>
> After looking at the license here https://www.unicode.org/license.txt ,
> I don't think the unicode data in tools/data folderare non-free.
What Thorsten asks is that you include the above clarification as a
"Comment:" field in the debian/copyright file.
- Jonas
--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
* Sponsorship: https://ko-fi.com/drjones
[x] quote me freely [ ] ask before reusing [ ] keep private
--
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 with node-webfont test failures on 3 arches - possibly wasm related?
Quoting Julian Gilbey (2023-02-15 08:17:52) > On Wed, Feb 15, 2023 at 12:32:54AM +0100, Jonas Smedegaard wrote: > > (I used to maintain emscripten, but have been laid off from the job > > sponsoring my work on that) > > I'm really sorry to hear that - I do hope you find another job soon > (or already have) - good luck! Thanks for your concern. It happened last spring, so arguably old news however. I didn't find other income, but chose to instead study full time, and am now aiming for getting into university, by finishing my teenage education - after 30 years sabbat. It's a crazy and great experience! :-) - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] Help with node-webfont test failures on 3 arches - possibly wasm related?
Quoting Julian Gilbey (2023-02-14 23:24:08) > I've just submitted node-webfont to ci.debian.net and had failures on > three architectures. [...] > My guess is that s390x can't handle wasm, or something like that, but > if that's not the issue, then I have no idea. This code is generated > by emscripten, so I presumed it should be able to run on all > architectures, but clearly I'm wrong! WASM _code_ is architecture agnostic, but emscripten as WASM _compiler_ contains architecture-specific code. Beware that emscripten is lacking a maintainer for some time, so any bugs there is unlikely to get fixed soon. (I used to maintain emscripten, but have been laid off from the job sponsoring my work on that) > If these two architectures (s390x and ppc64el) can't handle it because > of wasm, how can I specify that node-webfont should only be > installable on certain architectures? Is there some package I should > build-time and run-time depend on to enforce this? (node-webfont is > currently an Architecture: all package.) When your package is arch-all and you experience CI failures for tests on some exotic archs, then ask release time to ignore those tests. I have been told to do the same for Rust libraries that are arch-all but depend on other arch-any libraries failing on s390x and ppc64el. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] node-xregexp_3.1.1+dfsg-1_amd64.changes REJECTED
Quoting Yadd (2023-02-04 13:19:56) > On 2/4/23 14:00, Thorsten Alteholz wrote: > > > > Hi, > > > > sorry, but I don't see the license text of Unicode-Expat on the websites > > you mention in the comment. > > Instead I see something like: "Modification is not permitted with respect > > to this document." > > So I don't think the license of the files in tools/data/ are compatible > > with DFSG. > > > >Thorsten > > Hi, > > these files exist also in liblayout sources, example: > https://sources.debian.org/src/liblayout/0.2.10-5/resource/Blocks.txt/?hl=4#L4 > and modified version of them are included in libreoffice (see > https://codesearch.debian.net/search?q=Unicode+Character+Database) > > So if they are not free, we should drop libreoffice from Debian too. > > Upstream copyright isn't clear, on the given link you can find: > >[...] >3 Further specifications of rights and restrictions pertaining to the > use of the Unicode DATA FILES and SOFTWARE can be found in the > Unicode Data Files and Software License > <https://www.unicode.org/license.txt>. >[...] > > which points to the same text than added in node-xregexp (modified > Expat), and > >[...] >8 Modification is not permitted with respect to this document. All > copies of this document must be verbatim >[...] > > So what can we do, consider node-xregexp as free or exclude libreoffice > or maybe there is another solution? Two wrongs don't make a right: This being an issue un other packages too is not an argument that this one should be acceptable. If the licensing is considered DFSG-free, then defend that (not here in an email conversation discrete with ftpmaster, but) in a Comment field in debian/copyright file, and re-upload. If the licensing considered DFSG-nonfree, then a) for this package (if possible) repackage to exclude the nonfree files and document why they are excluded in debian/copyright, and b) for other packages containing same/similar files file severe bugreports about each case. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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 - http-server
Quoting Praveen Arimbrathodiyil (2023-01-16 18:23:35) > I have not found any other package with http-server as name (apache, > nginx, lighttpd are the most common ones, new go based one is caddy). It > is useful outside the node ecosystem as a generic http-server and > provides http-server command line. I find it a much too generic name, regardless of upstream offering a command-line interface for it. Only if a widely used command-line tool where lots of scripts in the wild would fail to work should this generic name _maybe_ be preserved. Please package it as node-http-server - and if including the command-line interface in /usr/bin or /usr/sbin then please rename that as well (but if just a sample demo script not of production quality then instead install it only below /usr/share/doc/node-http-server/examples). - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private -- 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: Bug#1026974: Cannot exclude a component from consideration using !
Quoting Julian Gilbey (2022-12-25 22:43:05) > On Mon, Dec 26, 2022 at 02:07:02AM +0530, Pirate Praveen wrote: > > > > 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. > > Ah, OK. Unfortunately it's not possible to package these two > separately for my purposes (and they are both already packaged in > Debian): node-wawoff2 requires an emscripten/WASM build of these two > C++ libraries, so it needs the source code. It is sensible to expect debhelper scripts to support ignoring some parts of a project - either because those other parts need different tools (like here) or because those parts need custom handling for other reasons. Please a bugreport against dh-nodejs. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] node-webfont (was: Re: Request to join the Debian JavaScript Maintainers group)
Quoting Julian Gilbey (2022-12-11 22:20:47) > On Sun, Dec 11, 2022 at 09:38:12PM +0100, Jonas Smedegaard wrote: > > Quoting Julian Gilbey (2022-12-11 21:04:39) > > > > > Maybe create just a node-webfont package with embedded dependencies > > > > > > That does seem like a sensible idea - I hadn't thought of doing that > > > until I read the wiki (there's a theme here!). I doubt that most of > > > the packages required by webfont would be needed by other packages. > > > > Please don't hide embedding dependencies, but install them and provide > > them as virtual packages. > > > > It is not only a matter of them being concretely needed by other > > packages *now* but also being easily able to locate them if needed > > *later* and for other reasons - e.g. security bugfixes. > > Hi Jonas, > > https://wiki.debian.org/Javascript/GroupSourcesTutorial explicitly > advises doing this. I agree with your points, so I'm a little > confused. > > I realise, though, that I don't know exactly what you mean by "install > them and provide them as virtual packages"; is it the point made in > "Step 2" on that Wiki page about adding them to d/control as Provides? > If so, then I think what is meant is: we include them all in a single > source and binary package, in this case node-webfont, but that package > should install these embedded node packages in /usr/share/nodejs/ as > normal (and not under /usr/share/nodejs/webfont) and declare Provides: > node-... for all of these dependencies. > > Have I understood correctly? Yes, we agree. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] node-webfont (was: Re: Request to join the Debian JavaScript Maintainers group)
Quoting Julian Gilbey (2022-12-11 21:04:39) > > > Maybe create just a node-webfont package with embedded dependencies > > That does seem like a sensible idea - I hadn't thought of doing that > until I read the wiki (there's a theme here!). I doubt that most of > the packages required by webfont would be needed by other packages. Please don't hide embedding dependencies, but install them and provide them as virtual packages. It is not only a matter of them being concretely needed by other packages *now* but also being easily able to locate them if needed *later* and for other reasons - e.g. security bugfixes. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] Request to join the Debian JavaScript Maintainers group
Quoting Julian Gilbey (2022-12-11 16:13:35) > On Sun, Dec 11, 2022 at 11:19:44AM +0100, Yadd wrote: > > On 11/12/2022 11:16, Debian GitLab wrote: > > > Julian Gilbey <https://salsa.debian.org/jdg> requested Developer access > > > to the Debian JavaScript Maintainers > > > <https://salsa.debian.org/groups/js-team/-/group_members> 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 Welcome aboard, Julian, > I'm just a beginner, but I'm having a look at the > fonts-materialdesignicons-webfont package and trying to update it. I recommend to not discuss specifics of a package in same thread as joining the team - that makes it more difficult to later locate e.g. by others wanting to package a similar package. Ideal is that you file am RFP bugreport, using reportbug, and when asked then put the team mailinglist as cc. Then post to that bugreport about your details of how to do the package - which then is cc'ed this list. Imagine if it turns out that your package is more suitably packaged in the fonts team, then all discussion can be included when moving to that other team to work on it there. Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1025666: Bug#1025666: Bug#1025666: Bug#1025666: Installing npm on 11.5 pulls x11
Quoting Jérémy Lal (2022-12-07 14:51:33) > Le mer. 7 déc. 2022 à 14:33, Yadd a écrit : > > > On 07/12/2022 09:30, Pierre-Gildas MILLON wrote: > Also, I remember that some dependency of npm (maybe the one that calls > xdg-open) > recommends or suggests some x11 packages, and one can inadvertently install > those, > but it was possible to not install them (by installing only dependencies). > Sorry for the lack of details, I don't remember right away the name of the > package. apt install npm libx11-data- Above command installs npm while avoiding pullng in libx11-data and anything depending on it. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1024691: Bug#1024691: eslint: Please update node-ajv dependency to version 8
Quoting Yadd (2022-11-23 11:08:46) > I prepared node-ajv 8 in experimental branch and a patch for eslint. > There are remaining problems: some "throw" tests fail because error > strings changed. Seems to me it is not just a few changed strings: This line is now spewed more than 17000 times: meta-schema not available Seems to me the patch is incomplete - but unfortunately I cannot help in more detail. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] please subscribe to our list
Quoting Joshua Nsereko (2022-10-21 06:24:33) > My bad Jonas! > I didn't even think about checking my spam. I just kept on clicking the > subscribe button recursively. > > I have now verified my account and will be receiving updates. We've probably all been in that situation at some point. :-) Welcome aboard! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] please subscribe to our list
Quoting Joshua Nsereko (2022-10-20 13:43:36) > thanks Jonas. > > I have subscribed and am awaiting the confirmation email :-) Unless you mean that you've subscribed just now, something else is wrong (i.e. try check your spam folder): The confirmation email should arrive within few minutes of your request. ...or perhaps you are waiting for another subscription: mailinglist and wiki and salsa each need separate subscription, as does each list you want to join. Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] please subscribe to our list
Hi Joshua and others new to the JavaScript team, Please subscribe to our mailinglist, here: https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel Emails posted from strangers are manually screened to limit spam, which means your posts get needlessly delayed when you are not subscribed to the list. Kind regards, and welcome to the team, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1004471: Fwd: node-terser_5.15.0-1_source.changes ACCEPTED into unstable
Quoting Yadd (2022-08-29 17:16:58) > On 29/08/2022 16:46, Jonas Smedegaard wrote: > > a) Why is patch 2001 still needed? You kept parts of if despite terser > > now being v5. Yes, testsuite fails without that patch but I don't > > understand why (suspect the cause being newer-than-expected jest). > > yes this patch should be renamed. The part I kept wasn't related to > terser 5 but something else. This seems not be related to jest (existed > before jest update). I'll search from where comes this error Thanks. Do you mean within hours, or better that I file a bugreport to track this? Don't mean to rush you (and fixing this is not urgent), just don't want to bother with a bugreport if you are as swift as commonly :-) > > b) Why do binary packages now contain file > > /usr/share/nodejs/*/pkgjs-lock.json? Bug in pkg-js-tools, perhaps? > > This files are automatically added to all package suspected to embed > copies of some other modules (ie built using webpack or rollup). We > discussed about that some months ago, it may help in case of CVE Ohh, I see it now. And I even commented on it - sorry for my failing memory! > > c) Why do testsuite for ascjs emit several errors without failing? > > Bug in pkg-js-tools, perhaps? > > Here: >+ node Xascjs/test.js >ascjs v5.0.1 - 33 tests > >true both import and export can be overwritten Ah, I was mistaken: I talk about the instances of "console.error" that can be seen e.g. at https://buildd.debian.org/status/fetch.php?pkg=node-rollup-plugin-terser=all=7.0.2%2B%7E5.0.1-3=1660820526=0 ...and I see now that it is (not ascjs testsuite failures, but) main testsuite explicitly provoking and checking a few failure modes, so it is not test failures but intended noise. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1018728: dh-nodejs: long description promotes bad control file hint
Package: dh-nodejs Version: 0.14.36 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Long description mentions control file hint X-Javascript-Built-Using. As explained by Mattia Rizzolo at Fri, 4 Feb 2022 16:47:20 + (Message-ID: ), the hint need tp ue prefix XB_ (not X-) to get included with metadata of binary packages. Please adjust (also any code that might auto-inject it) to instead use XB-Javascript-Built-Using. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmMM55wACgkQLHwxRsGg ASEwCQ//dCDpdyQ0OYRMXOy897j+4gfvCxNdjQ+yQtGPEXCOyzC9h7rYJdjIv1dA t6T4Y8yzwO0zMmzMXeBHXVM+URLjTG6ZK6BAitcr+WtRpEdWbu9z1wBBWLoiqgug Q6s7sFpVv58+AfaIuVTRhELprTF+kJfn1I5hZBWwfJ7QGTKP0FA2BAiE+q1eMg+H 22yIGEcaVJ8oVuSL0BEG7608AiXiofjK0kDYpDApAWCRBGzS14ieeD3ib5/OU/3Z emOdWHGSK8jLNMSM8T3VGxYogQwXKtJm5ZYYGHhNummNzB6QZ2hg4qakpmN1jywZ 8Mo1lHeIx57u8hbxddPZm9eX2F9QdgFnRSM3Q7wAV5Vp/zTQeImS7y1W3D+n56Ad 5zr+Pzu0kXLXI/AgaRNl6TJytIRjHQEuyYE+A0Zleae+4FJCVI3YuufPIPAT7sV/ Iqvryb1k0nL9eswRNgBAmOR7AtMKvA7oajBAVSW1dIVM/duCx+xifC2RqIqi/xN3 I+CTQBLjLwg+eDAIRy8tmG/J96K+cPdCP/HbQG+axbAaiqLns5TbRr/4vQI6oilr UaH4pShRm1xOEQynGAgBGcVINDMRI3T9a8nHnFyGs1dAiZMHPT3mp7n/NAweMwGo u8Cfp8JObpLXrR+w7bxX2vA+BWJS7AxuASmxorRJ+SUZE/XTaLg= =tfZb -END PGP 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#1004471: Fwd: node-terser_5.15.0-1_source.changes ACCEPTED into unstable
Quoting Yadd (2022-08-25 20:38:08) > could you also push node-rollup-plugin-terser ? I fixed it for terser >= > 5 (partial patch revert: 2001_*) and added a "Breaks > node-rollup-plugin-terser (<< 7.0.2+~5.0.1-3~)" in node-terser. Thanks for looking into this. I am not happy with current state of node-rollup-plugin-terser, however: a) Why is patch 2001 still needed? You kept parts of if despite terser now being v5. Yes, testsuite fails without that patch but I don't understand why (suspect the cause being newer-than-expected jest). b) Why do binary packages now contain file /usr/share/nodejs/*/pkgjs-lock.json? Bug in pkg-js-tools, perhaps? c) Why do testsuite for ascjs emit several errors without failing? Bug in pkg-js-tools, perhaps? Regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1004471: Bug#1004471: Update node-terser to latest upstream (node-terser 5)
Quoting Yadd (2022-08-25 16:35:20) > only ruby-terser is broken by terser 5 for a bad reason, upstream uses a > patched version of terser 5.14. > > I propose to upload node-terser 5 to unstable and let Ruby Team fix > their package. Thanks for the investigation - I will follow your advice :-) - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1016587: Bug#1016587: Bug#1016587: pkgjs-depends: please add option to list inverse dependency trees
Quoting Yadd (2022-08-06 08:45:30) > On 03/08/2022 18:30, Jonas Smedegaard wrote: > > Package: pkg-js-tools > > Version: 0.14.32 > > Severity: wishlist > > Tags: upstream > > > > pkgjs-depends resolves a dependency tree with the inspected package as > > root. > > > > This results in reused dependencies always being listed multiple times. > > > > I think it would be helpful to flip it around to resolve multiple trees, > > each with the "final leaf" as root and the inspected package (which > > would then be the final leaf) omitted. > > > > Please consider providing this as an option - or perhaps do it by > > default. > > > > It might also make sense to offer to output the internally computed > > graph structure (e.g. in graphviz "dot" format) to allow rendering the > > a multipgraph (which is hard to do in a console so more sensible to > > offload to other tools). > > > > - Jonas > > Hi, > > I just implemented a --graph option (0.14.33). Will see how to fix this > issue later. Thanks! Thinking some more I am not so sure that an output reversing the order is sensible after all: I suggest simply closing this bugreport, now that the other suggestion (a graph output) has been implemented. Thanks! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1016692: pkgjs-depends: please include total amount of missing dependencies
Source: pkg-js-tools Version: 0.14.32 Severity: wishlist Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Resolved data is listed as a directed graph. That's nice to get a feel of the complexity of the packaging task. Would be quite helpful as well to have the total count of missing NPM modules. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmLs+9MACgkQLHwxRsGg ASE+pRAArQoiN0NAnrGdtAUsNFxI8HCwjuKbU4Tqi9uTxII92C9X5p+kK3hsCKMn 3ZAsfIltd5cPVEMdLomGYrRPpsdWW8XNUGwZKPgGRVWwkMFvTS6gzTycxKEVaaOn RVZCU1jK2Mr2NNA2HC3pvswmG3a3pqhrTqT8F3ziLWHWf1KU38FGdlMRB04ocs7O l/wh7M0iArIh73xJcZpBVn9FNkYlUGkq2SDxZgF59ffXvV3yHcR6PDI6oZ8fA+lQ BeUxWiaLqVUYGC8fad5BAjov9kSXC+JV7KXFtPps6NUHB9ccxWpSPDlmHPjq7osi aMPbJpN6zinvXFumBMwZBXTv9RYW7vYSRFUq6613nFPBLUmy6e3HpKdl5WNtdyoJ vuHamdbTDdwFiyx5TbQ3gxnfWpJ5A/uRbBSTia3miVlYdqRx8s1Ds6eLe/Bh587o fhvupaBCbwgiTe87Bg+eCjmvnIUiEBIdZIsX+C8K8+O40TzyzjPT4mkPPgKPzIuK 56uV0j0KGYD7ZnGFKivoFL8exB3xN1IWUGuV3pmIPTjPXQ63nYNVmuY4XO3WP/wW Z2vNK7Ad02QbjBtTd0AVFZC1zj7oE/JfMLHL9ZfOUlGeHfk6AaNBVnnNzuCAeOeU uV6OejM7zMQkohTd8R+4gXFzXKdFUMLQeMaSaG1V0doD2TbLSFM= =fZKl -END PGP 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#1016691: pkgjs-depends: please include version for inspected package
Source: pkg-js-tools Version: 0.14.32 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Output of pkgjs-depends includes version for each dependency, but inspected package itself is listed without version. Please include version for the inspected package as well. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmLs+n4ACgkQLHwxRsGg ASFU4A/9HRkAlt8dXcke/+uVXv6g5PHvPsSXqYIP42Jd8X8F4q5bc3Irjln+6nbo O+iRnlaVtqHXtHoPrIR8ipC6/YfHhFoYBIOwp7nDn+SouBB9jbUMPC4ZKi/tlr18 Mu0Val+bfq9zPmo0QOK/AYaWszIuEdwNU/Bjw3kTnz+ihdloRrFfce/+5o7sFHvx y2CiJmmDycmv8mPO5hmNQx4wJV5RDqZm1PUiAfS9uO1psp2/Hckb0KklIjsRNqMT He3vZscFjpFM66ijbKwS6fK1dMdrNWrca87o2uzdfwSrrkPv3+SgYaxjP5Iq66b8 zGAX46TSlUkKkoPgpPgYWoJMdK6FmrnPR6my/ow/+Kz2Ih2Y/Zk/kjsvjn1Z/tNk WVPpQBFttkU5x7w1+Gxu97s4ZLK80iJ5OePtdQledj+DpahtmInEs9pX/Zgg+bta Ie2AUJ0QmCSYOIAC+Qxw1kr5dxlfOvt5CjqMJTx05lQYtFzRDW0TZujnrDqv2AbZ saAo+Q+2BAvvLGJNWsSvXESjcphrDzEbefox+N7UFL7qamRKyTeGRUJ1c7xCG4hQ xfmYK7zBgc8QZrZ4Is+UYTh1wwbYJ9CkPvXwUfZ578B4eE/b+GsALzdoMnBBDpJJ 6zN9wgOa6ugOJGaNJtocE8LxrKCIho64mGHq4TP4M50MWon+OBQ= =bCQi -END PGP 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#1016689: pkg-js-tools: broken manpages: Can't locate Cache/FileCache.pm in @INC
Source: pkg-js-tools Version: 0.14.32 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Installed manpages pkgjs-depends.1.gz and pkgjs-easy-to-update.1.gz contain the following: CAN'T(1) User Commands CAN'T(1) NAME Can't - pkgjs-easy-to-update DESCRIPTION Can't locate Cache/FileCache.pm in @INC (you may need to install the Cache::FileCache module) (@INC con‐ tains:lib/etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.34.0 /usr/local/share/perl/5.34.0 /usr/lib/x86_64-linux-gnu/perl5/5.34 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.34/usr/share/perl/5.34 /usr/local/lib/site_perl)at lib/De‐ bian/PkgJs/Cache.pm line 13. Can't locate Cache/FileCache.pm in @INC (you may nee.Ad.ugt.uo.stin.2s.0t.2a.2ll the Cache::FileCache module) (@INC contai.Cn.As.N:.'Tl.(i.1b.) /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.34.0 /usr/local/share/perl/5.34.0 /usr/ lib/x86_64-linux-gnu/perl5/5.34 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/ 5.34 /usr/share/perl/5.34 /usr/local/lib/site_perl) at lib/Debian/PkgJs/Cache.pm line 13. Please ensure that all libraries needed to render the manpages are available during build. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmLs8Z4ACgkQLHwxRsGg ASFOrhAAnrWgtQfHEwkeqE+G/41JIYYZ3axmUTBYBJt0Y9cClNFGHUc2+5qoKGHm YCF0XQ7nh0MxBYZOOvxz843dyR/9HyFClEABCQB0WIVBO7f0bSi07dUZ/uh0hbvH 0YjEb3wVeWuD1jboowOrpOvUvkzAsOQoMS9XVareFG0/5VwYu+c5oQcQwiwfMdjC J7zwXS1kF6wVJ62sRb5v4PgQWeVaOXUNz/gvBlgSmAOvZeZooI3Rdv9t0DuXdldW Wd1EWhVYfZIiQ1xpwImajR5MMZKALOcj4vmK4TBkdhYIRegVmp7ZHR3rKblWOFrM dwCLcwWQi8kTGu7QNF3iITuHVq/VP0klX2r5vB12Sssgzs9bUTXElEsNGWr5qzdV wDHqGRmkgytAAyjPamMHTA65QDrwSEjYp1IIvoLQ7cbZ1nkwzcI6CpqV2cR/W3FU oO2F+/Wf1MovihB6oh8wL7Hd8fuHgt68h3cczDWe/Wpf7vvlLG7PDW1ZcUIlzx9I oIAUYwjtQenkJguS2WBUGlBSdini04Hc2Av7Gxj15v1pxmhPOrtIBV5w5hJuiB68 lbmNCrFMTVe16TBKI26xcm78d9CdZQXSkLiTt2kEjDzPhO3tM9UAlwbQm5JSJiVP eIZX0C18jsMDWPJ2vkj1wjOdTMzogJ2bpRAjz84TqJEeE/v/oas= =F11R -END PGP 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#1016587: pkgjs-depends: please add option to list inverse dependency trees
Package: pkg-js-tools Version: 0.14.32 Severity: wishlist Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 pkgjs-depends resolves a dependency tree with the inspected package as root. This results in reused dependencies always being listed multiple times. I think it would be helpful to flip it around to resolve multiple trees, each with the "final leaf" as root and the inspected package (which would then be the final leaf) omitted. Please consider providing this as an option - or perhaps do it by default. It might also make sense to offer to output the internally computed graph structure (e.g. in graphviz "dot" format) to allow rendering the a multipgraph (which is hard to do in a console so more sensible to offload to other tools). - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmLqorMACgkQLHwxRsGg ASH3nQ/9E+KfSv+hRQMIarOJOYRlM4JuyBc2Es+N5U7OO03rBqncTW0bOfxYRrfJ 5gdXwHUE6gpTX5+EqI7zJPRV27S3pZUbU+tUKADk8k5NP3rpuVIXyEGitBxwXwf3 674hRbIUGgl/P0AkWpxcfi2H7hcTBJHOcBTi081xjtrr/e6psC5q659rHUpGp1Vq roHEl1/pFXRpGIZyw7F+yuWc4qT2W1aaZItkCZPFyk7LNJIDAiGkZj+CMU3YiFKC 3CZDyprSJ1RANoLRhvJKunT9f9wR6viCL5h0ZVaBZ+GIKcadXG/i0d9Cfw1ut5J1 4cG5oqooJJHnSaGcSOEMwLifU8SkOr6iEMoKIUn+tKOaRtVJeEO5FAJ+OCQyLXL2 YRTKudQHR7Yl2sg2QOD9mpP2FMvT9I+VmgSbap9beA4uX+E/N39PzjtRJt5StLdv 1cju0STxHbaTwcoc0hFiafErzunyZOG0pPd9yPoUppYMv8C4bJDFHrPsq8dR8x7a 5HnEtiHK88kjurovHguL2vO82+YMGB6SaED/JWkAqQmtJWzm6AaBNYAzTC7dLToA n56sW9J9dvIdEkMmR7xgP1kMCrm9MDg7DV2Xlw6wdSVSZ2VpnbXiBeWQwjjl2qsX VjmUIAijWtU2p2ovhelOYCCOAwOY+/OFkp5tF3d+ZAgsC54wKqU= =abM5 -END PGP 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#1016528: Bug#1016528: node-fetch: please upgrade to at least v3.2.3
Quoting Yadd (2022-08-02 17:59:47) > On 02/08/2022 13:00, Jonas Smedegaard wrote: > > Please upgrade node-fetch to at least v3.2.3, needed by several projects > > I am preparing for Debian. > > > > (yes, I am aware that there is a package in experimental - this > > bugreport is to track availability in unstable) [...] > node-fetch >= 3 seems to break node-solid-rest [1], that's why I didn't > pushed it to unstable. Since you're maintainer of node-solid-rest, could > you fix that ? Please don't let that stop upgrade of node-fetch: node-solid-rest needs to be upgraded anyway and newer releases depend on newer node-fetch (via node-rdflib not yet packaged which also needs newer node-fetch). - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1016528: node-fetch: please upgrade to at least v3.2.3
Package: node-fetch Version: 2.6.7+~2.6.1-1 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please upgrade node-fetch to at least v3.2.3, needed by several projects I am preparing for Debian. (yes, I am aware that there is a package in experimental - this bugreport is to track availability in unstable) - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmLpA6wACgkQLHwxRsGg ASGxzg/9GE3ROAVwppNJQDSvle2baV/v68kgALAB/tLvmF5ZitIQVGeRbmr2CRXG yOTZ++tv89qLg78RVLaFcTJR7W2oYbBwrAPtQSMRiS7zROjPqjlnZMe7Dx2+eDb9 eUX9rDTeKT+X7wQKuaIuMkykdTIcr2Ipvq80RWgt/icIuVQyZPEvA2QfGwDW9pBq DRftUQ7G7eL7pig9I8xv74D6toA6wD7nXdyWs8oDDqdd/s0yVyDWHyCIpQLpqNgS XvOytl1ncYNTf+MI0c69yVuo+RbXLFjWgdSym46XURZaa1Ob4GiXNhgW+u9KjWgr dMEbndHpGSRIreqWZnSTA5VllnZslN25bY8KqGjupQ0XryCbpFIvgxZPzmgxHCxP 8Fw+FyZ7/sqfGP9ONSjDb6/lq3N7zCJ603HAogRLRGboZuzBIFeqlMwt6LbrhkY2 PI+PVaUZKoe/dik13iplL6tgcvxQ/+7G5evQWoFiOAknyWUGwc9vq4J/Yav11TdR 2kSVivBMEkbKjbuEyTtZFjZ5XUUCMQZev2WuDbCsfakV3Ltlvp09bhUgX4+3tomN ujqCGmq7Zl1n/xH39Lu3u2WrhdArQUQMxYi5vfOyNNNq1IBw2zYJrN5Y+BCG/jqF D/C8lyhkyySUbltY8x0JkN18lLIYoCU9GNSece5mhVXLlxtjhg4= =TbB9 -END PGP 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#1016483: pkg-js-tools: pkgjs-depends eats all memory and dies (probably by linux OOM Killer)
Package: pkg-js-tools Version: 0.14.31 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I tries run the following command in a pristine Sid environment: pkgjs-depends @solid/community-server After hanging at 4% for 5-6 minutes, the process ate all available memory (16+ GB!) and then died (probably killed by the linux OOM Killer). - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmLn6OoACgkQLHwxRsGg ASGaPQ/+MfyPlcyU7sudQWEbeaW/wG/dFBbENcXSNsGeLu8JMFA3AzNZ+Ge0m/rx ezT2z2tF8O9gG2+80buD5clRRiHL0RYQbZkql7drY5YSSgvVXm9wZNgVevznZ9wh 0+OKjEMSakNmC6LSJ/ezaxehFFNwGZduJdlhKp67+cYlA2hiTuErPJKdO7H9nlf/ IimnjId5hml5YBrsjrtOQ00vHyXGw5i622BKAmjMDmQ4gkjtOn26r6wI6Xc32eGW lj65pqZUMpteD1KyV9n8TxSP30bpxTu9hAf3bKVNIDYv2mahJaWtQ3DowLxeJfuu TLgH8vlvR0R1kYvlvZZzISslH8huUw99GPu4sXsD700JiTEmZlYiyfnXtcYZlSaV hUwlMKpSFmNvmcSaS6cPxmoKzhBY+0rMGdi+dZE3utgBBoP08f73DYXdLy28bcyX zP89iDTMgnM7Fbo14/3tCW0szTF7k2c0OMhcpzDhDpvf2cEA6p/mCF/m9PF+h4Wv 8WfUKvCsiIgLnaHVfJ0ewCu44HlKtMWoI/OtzjEpBuawQ8udWp7WwSR+YhoLDOnM K+XVNVTJ4dfWGUnva/u4cM3ySAWdjj9gaDXhS+mQankznWr6GowdMrmoylX4pee7 AdM1xW1iVr9ZGvks5NrTbHEfm19WgwmbcC5TXhgLM5YgP6KgjNU= =3hin -END PGP 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#1011816: Bug#1004471: Update node-terser to latest upstream (node-terser 5)
[ dropping randomly one of the cross-posted bugreports ]
Quoting Yadd (2022-06-25 12:13:48)
> On 25/06/2022 12:03, Jonas Smedegaard wrote:
> > Quoting Yadd (2022-06-25 09:51:05)
> >> On 30/05/2022 13:07, Jonas Smedegaard wrote:
> > Your fixing the issues is great. The minor issue I had with it
> > was your sharing fixes for multiple issues as a single patch, making it
> > hard to follow what exactly is going on, and consequently making it hard
> > to navigate in it - i.e. adopt only some changes but not others.
> >
> > Concretely, I am not ready to move to terser v5 yet, and this RC bug
> > does *not* require bumping to terser v5. Your sharing a fix for this
> > issue that goes "first upgrade to terser v5, then patch that different
> > codebase like this..." made it hard for me to change that *one line*
> > really related to this bug:
> >
> > -+if ("ecma" in opts) {
> > ++if ("ecma" in opts && opts.ecma != undefined) {
> >
> > Let me repeat to emphasize: I truly appreciate your work triaging bugs!
> >
> > Just please consider making "atomic changes": One git commit (or patch
> > file) per semantic change - not multiple lesser-related changes lumped
> > together.
>
> Thanks, usually it seems like you prefer debdiff instead of MR, that's
> why I did this. Would you rather I make some MRs this time?
No thanks: I dislike MRs because they put the burden on the receiver to
play along with a specific model of using git indirectly via a custom
web interface (or a custom REST interface).
But the alternative to MRs is not a debdiff, but a diff.
If it takes 7 changes to fix a bug, then share that as 7 distinct
pieces, either as a git branch somewhere containing 7 commits, or as 7
unified diff patches attached to an email.
Regards,
- Jonas
--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: 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#1004471: Update node-terser to latest upstream (node-terser 5)
Quoting Yadd (2022-06-25 09:51:05)
> On 30/05/2022 13:07, Jonas Smedegaard wrote:
> > Quoting Yadd (2022-05-30 12:05:41)
> >> here is a debdiff (debian part only) to update terser to version 5.13.1.
> >> This fixes also #1011816 (FTBFS)
> >
> > Thanks!
> >
> > It seems you are sharing that patch as a proposal, as you only pushed
> > some parts of it to git.
> >
> > ...and I disagree with some minor parts of it, so that's good: I will
> > take a look at it, and when I get a better sense of it reply back here
> > in more detail which parts I disagree with.
>
> Hi Jonas,
>
> did you have some time to look at this ?
Thanks for nudging - I had actually forgotten about this, but now dusted
off and finalized my work (terser v4.8 will be in unstable shortly).
Thanks again!
Your fixing the issues is great. The minor issue I had with it
was your sharing fixes for multiple issues as a single patch, making it
hard to follow what exactly is going on, and consequently making it hard
to navigate in it - i.e. adopt only some changes but not others.
Concretely, I am not ready to move to terser v5 yet, and this RC bug
does *not* require bumping to terser v5. Your sharing a fix for this
issue that goes "first upgrade to terser v5, then patch that different
codebase like this..." made it hard for me to change that *one line*
really related to this bug:
-+if ("ecma" in opts) {
++if ("ecma" in opts && opts.ecma != undefined) {
Let me repeat to emphasize: I truly appreciate your work triaging bugs!
Just please consider making "atomic changes": One git commit (or patch
file) per semantic change - not multiple lesser-related changes lumped
together.
Kind regards,
- Jonas
--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: 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#1013411: O: matrix-hydrogen -- webapp IM client for the Matrix protocol
Package: wnpp Severity: normal X-Debbugs-Cc: Debian Javascript Maintainers , Matrix Packaging Team Control: affects -1 src:matrix-hydrogen -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I intend to orphan the matrix-hydrogen package. The package description is: Hydrogen is a minimal Matrix chat client, focused on performance, offline functionality, and broad browser support. . Hydrogen's goals are: * Work well on desktop as well as mobile browsers * UI components can be easily used in isolation * It is a standalone webapp, but can also be easily embedded into an existing website/webapp to add chat capabilities * Loading (unused) parts of the application after initial page load should be supported . Matrix is an open, federated communications protocol. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmK0FMcACgkQLHwxRsGg ASFZtBAAhhzzFGZGttZcIaTGNvyoIqIUiQ+OfgrYK0Lc1eHcmMDdDrtOmkuyl7+e rQjHiRqphX1fsGXq4sErOzjCz4qk6zCQIr71jkFdl9mrHVptSN5jpMUMgZ7Jg5By 3QC3JdnUvRujf6+OxkQNIWs8VI+h6Fyq0PsLKCY/ndcDuUCzBCmXhF6DTlvL5Rfg Zj//9/vymXhcAaTG3tBskpjWi9BQbL9xZdir4zp6nCKPlu5RQsqRm1Ie5iqTUyPY cNMal/vVCvDXiMgEIGnbRPgMXWU0xLXKy/4w1Dtl2YNXsBnx4fccUetJjPUXVB9i C1/XtVADtsZZr6hoDaEAwPVOmaPWXr/1JbA2vaNKMYNt3sCoCoo2IVF1SbQn8oDb znThZq4hYBlNMh/lm2nu0jzRA03DlrG0Hsl/8df/RY7tGeXNwOXOKUFpRyazEwhO rbI8FNY/p5TGVMuCkscPWxYrn8X5l1nk58Tp7dC1aoTydI6bMj+bqJDS69Dt1nEE OdAsogqEpw+KjQo6GP3T+aKzEWsMiqZ1Qaiwo2NXeY5oFjcoBUi+Wz/qYWxtaqnj Nxrz8zlEfQc+5j0fE7HLpicYcOTcU/hpg56E+Te8++ihiIr3RBne1Qy4ZWb3lJqu wHCAMsRgd3Ps7tbkm/L8lIqbA0WWCF25uiZbTZj/7XN6JNq3iV4= =EkdB -END PGP 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#1013374: O: emscripten -- LLVM-to-JavaScript Compiler
Package: wnpp Severity: normal X-Debbugs-Cc: Debian Javascript Maintainers , LLVM Packaging Team , Matrix Packaging Team Control: affects -1 src:emscripten -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I intend to orphan the emscripten package. The package description is: Emscripten is an LLVM to JavaScript compiler. It takes LLVM bitcode, also called LLVM IR (which can be generated from C/C++ using Clang, or any other language that can be converted into LLVM bitcode) and compiles that into JavaScript, which can be run on the web (or anywhere else JavaScript can run). . Using Emscripten, you can * Compile C and C++ code into JavaScript and run that on the web * Run code in languages like Python as well, by compiling CPython from C to JavaScript and interpreting code in that on the web . Some uses of emscripten require additional packages: * setting WASM2C requires wabt (at least release 1.0.24-2). * emcmake requires cmake. * emconfigure may require automake. * emmake requires make. * emrun option --android requires adb. * emscons requires scons. * WebIDL Binder requires python3-ply. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmK0B54ACgkQLHwxRsGg ASHi2xAAkgaYJmycJ1DaTLmEPVivxjO13BH34EtAIOjZ2BKy2LLtns92AfYD/qXu h/lQvETlEUsXH9kptV10kNLgKqGsZKUFJU06M1dzmpk7N6ez5pdEAWilsGJ3Bo0/ vkjn3L9EROQSn5YwViXe1AaaBh3afx4naeLfDiYAtBMgoMxFiOjLt+iyQ2ptj0El +DaCV78cprqUuyJhEnbSJYlvRCBSrbRVp3OInV3lAt6wrtyNZGgYPUm91Z+Xtzl1 57X8Zj+vnsceox6Fs0BBYfzLJhlj0CRNQHmNkj2WoM0dJsVMIHVFFIKrpuIj6mko 1lg3r1mg0IWKDkJL5oEuOhdJDliTWpjsBfEy++RT8hLh+Bkjzww+5tj0fOqCPSJb 0XRrkHZ3C2i4fGUoP7zeR2lmnVQDVLZk+fG4Io47SSPro5fUlhQ20wXjlLXzVBHu dKPKDWNBJ55+CTuzG8p11G/FTN0jigofxWSIYhvvyIoaATJHSol33Wg/RSlR0hEZ rnkIvDLQDrgOeyxNFxSzMUchfaG3vCrn88N8p5FN6ee8XWicweaJPYTSgQssXX7n 2kzbz4CHuzCikAxShDRjdlU4BNhOf/atBbLhvHtIX05zwvxL+D9dv27kSKlmnrTg Tb6KNuEjIqiexJcIHw7NcWWw0wStMEUt31lfP/ZJUge/n17Eaps= =3ikY -END PGP 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] Bug#1010887: eslint FTBFS and autopkgtest failure
Quoting Yadd (2022-06-10 12:15:00) > On 10/06/2022 11:07, Jonas Smedegaard wrote: > > Control: tags -1 +unreproducible > > Control: severity -1 minor > > > > Quoting Yadd (2022-06-10 10:08:54) > >> Hi, > >> > >> I'm unable to reproduce this issue, can someone confirm ? > > > > Yeah, I also cannot reproduce that specific failure now, so evidently > > the error was somewhere else. > > > > A month ago I tried to work around this bug by ripping out support for > > that optional renderer altogether, only to realize *after* fighting it > > for some time that it was instead failing with some errors indicating > > incompatibility with the newer release of Node.js. > > > > I chose to simply let it bitrot for some time to see if that _too_ was > > an error somewhere else, and apparently it was: When I try build now, > > only (yet another) single test fails, unrelated to both Node.js and > > chalk module. > > > > I am sick and tired of the messy Node.js ecosystem. > > Yes, the transition from CJS-only to the current mix generated a lot of > work. Hope the situation will be more stable now. > > I wrote some utilities to debug, part in pkg-js-tools, part in > https://salsa.debian.org/yadd/yadd-js-tools (not well documented...). > > Currently, I use porterboxes (after breaking 2 laptops...) with some > custom tools for complex bugs: > * first launch build until failure > * then install wanted dependencies (first using pkgjs-install, then > if it fails using npm/yarn --ignore-scripts) > * retest command that failed > * if succeed now, launch "reduce-nodejs". This tool will try to remove > each module in node_modules, link Debian dependencies,... > * wait a long time and do something else > * when finish, relaunch "reduce-nodejs" to see if things can be > improved > * take a look at the result (version mismatch, missing modules,...) and > try to understand the real problem > > This is the better way I found to be able to update jest, babel,... What frustrates me is (most likely very related, but) how we handle dependencies (not how to resolve dependencies). - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1010887: Bug#1010887: eslint FTBFS and autopkgtest failure
Control: tags -1 +unreproducible Control: severity -1 minor Quoting Yadd (2022-06-10 10:08:54) > Hi, > > I'm unable to reproduce this issue, can someone confirm ? Yeah, I also cannot reproduce that specific failure now, so evidently the error was somewhere else. A month ago I tried to work around this bug by ripping out support for that optional renderer altogether, only to realize *after* fighting it for some time that it was instead failing with some errors indicating incompatibility with the newer release of Node.js. I chose to simply let it bitrot for some time to see if that _too_ was an error somewhere else, and apparently it was: When I try build now, only (yet another) single test fails, unrelated to both Node.js and chalk module. I am sick and tired of the messy Node.js ecosystem. I am leaving the bug open since it evidently existed and I have no idea if there is still a bug somewhere - most likely elsewhere than in eslint since it appeared and went away with *zero* changes to eslint itself! If someone is confident that this issue is solved now, then please close this bugreport. Or if someone has a clue which other part of the insane Node.js ecosystem caused this bug then please share here, and/or reassign to that package. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1011884: Bug#1011884: coffeescript: FTBFS: /bin/sh: 1: /usr/bin/licensecheck: not found
Quoting Yadd (2022-06-02 12:39:07) > can I switch this package from cdbs to debhelper+dh-sequence-nodejs ? Please remove my name as maintainer, and maintain it however you like. ...or if you have no need for the package yourself either, then consider dropping it: I suspect ot is obsolete nowadays. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] more nodejs depending packages
Hi Paul, Quoting Paul Gevers (2022-06-02 09:42:38) > On 02-06-2022 08:54, Pirate Praveen wrote: > > Or creating libjs-d3-dsv for browser files is a better idea. > > I didn't propose this because all other node-d3-* packages follow the > node-d3-* scheme *and* there are three reverse dependencies that would > need fixing too. I can do this if you favor this, but it looks a bit > sub-optimal. The naming scheme used generally for JavaScript packages is to use "node-*" for packages targeted system-installed Node.js interpreter, and "libjs-*" for packages targeted browser-embedded JavaScript interpreter (where * is the NPM project name when used, slightly normalized). Packages that serve both roles should provide one of the package names as a virtual package. Reason it is suggested to rename here is exactly in case this particular package does *not* serve both roles: Then the proper aproach is to provide separate packages, appropriately named. ...but only if you go down the road of keeping the Node.js executables. Thanks a lot for your work on these D3 packages! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1011816: Bug#1004471: Bug#1004471: Update node-terser to latest upstream (node-terser 5)
Quoting Yadd (2022-05-31 14:48:19) > On 30/05/2022 18:24, Yadd wrote: > > On 30/05/2022 18:21, Yadd wrote: > >> On 30/05/2022 14:37, Yadd wrote: > >>> There is something broken with cjs/mjs. I'm going to fix that. > >>> > >>> Cheers, > >>> Yadd > >>> > >>> Le Lundi, Mai 30, 2022 13:07 CEST, Jonas Smedegaard > >>> a écrit: > >>>> Quoting Yadd (2022-05-30 12:05:41) > >>>>> here is a debdiff (debian part only) to update terser to version > >>>>> 5.13.1. > >>>>> This fixes also #1011816 (FTBFS) > >>>> > >>>> Thanks! > >>>> > >>>> It seems you are sharing that patch as a proposal, as you only pushed > >>>> some parts of it to git. > >>>> > >>>> ...and I disagree with some minor parts of it, so that's good: I will > >>>> take a look at it, and when I get a better sense of it reply back here > >>>> in more detail which parts I disagree with. > >> > >> Hi Jonas, > >> > >> I fixed: > >> * debdiff: diff from debian/latest (still only debian/ directory) > >> * commonjs use > >> > >> Now autopkgtest passed except pure browser test (command2): webpack > >> produces a bundle unusable for domino test, maybe for browser... > > > > "webpack produces..." => in node-source-map ["self is not defined"] > > > >> I think mocha test could be added to autopkgtest now > >> > >> Cheers, > >> Yadd > > Hi, > > all is fixed now with node-source-map 0.7.0++dfsg2+really.0.6.1-11 Thanks! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1004471: Update node-terser to latest upstream (node-terser 5)
Quoting Yadd (2022-05-30 12:05:41) > here is a debdiff (debian part only) to update terser to version 5.13.1. > This fixes also #1011816 (FTBFS) Thanks! It seems you are sharing that patch as a proposal, as you only pushed some parts of it to git. ...and I disagree with some minor parts of it, so that's good: I will take a look at it, and when I get a better sense of it reply back here in more detail which parts I disagree with. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] Outreachy Internship with Debian
Hi Michael, Quoting Michael Ikwuegbu (2022-05-24 10:23:39) > My name is Michael, and I have been accepted as an Outreachy Intern > under Debian for the May - August 2022 round. I have been contributing > to the Debian JavaScript project for more than a month now, and I am > very grateful to the team for the opportunity to intern under Debian > with my co-intern Israel. We both understand that we have a lot of > learning to do over this three month period and we are thrilled to go > through this experience. Welcome aboard! I sincerely hope you enjoy your stay here - perhaps so much that you will never leave again :-) Feel free to ask us anything. Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] Outreachy Intern Introduction
Quoting Israel Galadima (2022-05-23 09:12:35) > Hello Debian JS Team, > > My name is Israel and I've been selected as an Outreachy Intern with Debian > for the May 2022 cohort. I am glad for this opportunity to contribute to > FOSS with the Debian JS Team. I will be working on a yarn plugin with my > co-intern Michael. I'm hoping we can bring value to Debian through our > work. Nice to meet you all!!! Welcome to you both, Israel and Michael! Feel free to ask questions. Seriously: Many details in our work is pretty vague and inconsistent, and it is *helpful* to our team (not annoying!) to have someone looking at it with fresh eyes point out where the weak areas are, so we can maybe improve on it. And regardless of questions you may have, have fun! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] Proposing to upload webpack 5 to unstable
Quoting Pirate Praveen (2022-05-20 11:03:15) > > > On വെ, മേയ് 20 2022 at 07:18:41 രാവിലെ > +02:00:00 +02:00:00, Jonas Smedegaard wrote: > > Please provide more detail: > > > > Which packages fail to work with webpack 4, and how? > > > > webpack 4 itself is broken, I don't think the effort to fix webpack 4 > is really worth it as we won't be able to support in bullseye anyway > and webpack 5 was in experimental long enough. > See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011097 > > > Which packages listed as failing with webpack 5 is easy peasy to > > simply > > upgrade (without collateral damage to reverse dependencies)? > > > > Bugs were filed long time ago for all failing packages and most of them > are fixed. > https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=pkg-javascript-devel%40alioth-lists.debian.net=webpack5 > > has full list. For bigger transitions, we can't really wait for every > package to be fixed, we can only realistically give a good heads up for > people to fix things. You can see how we did not even get any notice > for openssl, we only got a bug after it was broken. But for webpack5 > all affected packages have bugs for a long time. > > > The last major upgrade of chalk has lef eslint broken, so I am *not* > > happy if you push webpack upgrade forward without properly weighing > > the collaterals! > > > I agree with this sentiment in general for breaking without sufficient > notice. But I don't think webpack 5 transition was any surprice, at > least 3 full months of outreachy work happened on the transition and > two people worked full time on it. So I don't think asking for more > time is reasonable. For the record, it is not time I ask for, only clarity. I don't try to stall unnecessarily. My point is that "current package is broken too" is not in itself an argument to move to major new upstream release. Thanks for the link to the bug in webpack4, I agree with moving to webpack5. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] Proposing to upload webpack 5 to unstable
Quoting Yadd (2022-05-20 06:28:38) > On 17/05/2022 06:38, Yadd wrote: > > On 17/05/2022 06:28, Pirate Praveen wrote: > >> > >> > >> 2022, മേയ് 12 5:41:14 PM IST, Jonas Smedegaard ൽ എഴുതി > >>> Quoting Pirate Praveen (2022-05-12 13:36:42) > >>>> Thanks for your work on webpack 5 transition as part of outreachy. Can > >>>> you share a status of how many packages still needs to be fixed? > >>> [...] > >>>> I think a majority of packages are fixed already and I think we should > >>>> upload webpack 5 to unstable now. > >>>> > >>>> If there is no objections, I propose to upload it next week. > >>> > >>> Let's first get a status and only then set a time :-) > >> > >> https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=pkg-javascript-devel%40alioth-lists.debian.net=webpack5 > >> > >> this has list of affected packages. And with webpack 4 failing with > >> openssl 3.0 I don't think we have much options to keep webpack 4 any > >> longer. > > > > Hi, > > > > yes it's time to switch to webpack 5. Some packages from this list just > > need an update (mocha for example). > > > > My opinion: push webpack 5 and related packages from experimental to > > unstable right now and then fix problems > > > > Cheers, > > Yadd > > Hi all, > > webpack 4 is ~unusable. So I think we should upload webpack 5 and then > fix remaining problems Please provide more detail: Which packages fail to work with webpack 4, and how? Which packages listed as failing with webpack 5 is easy peasy to simply upgrade (without collateral damage to reverse dependencies)? The last major upgrade of chalk has lef eslint broken, so I am *not* happy if you push webpack upgrade forward without properly weighing the collaterals! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] Proposing to upload webpack 5 to unstable
Quoting Pirate Praveen (2022-05-12 13:36:42) > Thanks for your work on webpack 5 transition as part of outreachy. Can > you share a status of how many packages still needs to be fixed? [...] > I think a majority of packages are fixed already and I think we should > upload webpack 5 to unstable now. > > If there is no objections, I propose to upload it next week. Let's first get a status and only then set a time :-) Thanks to everyone working on this, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] more nodejs depending packages
Quoting Yadd (2022-05-12 10:46:43) > On 12/05/2022 10:11, Jonas Smedegaard wrote: > > Hi Paul, > > > > Quoting Paul Gevers (2022-05-12 09:38:17) > >> As the maintainer of cacti very I'm interested in getting all those > >> node-d3-* bugs about depending on nodejs fixed. Does anybody have > >> objections if I just go ahead and upload all node-d3-* packages > >> that depend on nodejs with that dependency dropped? Obviously I'll > >> take what's currently in git as the starting point, drop the > >> dependency, update the changelog, do a trial build and then upload. > > > > Please go ahead - there should be no downside to that change. > > > > Just make sure to then add dependency for autopkgtests as needed > > (I've been bitten by that detail numerous times). > > Only for package not using "Testsuite: autopkgtest-pkg-nodejs" ;-) Touché! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] request to join the JS team
Quoting Yadd (2022-05-12 10:40:53) > Build depends on google-closure-compiler which is hard to package. If closure-compiler is not passed any advanced options, then it can be safely replaced with either uglifyjs or terser. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] more nodejs depending packages
Hi Paul, Quoting Paul Gevers (2022-05-12 09:38:17) > As the maintainer of cacti very I'm interested in getting all those > node-d3-* bugs about depending on nodejs fixed. Does anybody have > objections if I just go ahead and upload all node-d3-* packages that > depend on nodejs with that dependency dropped? Obviously I'll take > what's currently in git as the starting point, drop the dependency, > update the changelog, do a trial build and then upload. Please go ahead - there should be no downside to that change. Just make sure to then add dependency for autopkgtests as needed (I've been bitten by that detail numerous times). Thanks! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] request to join the JS team
Hi Phil, Quoting Philip Hands (2022-05-12 08:34:19) > I maintain openQA, which recently gained a dependency on (the > currently unpackaged) shepherd.js. > > I therefore need to package that, and it seems that the right way to > proceed is as part of the JS team, hence this request. > > I've already requested to join the Salsa group, and had a good look at > the wiki pages about this stuff -- is there anything else I need to > do? I have accepted your Salsa request. Welcome aboard! The wiki pages should cover the basics. I am not aware of other places for coherent material about our teamwork (but I could easily miss something - let's see if others chime in and correct me...) > BTW If I need to ask newbie questions about packaging JS pacakges, > where's the best place to do that: here, #debian-js, or somewhere > else? This is the best place to ask questions, in my opinion. Happy to "see" you here, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1010738: node-rollup-plugin-uglify: depends on node-uglify (not node-uglify-js)
Package: node-rollup-plugin-uglify Version: 6.0.4+repack1-2 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 node-rollup-plugin-uglify depends on node-uglify which provides v2 of UglifyJS. Upstream release 6.0.4 pckage.json indicates that it requires v3 of UglifyJS. Please ensure that the package depends on the correct version. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmJ4Ro0ACgkQLHwxRsGg ASEE4hAAm7oFNZVGDTmwMoC7dJUYYTE8GnR5BqM55TumbjsJGjIllKjml5Ydon0r QfXR0Kr9Wn8LN8kpEs+xqa9vmpREwM+fT+TbyBb/SR+cs/UqW4FtkFS9uDmytfds c1ZL79JcvE9+kMM03JhX6zMJEQhlVsy9Pnh8v7Kz1K73sTW0xNik56NVz/11aXo+ M//dHCyxmrxT1oLm8yQN3ARkmB4YvdM3zFXjXfHfpLubLDQwuY6fpWxd09DpjlKZ FMkqAajz0UFVnNi/YsFuXBJ7goBrABBxQmSJWzq/0b7nTSPnZd7jupwaMgGMVo9U guI+Mwpp7Jab12LiFBv+4qe2wCN8SgeGNUpyfnvrnN7pIYeZW4BwdTfIW3Dk9nUY VoUGoXiOV8KotINDQPb0zFKPPpvhvWdUW7lNpVcJyJ2inx+GEJTqsB2PofbzwOiE SeMc1KYkGP29bVCoTBXoqvE+LPZ4Yp/RJVvBerQV7rjQWOoJctmeG6FTSaVf7naJ 7ujhTx4sDA88bxDyNh4QsltubMG2MkT0R2jLIXpJtqxkEGRRAJvuwOrf6TRVrVZ/ TpuCPMHgaGDSA+gmMmXaEU5A2KsXzwF+TUJA44W1nif5qb3mMVynOJS9qYkQMPsh 0N2lXB1Ffe9kYGIflhcFYKQiJS3BwIe9lNO6Xzaix3RxqH3jMUU= =Y++U -END PGP 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] Comments regarding node-types-d3_7.1.0-1_amd64.changes
Quoting Thorsten Alteholz (2022-05-08 19:46:34) > is there any update on the status of this package? That package is now provided virtually by node-types-d3. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1010471: Bug#1010471: Bug#1010471: eslint: please move Recommends to Depends
Quoting Jérémy Lal (2022-05-02 11:59:15) > Le lun. 2 mai 2022 à 11:54, Jonas Smedegaard a écrit : > > > Quoting Jérémy Lal (2022-05-02 11:45:36) > > > I stand by saying as it is, putting those packages: > > > node-chalk > > > node-strip-ansi > > > node-text-table > > > in Recommends just breaks the default functionality of eslint. > > > > Ignoring recommends breaks systems. > > > > eslint is a build-dependency of enigmail (nothing odd about that). > When sbuild builds a package, it doesn't install recommended packages > of build-dependencies ? Correct: Build environments need recommendations explicitly declared as build-dependencies, when needed. That does not mean that the package is broken (as you wrote). - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1010471: Bug#1010471: eslint: please move Recommends to Depends
Quoting Jérémy Lal (2022-05-02 11:45:36) > I stand by saying as it is, putting those packages: > node-chalk > node-strip-ansi > node-text-table > in Recommends just breaks the default functionality of eslint. Ignoring recommends breaks systems. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1010471: Bug#1010471: eslint: please move Recommends to Depends
tags -1 wontfix Quoting Jérémy Lal (2022-05-02 09:50:54) > I was trying to fix "enigmail" FTBFS, and discovered that it was > simply missing all the packages that "eslint" recommends. > > enigmail > Build-Depends: > eslint , > node-chalk , > node-strip-ansi , > node-text-table > > Those three packages are not explicitely called by enigmail's eslintrc > config: they should just be in eslint Depends, because they are > required to make eslint work. Those are not _always_ needed for eslint, only _often_ which is the exact purpose of "Recommends. Please include those recommended packages as build-dependencies, or patch/override configuration to not use them: They are related to how eslint outputs information, and since ideally packaging should be verbose/terse depending on build flags you would want to manage such configuration anyway. I commonly add something like this near the top of the rules file: ESLINT = NO_COLOR=1 eslint JEST = jest --color=false MOCHA = NO_COLOR=1 mocha --no-timeout --no-color # normalize output with TAP where possible unless terse requested ifeq (,$(filter terse,$(DEB_BUILD_OPTIONS))) ESLINT += --format tap MOCHA += --reporter tap else ESLINT += --format unix MOCHA += --reporter dot endif ...and then call $(ESLINT)/$(JEST)/$(MOCHA) in target rules. Hope that helps, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1004244: Bug#1004244: eslint: Please update at least to version ≥ 7
Mainly waiting for eslint-plugin-jsdoc getting packaged for Debian. See https://salsa.debian.org/js-team/eslint/-/blob/debian/latest/debian/TODO For more details. Quoting Jérémy Lal (2022-05-02 10:06:06) > - v8-compile-cache, one of the missing deps, is in NEW. That sounds good, as it will provide a runtime speed boost, but it is already patched away (patch 2001 in current packaging) so not blocking upgrade to eslint v7. > - @humanwhocodes/config-array should be bundled, it's barely useful > outside eslint > - @eslint/eslintrc should be bundled: "It is ESLint-specific and not > intended for use in other programs." I will consider embedding: Have updated debian/TODO. > - node-cross-spawn is useless and can be patched away by nodejs spawn Already patched away (patch 2005 in current packaging) so not blocking upgrade to eslint v7. > - node-json-stable-stringify-without-jsonify can be patched to use > node-json-stable-stringify, i guess Already patched away (patch 2008 in current packaging) so not blocking upgrade to eslint v7. Main blocker is none of those mentioned above, however, but packaging eslint-plugin-jsdoc that I consider too big for embedding and am (slowly) preparing an independent package of. Added that detail also as initial paragraph of this post, for use as status message for the bugreport. Thanks for your investigations, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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: Package new node module node-is-error (Closes: Bug#850124)
Quoting Yadd (2022-04-28 06:26:55) > On 27/04/2022 20:58, Michael Ikwuegbu wrote: > > Hello, > > > > I have packaged the node module node-is-error version 2.2.2 (Closes: > > #850124) > > > > I am requesting sponsorship. I have made sure the package is lintian > > clean and built in a clean chroot with sbuild. > > > > I have pushed the current changes to my salsa repo: > > > > https://salsa.debian.org/mikemando/node-is-error > > > > Thank you. > > Hi, > > this is a very little package. Should be embedded where needed. No: When very little but not project-specific, it should be embedded *once* and provided as virtual package! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] icu 71.1-2 (source) into unstable -> nodejs 16 will follow
Quoting Jérémy Lal (2022-04-22 23:30:58) > Le ven. 22 avr. 2022 à 23:30, Jonas Smedegaard a écrit : > > > Quoting Jérémy Lal (2022-04-22 21:27:19) > > > Excellent news ! ICU 71 is coming to sid... meaning nodejs 16 will > > > come along soon. > > > > > > Nodejs 18 requires more work (undici -> llhttp, some wasm things > > > to work out, please help). > > > > Please (create and) reference bugreports for any issues you hope to > > recruit help. > > > Right, will do. Thanks. I cannot promise that I can help, because I honestly don't know what the issues are from the hints you threw... - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] icu 71.1-2 (source) into unstable -> nodejs 16 will follow
Quoting Jérémy Lal (2022-04-22 21:27:19) > Excellent news ! ICU 71 is coming to sid... meaning nodejs 16 will > come along soon. > > Nodejs 18 requires more work (undici -> llhttp, some wasm things to > work out, please help). Please (create and) reference bugreports for any issues you hope to recruit help. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1009233: Bug#1009233: node-d3: depends on nodejs
Quoting Jérémy Lal (2022-04-09 16:07:50) > On Sat, Apr 9, 2022 at 2:21 PM Jonas Smedegaard wrote: > > The binary package node-d3 depends on nodejs. > > > > Dependencies are directional: Packages with code that _calls_ other > > code should depend on the package providing that other code, but > > packages providing code _called_ from other code should *not* > > declare a dependency. > > > > It seems the package node-d3 contains only library code, no > > executables, and it is therefore highly unlikely that the dependency > > is needed. > > > > Concretely the depenency is painful when using the library code with > > other JavaScript interpreters, most notably loading the code int a > > web browser. > > > > Please drop the dependency unless really needed. > > > > (...and do so for all other node-d3* packages as well) > > > > node-d3 is supposed to be required from nodejs, > isn't libjs-d3 meant to be used for browsers ? A node-* package can provide a libjs-* package. Regardless of interpreters the code is usable for, it is still wrong to declare a dependency on the/an interpreter: Wrong direction! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1009233: node-d3: depends on nodejs
Package: node-d3 Version: 5.16.0-4 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The binary package node-d3 depends on nodejs. Dependencies are directional: Packages with code that _calls_ other code should depend on the package providing that other code, but packages providing code _called_ from other code should *not* declare a dependency. It seems the package node-d3 contains only library code, no executables, and it is therefore highly unlikely that the dependency is needed. Concretely the depenency is painful when using the library code with other JavaScript interpreters, most notably loading the code int a web browser. Please drop the dependency unless really needed. (...and do so for all other node-d3* packages as well) - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmJRec0ACgkQLHwxRsGg ASGcZA/+Kcq/KNkhKeGMaMduMRjdm7vjqDngrKrhdz2V2MZ9STZBZLH3JoZel1ka TaJLUbHDNaH18UI8bYHfPUXAAHODgS06kAuQdGEynkYshCH44wMxuX2vo2KZl3TJ AfG7JvtNVTg1kuUMDuh+VUOc6vFQo29lg3MA4t2vwnMBC7pa+bE6wWGKwUjOqtkM r60By3txazDcbWXoAefPftuLmth6rIoObOzcVg0J7mBlIWLH/jh7D9afNMpx2Jj7 Linu81Ky/SYs4O15Ml1Rh8VmjIyHHXGv9d4gic9t2Pvgr8G1RwPN0tbTTRJF3bVk tSqeG6WEXhJJOlFgoaliRa84COGTPiyuQLSKo0NK4OQpTRfKquENE7hlGRgJj1zY avbmNellSP52QDRCAAIpYyTOjAozXUIRTwxmty5yYjav+7SefartQTC/wRxbCamQ p7o35yEQnDE7YaMIBOmDFaaa/ZbK2RYQ76uVEd2h1BHEcCuH/EZfTB0NBsqQ5asr oVFHM+b3a+zlZ4gN0Vv4xrJRJ5DDBg3VjiIGZC+zNfWKESdqQkpUJW0MZni5LiWV a2mEBmoRrBX+RhpWWSh0BWN5aXBNY2n9ssCeQPSWv9lNWnANFFh+1aBT9GTK9YWi RhG4LFy3t1/dbkB+1/ra8WHV4LozGjdJGvY1dFO/KiG+FN5GlWo= =ylfz -END PGP 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#1007858: Bug#1007858: Bug#1007858: node-lodash: FTBFS with nodejs experimental/14.19.0
Quoting Yadd (2022-04-06 18:12:30)
> On 19/03/2022 08:38, Yadd wrote:
> > On 19/03/2022 08:11, Yadd wrote:
> >> On 17/03/2022 19:21, Jérémy Lal wrote:
> >>> Source: node-lodash
> >>> Version: 4.17.21+dfsg+~cs8.31.196.20210220-2
> >>> Severity: important
> >>> Tags: ftbfs
> >>>
> >>> This package fails to rebuild. Build log is attached.
> >>
> >> The real problem comes from uglify-js call. Build works fine with
> >> uglifyjs 2 (as required by node-locash/package.json) but fails with
> >> uglify-js 3. Here is the real error:
> >>
> >> error: JS_Parse_Error [SyntaxError]: Invalid flags supplied to
> >> RegExp constructor 'node'
> >> at JS_Parse_Error.get (eval at
> >> (/build/node-lodash-wQJpO3/node-lodash-4.17.21+dfsg+~cs8.31.198.20210220/node_modules/uglify-js/tools/node.js:18:1),
> >>
> >> :63:23)
> >> at formatError (internal/util/inspect.js:1149:38)
> >> at formatRaw (internal/util/inspect.js:919:14)
> >> at formatValue (internal/util/inspect.js:774:10)
> >> at formatProperty (internal/util/inspect.js:1660:11)
> >> at formatRaw (internal/util/inspect.js:987:9)
> >> at formatValue (internal/util/inspect.js:774:10)
> >> at inspect (internal/util/inspect.js:319:10)
> >> at formatWithOptionsInternal (internal/util/inspect.js:1979:40)
> >> at formatWithOptions (internal/util/inspect.js:1861:10) {
> >> filename: '0',
> >> line: 1,
> >> col: 0,
> >> pos: 0
> >
> > For now, I dropped internal minifier and pushed result to experimental.
> > This may break some builds: minified files have to be generated separately.
> >
> > Can someone else have a look at this ?
>
> I'm unable to reproduce this failure in an up-to-date schroot, but build
> fails in salsa CI [1], that's why I reopened this issue.
>
> [1]: https://salsa.debian.org/js-team/node-lodash/-/jobs/2648172
Maybe check if upstream has a branch or pending MR with code to upgrade
to UglifyJS v3?
If not, then maybe report the issue upstream? UglifyJS v2 is pretty
dead!
- Jonas
--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: 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#1009058: webpack: lack TypeScript types
Package: webpack Version: 4.43.0-7 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please provide @types/webpack. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmJNvgIACgkQLHwxRsGg ASHXYhAAmxd+4Wlb81AB0twyxpic6IdSbie9Rm19sRf/032qRpMpc/4H+dne0jOT hTYU9WSbPb2V0qhQK06pTvCvHti5Ltt2cR+rqN1dJKFB6RnZrq0KY0fU36F4lM7J u86mNyw8FmF09mW0xO6DhXS85DcePR8kjBdyyLDxBV7CtFMmxEPs8awrFUG9JP4a pq1qmKi0GQIGmhWlglIlqUXblrjAw/gISGQW/5Rv6kYrkWa1rBrjqOhc9VnZ8T3r 5tsNHdfUnCunOgUrb9bdp45sU8GWXTiI7DNaHo37HxdUVZvJjQLyqaMEhMOZmXER xf33Qc9E7cLR2IFX/BWee3/YaneLpuhFC/iAiGXPF5l2w4BS4ShjgpYbEHoC4N16 sL/BcMJ+QMpxdGzVpGt56ddE5FNPk7JPDe8axF7RmL2EiibAPq7nC+x+wjbkvJFC PhudXskJ8T6ezOrJBx8bjeS8sQsPT0R6kYaLclB+zrcnjMzTk8BVK1wdBLJKP0G5 UgVUsFel0rghY5s83szZO1cPctpzNCBCizavP9uw6G//Rzx0AHwI+n4uLasbKpDt QDay0SgAtMv6RclU93mQD1hWBIE4jQ4mFIYr//cjSJWXSWhfQ+W+R7V42imX+I4i TO4tIqE/uzh4iDkFG2BbYgBq9BO0/0O6xQ3vpEVq4nlYhwRrEEw= =8GNm -END PGP 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] Update node-vue-style-loader package
Quoting Pirate Praveen (2022-04-01 13:18:11) > > > On വ്യാ, മാർ 31 2022 at 11:22:22 രാവിലെ +0100 > +0100, Michael Ikwuegbu wrote: > > I have updated the package node-vue-style-loader from version > > (4.1.2 —> 4.1.3). > > > > I am requesting for sponsorship. I have made sure the package is > > Lintian clean and built it in a clean chroot with sbuild. > > I have pushed the current changes to my salsa repository: > > https://salsa.debian.org/mikemando/node-vue-style-loader > > > > The package is available at: > > https://salsa.debian.org/js-team/node-vue-style-loader > > > > We should follow the years mentioned in license files > > https://salsa.debian.org/mikemando/node-vue-style-loader/-/commit/4384975bd7f875a4312104d61ae0f885664f3602 > > We don't need to update year if upstream has not updated it. So just > keep it 2017 or if you really wanted, you could say 2017-2022. Year in > copyright indicates the time when it was created or modified. > > For files in debian directry we may update it, but not really > required. If at all you wanted to update, you can add your name for > 2022 and keep the previous line the same. I agree with the final suggestion, but feel that the previous remarks are misleading: Copyright notices are messages from the copyright holders to users, and we should only communicate that message, not alter it! When you write or update the debian/copyright file, then you act as "secretary" for the owners of the project - only for files in the debian/ directory that you created or changed yourself should you decide on your own which years are correct. For all other notices (also those of fellow Debian maintainers) you should only update to mirror facts already stated elsewhere in the project. If you feel the need to extend or correct some statements, then add a Comment: field describing how/why your information is different - e.g. "No license was stated in the project, but is assumed to be the same as https://example.com/foobar that is licensed as blabla-2.0". Please also note that copyright years reflect when [original] change is introduced (i.e. time of innovation, not time of every change, and not time of release). [original]: https://en.wikipedia.org/wiki/Copyright#Originality Generally the copyright holder decides which changes should be considered "original". Because nowadays copyright [registration] is automatic and main purpose of copyright [notices] have shifted to be a reminder to users that "I made something here, so if you want to negotiate licensing you should get in touch with me". [registration]: https://en.wikipedia.org/wiki/Copyright#Registration [notices]: https://en.wikipedia.org/wiki/Copyright_notice#Reasons_to_include_an_optional_copyright_notice - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1008662: Bug#1008662: node-is-wsl: Seems useless in Debian
Quoting Yadd (2022-03-30 12:06:05) > Source: node-is-wsl > Version: 2.2.0-2 > Severity: important > > Hi, > > node-is-wsl checks if the process is running inside "Windows Subsystem > for Linux". I think it is useless here, packages using it should be > patched with a "false" value. Am I wrong? Well, Debian is the Universal Operating System, not just a Linux OS. Is it a problem to have the package in Debian? What kind of reverse dependencies does it have (now and potentially)? - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] Updating node-typescript to 4.6.3
Quoting julien.pu...@gmail.com (2022-03-26 20:42:45) > Le vendredi 25 mars 2022 à 23:22 +0530, Pirate Praveen a écrit : > > > > > > 2022, മാർച്ച് 25 9:21:03 PM IST, julien.pu...@gmail.comൽ എഴുതി > > > I prepared the package and uploaded it to experimental: I know by > > > experience that an update from 4.5.4 to 4.6.3 has a very high > > > chance to break things. > > > > > > If I'm mistaken and it doesn't bring pain all around, I'll upload > > > to unstable in two weeks. If I'm right, well, here's a nice thread > > > start to notify and discuss. > > > > Please rebuild the reverse build dependencies using a tool like > > ratt, salsa ci script created by Jeremy or > > salsa.debian.org/ruby-team/meta script. > > I did t by hand: Great. [ breakage details snipped ] Now please file proper bugreports against each failing package! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] New JS team mailing list?
Quoting Nilesh Patra (2022-03-25 21:54:13) > On 3/26/22 12:56 AM, Jonas Smedegaard wrote: > > Ok. I am then still in the dark about your point of suggesting me > > in particular for moving this forward. > > I was (a few mails earlier), hoping that you might administer the new > list, if we happen to get it. > (And no, this does not mean that you'd engage in filtering spam, > although it only takes a couple of clicks usually) Makes sense. Thanks for clarifying. > > Not sure why you cc'ed me that followup to the bugreport, > > Well, since we just had 'a thread of conversation' about it, and you > pointed me to a HOWTO, I thought I'd keep you in loop(?). No motive > here other than that. Makes sense as well now. Thanks! > I think at this point all discussion is done. So let's end the > conversation here, shall we. Agreed. :-) - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] New JS team mailing list?
Quoting Nilesh Patra (2022-03-25 19:11:32) > On 3/25/22 10:58 PM, Jonas Smedegaard wrote: > >>> I recommend that you report that issue to the mailinglist admins: > >>> The footer of https://alioth-lists.debian.net/ lists > >>> https://salsa.debian.org/alioth-lists-team/support as their > >>> preferred place to report issues. > >> > >> I think it is already known for quite sometime. IIRC bugs.d.o and > >> alioth lists use similar mechanisms for mails. > > > > Ah, you mean the SPF issue, affecting domains outside debian.org. > > > > Yes, I am aware of that issue, and there is no need to report it, as > > there is nothing really to be done about it: It works as intended by > > design (and design of SPF is limited). > > No, not SPF, I mean DKIM[1] > it is not a policy framework, but rather a signature (not GPG) on your > mail validating it to be sent from your domain. > Unlike SPF, it is more robust by design. You need not sell DKIM to me. I believe issue for SPF and DKIM is same: Debian administrators administrate only services tied to the debian.org domain (and _delegation_ of services tied to debian.net). If you want to debunk that point of mine as well, then I recommend you do it at the bugreport you referenced earlier, because I am not a postmaster nor a listmaster in Debian and convincing me that some mechanism will work great is not gonna change anything. > >> Since you moderate this list, I thought it would be nice if you > >> would be nice if you could also moderate lists.d.o, as current > >> maintainer it would be easier to collaborate with list admins (just > >> a thought, not a strong opinion) > > > > I don't think I will engage in screening for spam at lists.d.o. > > Sure, that wasn't the point of my mail either :) Ok. I am then still in the dark about your point of suggesting me in particular for moving this forward. Maybe you have noticed by now that I have a hard time understanding what it is you are trying to point out. In some cases I only point out my failure but at other times I try guess. Possibly that is me being daft, but regardless it is helpful if you try clarify, and it certainly isn't helpful to simply inform me that I got it wrong. > > I don't see at https://www.debian.org/MailingLists/HOWTO_start_list > > that my status as DD should have any special relevancy for creating > > a new list for our team. > > What is needed is clear and accurate facts passed to listmasters > > when requesting - as documented very detailed. > > I am a DD myself. > So should there be such reqs, I possibly should be able to handle > that. > I just replied to the bug with the information that listmasters need, > with you in CC. > > Will see if it gets processed. Not sure why you cc'ed me that followup to the bugreport, but am not in the mood for guessing as to your motives, so just informing you that again I am clueless. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] New JS team mailing list?
Quoting Nilesh Patra (2022-03-25 17:55:33) > On 3/25/22 9:09 PM, Jonas Smedegaard wrote: > >> I actively want us to change. As the signal to noise ratio is > >> lowered due to tons of processing emails (and it is not only -my- > >> opinion) > > > > I guess that by "processing emails" you mean those emails sent from > > Debian infrastructure to the Maintainer email address. > > yes, things like "Processing of xxx_sourceonly.changes" Or bug > processing mails from BTS (like processing tags) > > > Do you mean that you want an _additional_ mailinglist which is > > _separate_ from the address used in package Maintainer field? > > > E.g. a -discuss list? > > Yes, as an example we have > "debian-med-packag...@alioth-lists.debian.net" as maintainer address, > and "debian-...@lists.debian.org" for discussions. > > Several teams have similar schemes. > Those without a alioth list use tracker+@debian.org as maint > address so as to reduce noise. Hope that helps clarify what I meant to > say. Yes, understand you now. Thanks for your patience. > >> Also, alioth lists (like the current one) break DKIM signatures and > >> is a sort of a bummer since I see valid mails get to my spam folder > >> sometimes. > > > > I was unaware that the Alioth list was broken. > > > > I recommend that you report that issue to the mailinglist admins: > > The footer of https://alioth-lists.debian.net/ lists > > https://salsa.debian.org/alioth-lists-team/support as their > > preferred place to report issues. > > I think it is already known for quite sometime. IIRC bugs.d.o and > alioth lists use similar mechanisms for mails. Ah, you mean the SPF issue, affecting domains outside debian.org. Yes, I am aware of that issue, and there is no need to report it, as there is nothing really to be done about it: It works as intended by design (and design of SPF is limited). > >> But please note that there is already a bug for lists.d.o for a JS > >> team mailing list here[1] it has been a long time since, though. > > > > Ah, right. I vaguely rmember us discussing mailinglist structure in the > > past, but I do not remember what was the conclusion of that discussion, > > and it is not clear to me from that bugreport either. > > Thread starts from here[3] > Conclusion was to start with it if no-one objected; and IIRC, no-one raised > any objections. > > [3]: > https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2019-December/037619.html Thanks! > >> Since you moderate this list, it would make a lot of sense if you > >> could follow up there and do the needful with respect to the > >> procedure. > >> > >> [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946979 > > > > Sorry, I fail to see how my role as moderator for the current Alioth > > list makes me any special regarding setup of additional lists - at > > alioth-lists.d.n or at lists.d.o. > > Since you moderate this list, I thought it would be nice if you would > be nice if you could also moderate lists.d.o, as current maintainer it > would be easier to collaborate with list admins (just a thought, not a > strong opinion) I am not listmaster anywhere related to Debian (only on systems I host myself). I am moderator for 13 lists at alioth-lists.d.n which is efficient for me since they all use mailman where I can comfortably do screening with the command-line tool listadmin. Spam processing for lists.d.o is radically different, as documented at https://wiki.debian.org/Teams/ListMaster/ListArchiveSpam and (more brief but official) at https://lists.debian.org/archive-spam-removals/review/ I don't think I will engage in screening for spam at lists.d.o. I don't see at https://www.debian.org/MailingLists/HOWTO_start_list that my status as DD should have any special relevancy for creating a new list for our team. What is needed is clear and accurate facts passed to listmasters when requesting - as documented very detailed. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] New JS team mailing list?
Quoting Nilesh Patra (2022-03-25 15:59:51) > On 3/25/22 8:09 PM, Jonas Smedegaard wrote: > > Everyone *are* allowed to post, we actively *chose* sensoring, and I > > *volunteer* to screen it to avoid spam on the list. > > ACK. > > > If you disagree and think that we should permit spam on our lists, > > then that is a different topic than that of my post, and it is not > > entirely clear to me if you simply misunderstood me or you actively > > want us to change. > > I actively want us to change. As the signal to noise ratio is lowered > due to tons of processing emails (and it is not only -my- opinion) Reduction of "processing emails" is unrelated to sensoring (if I understand you correctly). I guess that by "processing emails" you mean those emails sent from Debian infrastructure to the Maintainer email address. Do you mean that you want an _additional_ mailinglist which is _separate_ from the address used in package Maintainer field? E.g. a -discuss list? > Also, alioth lists (like the current one) break DKIM signatures and is > a sort of a bummer since I see valid mails get to my spam folder > sometimes. I was unaware that the Alioth list was broken. I recommend that you report that issue to the mailinglist admins: The footer of https://alioth-lists.debian.net/ lists https://salsa.debian.org/alioth-lists-team/support as their preferred place to report issues. > > Please if you want to change our mailinglist handling then > > (preferably as a new separate thread) state your proposal > > explicitly, and let's discuss that. > > Hope this serves the purpose. Yes. Thanks :-) > But please note that there is already a bug for lists.d.o for a JS > team mailing list here[1] it has been a long time since, though. Ah, right. I vaguely rmember us discussing mailinglist structure in the past, but I do not remember what was the conclusion of that discussion, and it is not clear to me from that bugreport either. > Since you moderate this list, it would make a lot of sense if you > could follow up there and do the needful with respect to the > procedure. > > [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946979 Sorry, I fail to see how my role as moderator for the current Alioth list makes me any special regarding setup of additional lists - at alioth-lists.d.n or at lists.d.o. Given my lack of understanding of both what exactly you want here and what was requested in the bugreport, I don't think I am the best to follow up. I am open to changes to mailinglists, for the record. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] Fwd: q2-composition - removed vega* from source tree
Quoting Nilesh Patra (2022-03-25 15:23:05) > On 3/25/22 6:55 PM, Jonas Smedegaard wrote: > > Quoting Nilesh Patra (2022-03-25 13:37:29) > >> Your message did not reach the js-team mailing list, hence > >> forwarding. > > > > This mailinglist is sensored - i.e. posts from people not subscribed > > gets held back and is manually screened for spam. > > > > Therefore, please give it some time before reposting. > > This is another good reason to move to lists.d.o instead. Less > processing emails, posting allowed by everyone :) Seems we are talking past each other here. Everyone *are* allowed to post, we actively *chose* sensoring, and I *volunteer* to screen it to avoid spam on the list. If you disagree and think that we should permit spam on our lists, then that is a different topic than that of my post, and it is not entirely clear to me if you simply misunderstood me or you actively want us to change. Please if you want to change our mailinglist handling then (preferably as a new separate thread) state your proposal explicitly, and let's discuss that. Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] Fwd: q2-composition - removed vega* from source tree
Quoting Nilesh Patra (2022-03-25 13:37:29) > Your message did not reach the js-team mailing list, hence forwarding. This mailinglist is sensored - i.e. posts from people not subscribed gets held back and is manually screened for spam. Therefore, please give it some time before reposting. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#994245: Bug#994245: nodejs: improve bootstraping nodejs
Quoting Jérémy Lal (2022-03-24 01:05:36) > (please avoid top-posting, it makes the discussion hard to read > for newcomers - my reply is at the bottom) Please also quote only relevant parts - we all received the previous posts in the thread, so no need to quote everything repeatedly. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1008141: Bug#1008141: Bug#1008141: FTBFS: unable to use iconv with nodejs >= 14
Quoting Yadd (2022-03-23 09:44:42) > Similar error found with node-sqlite3: Please mark the bugreport with "affects" in posts like the above. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1007267: Bug#1007267: (no subject)
Quoting Ayoyimika Ajibade (2022-03-20 18:51:35) > The new update to webpack5 release > https://salsa.debian.org/Ayoyimika/node-webpack/-/commit/758a0d0bdb2001400d73db53c5a3ce3c73086b7a > > which is basically updating how webpack5 requires node-eslint-scope > resolves this bugs. > I guess i will close it then Yes, makes good sense to simply close this bugreport. Thanks, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1007267: (no subject)
Control: forwarded -1 https://github.com/eslint/eslint-scope/pull/90 Quoting Ayoyimika Ajibade (2022-03-18 08:02:40) > I created a patch https://salsa.debian.org/Ayoyimika/node-eslint-scope > and sent PR https://github.com/eslint/eslint-scope/pull/90 for this > bug and the response from upstream shows that they have dedicated API > they intend to expose, by default all classes are exposed, webpack5 > just needs to update how they are referenced. Thanks for reporting it upstream. Tagging this bugreport accordingly. Unfortunately it seems upstream rejected your proposed patch, seemingly by same argument that I provided (but hopefully phrased more meaningfully than I was able to do - if not then I encourage you to kindly ask upstream to clarify further). Also, if I am not mistaken, then Yadd has already proposed (or already applied?) a patch to webpack that addresses this, the way eslint-scope upstream and I suggested. Regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1007267: Bug#1007267: node-eslint-scope: FTBFS while updating with webpack5: Error: Invalid webpack options
[ adding back bugreport as email recipient ] Ayoyimika, please beware that this conversation is held via a bugreport. Please do not reply only to me, but send your reply also to the bugreport. Quoting Ayoyimika Ajibade (2022-03-15 15:19:40) > pls what is ABI? Application Binary Interface - i.e. the interface offered by a code project for runtime use: https://en.wikipedia.org/wiki/Application_binary_interface Your patch changes that interface - see NodeJS documentation here: https://nodejs.org/api/packages.html#main-entry-point-export Specifically, NodeJS documentation says this: > This encapsulation of exports provides more reliable guarantees about > package interfaces for tools and when handling semver upgrades for a > package. Apparently, the authors of eslint-scope chose to treat referencer.js as a _private_ library. Maybe they did that for a good reason. > waiting for upstream to patch node-eslint-scope to expose the > directory in the package.json export fields may take some time and > almost all webpack5 reverse dependencies are failing because of that. We want code that is _maintainable_ for several years. If you want quick dirty hacks then apply those hacks at the _receiving_ end - i.e. by hardcoding path to the private library file in webpack or axios or whereever exactly it is (wrongly!) expected. > i think exposing a directory shouldn't be causing any breaking changes. > here is the patch I will be forwarding upstream: > https://salsa.debian.org/Ayoyimika/node-eslint-scope/-/commit/b696752c23863d7c98fabcd3da52fcdb945da2b8.patch Please share that with upstream, so that we can learn their opinion on the matter. We don't need to wait for them to issue a new release, maybe their response in the bugreport is enough to convince us. > >Where did you ask those questions? > >On our IRC channel? At our mailinglist? In a bugreport? > i asked the question via Matrix Ah, ok. Our chat channels/rooms are mostly for casual conversation - if you don't get a response there, then try post an email to our mailinglist. Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1007267: Bug#1007267: node-eslint-scope: FTBFS while updating with webpack5: Error: Invalid webpack options
[ re-sent with bugreport added back as recipient ] Quoting Ayoyimika Ajibade (2022-03-15 14:33:21) > >Do you understand what that change does, more specifically? > What is by default is that node-eslint-scope explicitly exports some > files, while excluding example is the lib/referencer.js file which is > required in webpack5 hence, this error from CI > https://salsa.debian.org/Ayoyimika/node-axios/-/jobs/2563777 that is > the problem. the patch is to add the excluded file > https://salsa.debian.org/Ayoyimika/node-eslint-scope/-/commit/feaf8a8ffb7a1b4794d04323b5e265ce058494a0.patch > > >Is it backwards compatible? What is the risk of breaking something? > Its doesn't break anything and its backward compatible with webpack5 > > what I will do Is re-update node-eslint-scope based on the newly > released package to include the patch and forward the patch upstream Please propose a patch upstream *without* releasing to Debian yet. It seems to me that upstream provided a limited ABI and that axios or webpack is accessing parts of eslint-scope code that is *not* exposed as part of that ABI. Possibly upstream has a good reason for limiting the ABI, and a better fix for this issue is to patch axios or webpack to only use the public ABI. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1007267: Bug#1007267: node-eslint-scope: FTBFS while updating with webpack5: Error: Invalid webpack options
[ Re-added bugreport as email recipient ] Quoting Ayoyimika Ajibade (2022-03-15 11:26:28) > >Uhm, I am confused here. Are you aware that upstream version 7.1.1 > >is in Debian unstable since February 28th? > > You are right, I verified that with (apt policy node-eslint-scope) > but until yesterday or today the gitlab repo was in version 5.1.1, Beware that Debian is not (the "Salsa" instance of) Gitlab! Salsa is a helper tool, but if Debian and Salsa is not in sync then Debian is what counts. Fine that you use Salsa if that is more convenient for you, but then try limit confusion by comparing with officially released package when you file bugreports - because Debian bugreports tracks the officially released packages, not Salsa. My point here is *not* that you should repeat Salsa tests with official packages - just that it is confusing if you assume that NPM and Salsa and Debian are in sync. A good place to get an overview of official Debian releases for a package is tracker.debian.org - e.g. https://tracker.debian.org/pkg/node-eslint-scope > I asked questions didn't get a response, Where did you ask those questions? On our IRC channel? At our mailinglist? In a bugreport? If you used one of those channels, then I am sorry that I missed it, and I would appreciate if you could tell me more details - e.g. time and place - so I can try investigate why I failed to see it. Please beware that if you used Salsa for conversations, then it might work fine if those you want to reach also use that, but Salsa is an *optional* set of tools and the JavaScript team (same as most teams in Debian) only generally use IRC and mailinglists and official Debian bugreports. > so I decided to update it as it was failing most reverse dependencies > of webpack5(hence the confusion, smiles), and no the new update made > didn't solve the problem > > here is an example of the prevalent error message from CI log > https://salsa.debian.org/Ayoyimika/node-axios/-/jobs/2563777 > webpack5 depends on node-eslint-scope so both webpack and > node-eslint-scope needs to be patched to fix the error > > here is webpack patch: > https://salsa.debian.org/Ayoyimika/node-webpack/-/commit/1b33b3505358ba411be0a1188cbcf5fe24b879fb.patch > here is eslint-scope patch: > https://salsa.debian.org/Ayoyimika/node-eslint-scope/-/commit/feaf8a8ffb7a1b4794d04323b5e265ce058494a0.patch Ah right, looking at that last patch above, that is clearly unrelated to the fix released earlier today. Do you understand what that change does, more specifically? Is it backwards compatible? What is the risk of breaking something? I am hesitant to change this, and would prefer to either understand it better, or (much better) that you report this issue upstream to the developers of eslint-scope and we have their opinion on the matter. Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1007267: Bug#1007267: node-eslint-scope: FTBFS while updating with webpack5: Error: Invalid webpack options
Hi Ayoyimika, Quoting Ayoyimika Ajibade (2022-03-15 08:20:26) > Source: node-eslint-scope > Version: 7.1.1 [...] > dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned > exit code 2 The version number you report is an upstream version, not a Debian package version, and I don't recognize the test failing as being the test from the Debian package. If you are bypassing official Debian packaging then please state that clearly (and sorry if you did and I simply missed it). If you are using official Debian package, then please use the Debian version number. > so i decided to fix the error and also update node-eslint-scope, While > updating node-eslint-scope from version 5.1.1 to 7.1.1 Uhm, I am confused here. Are you aware that upstream version 7.1.1 is in Debian unstable since February 28th? Also, Yadd fixed a bug in the autopkgtest causing two tests to fail, and I issued another release today with that fix. Perhaps that addresses the issue you are reporting here? I have only read your bugreport briefly: I have difficulty making sense of it - there seems to be a lot of debug output and little context, and the context I noticed was confusing to me, as mentioned above. :-( Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] pkg-js-tools news
Quoting Yadd (2022-03-14 18:02:11) > On 14/03/2022 17:49, Jonas Smedegaard wrote: > > Quoting Yadd (2022-03-14 15:45:23) > >> Le Lundi, Mars 14, 2022 15:07 CET, Jonas Smedegaard > >> a écrit: > >>> Quoting Yadd (2022-03-14 08:41:44) > >>>> pkg-js-tools 0.13.0 improve pkgjs-depends and add a new > >>>> dh_nodejs_autodocs tool (to automatically install components > >>>> documentation: @rouca, this is for you ;-)) > >>>> > >>>> Here is the result of new "-c" option (display mismatch versions) > >>>> > >>>> $ pkgjs-depends -c ava > >>> > >>> Using option -c requires apt-file. This should probably grow a > >>> Recommends: for the package, or at least a Suggests: and a notice > >>> in long description. > >>> > >>> That option -c fails unless mismatching packages are installed. > >> > >> It shouldn't, could you share some logs ? > > > > On a clean chroot, with pkg-js-tools installed (and its > > recommendations - i.e. *not* a broken system): > > > > root@auryn:/# pkgjs-depends -c ava > > [...] > > Unable to check versions, did you install node-semver ? > > > > After installing node-semver: > > > > # pkgjs-depends ava > > Can't exec "npm": No such file or directory at /usr/share/perl5/Dpkg/IPC.pm > > line 311. > > [...] > > After installing npm (and it shitload of dependencies/recommendations): > > > > # pkgjs-depends ava > > # ava@4.1.0Can't exec "apt-file": No such file or directory at > > /usr/share/perl5/Dpkg/IPC.pm line 311. > > [...] > > - Jonas > > I think the best here is to split pkg-js-tools into: > * dh-nodejs with minimal dependencies (just nodejs:any and > needed Perl libs) => provides dh-sequence-nodejs > * pkg-js-tools with: > + suggested dependencies upgraded to required/recommended > + a dependency to dh-nodejs > > Utilities that doesn't not add any dependency will stay on dh-nodejs > (pkgjs-ln, pkgjs-utils,...) because they are used in some > debian/rules; advanced tools like pkgjs-depends, pkgjs-ls, > add-node-component will move to new pkg-js-tools > > Then no regressions (most of package depends on dh-sequence-nodejs, > not pkg-js-tools and pkg-js-tools will continue to provide > dh-sequence-nodejs via its dependency to dh-nodejs) and a better > usability. > > What do you think about this ? Sounds sensible to me. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] pkg-js-tools news
Quoting Yadd (2022-03-14 15:45:23)
> Le Lundi, Mars 14, 2022 15:07 CET, Jonas Smedegaard a écrit:
> > Quoting Yadd (2022-03-14 08:41:44)
> > > pkg-js-tools 0.13.0 improve pkgjs-depends and add a new
> > > dh_nodejs_autodocs tool (to automatically install components
> > > documentation: @rouca, this is for you ;-))
> > >
> > > Here is the result of new "-c" option (display mismatch versions)
> > >
> > > $ pkgjs-depends -c ava
> >
> > Using option -c requires apt-file. This should probably grow a
> > Recommends: for the package, or at least a Suggests: and a notice in
> > long description.
> >
> > That option -c fails unless mismatching packages are installed.
>
> It shouldn't, could you share some logs ?
On a clean chroot, with pkg-js-tools installed (and its recommendations
- i.e. *not* a broken system):
root@auryn:/# pkgjs-depends -c ava
internal/modules/cjs/loader.js:818
throw err;
^
Error: Cannot find module 'semver'
Require stack:
- /[eval]
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 (internal/modules/cjs/helpers.js:74:18)
at [eval]:2:12
at Script.runInThisContext (vm.js:120:18)
at Object.runInThisContext (vm.js:309:38)
at Object. ([eval]-wrapper:10:26)
at Module._compile (internal/modules/cjs/loader.js:999:30)
at evalScript (internal/process/execution.js:94:25) {
code: 'MODULE_NOT_FOUND',
requireStack: [ '/[eval]' ]
}
Unable to check versions, did you install node-semver ?
After installing node-semver:
# pkgjs-depends ava
Can't exec "npm": No such file or directory at /usr/share/perl5/Dpkg/IPC.pm
line 311.
pkgjs-depends: error: unable to execute npm view --json ava version: No such
file or directory
# ava@Can't exec "apt-file": No such file or directory at
/usr/share/perl5/Dpkg/IPC.pm line 311.
pkgjs-depends: error: unable to execute apt-file search /nodejs/ava/: No such
file or directory
ava not found
Can't exec "npm": No such file or directory at /usr/share/perl5/Dpkg/IPC.pm
line 311.
pkgjs-depends: error: unable to execute npm view --json ava version name
dependencies peerDependencies: No such file or directory
After installing npm (and it shitload of dependencies/recommendations):
# pkgjs-depends ava
# ava@4.1.0Can't exec "apt-file": No such file or directory at
/usr/share/perl5/Dpkg/IPC.pm line 311.
pkgjs-depends: error: unable to execute apt-file search /nodejs/ava/: No such
file or directory
Can't exec "apt-file": No such file or directory at
/usr/share/perl5/Dpkg/IPC.pm line 311.
pkgjs-depends: error: unable to execute apt-file search /nodejs/acorn/: No such
file or directory
Can't exec "apt-file": No such file or directory at
/usr/share/perl5/Dpkg/IPC.pm line 311.
pkgjs-depends: error: unable to execute apt-file search /nodejs/acorn-walk/: No
such file or directory
Can't exec "apt-file": No such file or directory at
/usr/share/perl5/Dpkg/IPC.pm line 311.
pkgjs-depends: error: unable to execute apt-file search /nodejs/arrgv/: No such
file or directory
Can't exec "apt-file": No such file or directory at
/usr/share/perl5/Dpkg/IPC.pm line 311.
pkgjs-depends: error: unable to execute apt-file search /nodejs/cbor/: No such
file or directory
Can't exec "apt-file": No such file or directory at
/usr/share/perl5/Dpkg/IPC.pm line 311.
pkgjs-depends: error: unable to execute apt-file search /nodejs/nofilter/: No
such file or directory
Can't exec "apt-file": No such file or directory at
/usr/share/perl5/Dpkg/IPC.pm line 311.
pkgjs-depends: error: unable to execute apt-file search /nodejs/chunkd/: No
such file or directory
Can't exec "apt-file": No such file or directory at
/usr/share/perl5/Dpkg/IPC.pm line 311.
pkgjs-depends: error: unable to execute apt-file search
/nodejs/ci-parallel-vars/: No such file or directory
Can't exec "apt-file": No such file or directory at
/usr/share/perl5/Dpkg/IPC.pm line 311.
pkgjs-depends: error: unable to execute apt-file search
/nodejs/clean-yaml-object/: No such file or directory
Can't exec "apt-file": No such file or directory at
/usr/share/perl5/Dpkg/IPC.pm line 311.
pkgjs-depends: error: unable to execute apt-file search /nodejs/code-excerpt/:
No such file or directory
Can't exec "apt-file": No such file or directory at
/usr/share/perl5/Dpkg/IPC.pm line 311.
pkgjs-depends: error: unable to execute apt-file search
/nodejs/convert-to-spaces/: No such file or directory
Can't exec "apt-file": No such file or directory at
/usr/share/perl5/Dpkg/IPC.pm line 311.
pkgjs-depends: error: unable to execute apt-file search
/nodejs/common-path-prefix
Re: [Pkg-javascript-devel] pkg-js-tools news
Quoting Yadd (2022-03-14 08:41:44) > Hi all, > > pkg-js-tools 0.13.0 improve pkgjs-depends and add a new > dh_nodejs_autodocs tool (to automatically install components > documentation: @rouca, this is for you ;-)) > > Here is the result of new "-c" option (display mismatch versions) > > $ pkgjs-depends -c ava Using option -c requires apt-file. This should probably grow a Recommends: for the package, or at least a Suggests: and a notice in long description. That option -c fails unless mismatching packages are installed. I suggest to at least mention that constraint in man page, or (obviously) avoid that constraint if possible. Even without the option -c it takes extremely long time for big projects - I gave up after a few hours trying this command: pkgjs-depends @solid/community-server Maybe use Progress::Any::Output::TermProgressBarColor to enhance user experience? Maybe processing time could be drastically faster by bypassing apt-file: Essentially it does a grep on packaging files, so replacing 1000 calls to apt-file which does 1000 calls to grep is likely far more efficiently done by loading packaging files once and grepping internally in perl. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] help understanding autopkgtest failures for node-eslint-visitor-keys
Quoting Nilesh Patra (2022-02-28 22:52:20) > On 3/1/22 2:34 AM, Jonas Smedegaard wrote: > >> Simple solution is to create a temporary dir; or use > >> $AUTOPKGTEST_TMP (latter is best) > >> > >> I have attached a patch that fixes this, please apply and upload. > >> > >> Hope that helps. > > > > Thanks, very helpful. > > > > Do you happen to know where this behaviour is documented upstream? > > Unfortunately not. Actually, a few months back, I saw this in another > package (IIRC, that was yours too) I just fiddled around a bit and > found out back then. Ah, that was you as well? I remember having noticed that trick with $AUTOPKGTEST_TMP before, just didn't know (or remember) exactly what it was solving. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] help understanding autopkgtest failures for node-eslint-visitor-keys
Quoting Nilesh Patra (2022-02-28 19:21:07) > On 2/28/22 3:01 PM, Jonas Smedegaard wrote: > > Currently, autopkgtest fails for node-eslint-visitor-keys and I cannot > > figure out why. > > > > I would be happy if others could have a look and maybe help spot why it > > fails. > > [...] > > > Error: Cannot find module > > '/tmp/autopkgtest-lxc.w0404gv_/downtmp/build.H9q/src/dist/eslint-visitor-keys.cjs' > > at createEsmNotFoundErr (internal/modules/cjs/loader.js:842:15) > > at finalizeEsmResolution (internal/modules/cjs/loader.js:835:15) > ^^ > > As you might have noticed above, it tries to find dist/ in > the local autopkgtest directory instead of global one (/usr/share/) > > This happens because you are running the test in the same directory > where your source code is and the "local" package.json is interfering > with your "require" command. > > Simple solution is to create a temporary dir; or use $AUTOPKGTEST_TMP > (latter is best) > > I have attached a patch that fixes this, please apply and upload. > > Hope that helps. Thanks, very helpful. Do you happen to know where this behaviour is documented upstream? I ask because I experience another possibly similar error with failure locating chai for node-eslint-visitor-keys 3.3.0+~0.0.51, where it is not an option to switch directory. > > The package does _not_ use pkg-js-tools. > > Had you used this, it'd have passed since it does the change to temp > dir thing by default That's good to know, for packages using pkg-js-tools. > > Works fine interactively in a local pristine chroot with only nodejs > > and node-eslint-visitor-keys installed. > > I hope you run the autopkgtest in a schroot/container and were able to > reproduce it? Not sure what you mean to say here. I use a pbuilder chroot, and as I wrote I was unable to reproduce it - thanks to your explanation I now know why: interactive access and scripted access are not same environment with pbuilder. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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] help understanding autopkgtest failures for node-eslint-visitor-keys
Hi,
Currently, autopkgtest fails for node-eslint-visitor-keys and I cannot
figure out why.
I would be happy if others could have a look and maybe help spot why it
fails.
The package does _not_ use pkg-js-tools.
The test is this minimal command:
node -e "require('eslint-visitor-keys');"
Works fine interactively in a local pristine chroot with only nodejs and
node-eslint-visitor-keys installed.
Fails on Debian servers with this error:
internal/modules/cjs/loader.js:406
throw e;
^
Error: Cannot find module
'/tmp/autopkgtest-lxc.w0404gv_/downtmp/build.H9q/src/dist/eslint-visitor-keys.cjs'
at createEsmNotFoundErr (internal/modules/cjs/loader.js:842:15)
at finalizeEsmResolution (internal/modules/cjs/loader.js:835:15)
at trySelf (internal/modules/cjs/loader.js:400:12)
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:793:24)
at Function.Module._load (internal/modules/cjs/loader.js:667:27)
at Module.require (internal/modules/cjs/loader.js:887:19)
at require (internal/modules/cjs/helpers.js:74:18)
at [eval]:1:1
at Script.runInThisContext (vm.js:120:18)
at Object.runInThisContext (vm.js:309:38) {
code: 'MODULE_NOT_FOUND',
path: '/tmp/autopkgtest-lxc.w0404gv_/downtmp/build.H9q/src/package.json'
}
- Jonas
--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: 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#1003332: Bug#1003332: Proposed webpack5 compatible patch for node-es6-promise.
Quoting Jonas Smedegaard (2022-02-26 09:48:41) > Hi Caleb, > > Quoting Caleb Adepitan (2022-02-26 00:58:46) > > I just updated my fork of node-es6-promise which was reported to fail > > build with webpack5 earlier. > > Thanks for bringing my attention to this bugreport. > > I guess you did so because I was the last one to work on that package. > > I am however not really involved in maintaining that package - I only > did a minimal change as a "team maintenance" which sort-of means a > fly-by change within the team. Silly me: Your changes are as minimal as mine was for terser, so I can just as well release yours as a "Team upload" as well. Doing that now. Thanks! (also, I will file the suggestion about rollup and uglify-js as an independent bugreport). - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1003332: Proposed webpack5 compatible patch for node-es6-promise.
Hi Caleb, Quoting Caleb Adepitan (2022-02-26 00:58:46) > I just updated my fork of node-es6-promise which was reported to fail > build with webpack5 earlier. Thanks for bringing my attention to this bugreport. I guess you did so because I was the last one to work on that package. I am however not really involved in maintaining that package - I only did a minimal change as a "team maintenance" which sort-of means a fly-by change within the team. Although my concrete change involved terser which I notice that your changes also affect, I really have no special knowledge on how es6-promise should or should not use terser: All I did was to rename the call to the terser executable. I recommend that you try reach out to the package maintainer - Julien Puydt - whom I assume has the most intimate knowledge on the packaging setup of this package. Now that I am looking anyway, I do notice that upstream does _not_ use terser but uglify-js (via broccoli-uglify-js). Also, upstream seemingly does not use webpack either, but rollup (via broccoli-rollup). You might consider looking into _simplifying_ packaging by using rollup and uglify-js (but without the broccoli wrappers which are not in Debian). My point is that maybe *not* using webpack here is a more sensible way to help migration to webpack5 than to continue deviate from upstream build approach. Just make sure to coordinate such change with the maintainer, since that is (from the maintenance point of view) a more radical change. Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1006053: Bug#1006053: node-regexpp: FTBFS: Cannot find type definition file for 'eslint'.
Control: reassign -1 eslint Control: found -1 6.1.0~dfsg+~6.1.9-1 Quoting Lucas Nussbaum (2022-02-19 07:51:14) > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > make[1]: Entering directory '/<>' > > pandoc --from gfm-raw_html --to html --standalone --output README.html > > README.md > > [WARNING] This document format requires a nonempty element. > > Defaulting to 'README' as the title. > > To specify a title, use 'title' in metadata or --metadata title="...". > > pandoc --from gfm-raw_html --to plain --output README.txt README.md > > tsc --module es2015 > > [91merror[0m[90m TS2688: [0mCannot find type definition file for > > 'eslint'. > > The file is in the program because: > > Entry point for implicit type library 'eslint' This is a bug in recent releases of esling, failing to include all its TypeScript types. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1006359: Bug#1006359: node-eslint-utils: Update to node-dot-prop 7
Control: severity -1 important Quoting Yadd (2022-02-24 09:21:29) > I just released node-dot-prop 7.2.0. API changed. Here is a trivial > patch that fixes test. Thanks. Appreciated! Will postpone applying the patch, however, until it can be verified that it works: Currently testsuite is not checked due to Node.js module esm missing in Debian. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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-trust-json-document
Quoting Ayoyimika Ajibade (2022-02-25 09:16:17) > I have taken into consideration the information and corrections and > here is the updated repo > https://salsa.debian.org/Ayoyimika/node-trust-json-document Thanks! Looks good - released now, targeted unstable. I did make one minor adjustment (too minor to mention in changelog): You added a lintian override which was reported as a mismatch on my system. Not sure why (and your commit message is fine, I don't mean to say that you should have been more detailed). Maybe you ran an older lintian than I have installed? Maybe your system has some non-standard lintian rules added? But as said it was really only a minor detail: The other half of your lintian-overrides commit was correct, and I would have accepted your change even if you had not messed with lintian overrides at all, since all those lintian overrides are completely unrelated to your future-proofing of webpack. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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#1006378: Bug#1006378: Bug#1006378: Bug#1006378: Bug#1006378: pkg-js-tools: pkg-js-autopkgtest-require fails with type=module without default export
Quoting Yadd (2022-02-24 17:54:15) > On 24/02/2022 17:43, Yadd wrote: > > On 24/02/2022 17:31, Yadd wrote: > >> I'm going to fix this > > Sorry, my explanation was for a previous fix with "nodepath". Fixed > > in 0.12.10 with a real check. Thanks! > Note that "require" test is a best-effort test. You can disable it for > a specific module in debian/tests/pkg-js/require-SKIP or disable > globally require test using: > >echo require > debian/nodejs/pkg-js/SKIP > > Then only real test will be launched. This is useful for > not-really-nodejs modules. See node-grunt-webpack for example I fail to locate the word "SKIP" anywhere in /usr/share/doc/pkg-js-tools/README.md.gz Am I looking the wrong place, or it this (literally) an undocumentated feature? - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: 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
