Re: [Pkg-javascript-devel] Testing migrations

Le 20/08/2019 à 17:34, Pirate Praveen a écrit : > > > On 2019, ഓഗസ്റ്റ് 20 7:26:24 PM IST, Xavier wrote: >> Hi all, >> >> please take a look at: >> >> * node-d3-request[1]: seems built for browser instead of node [1]: >> "ReferenceError:

[Pkg-javascript-devel] Testing migrations

rname) { export ^^ SyntaxError: Unexpected token export" * node-markdown-it-html5-embed[3]: missing dependency "Error: Cannot find module 'mimoza'" * node-xmpp[4]: node-stringprep breaks node-xmpp autopkgtest Cheers, Xavier [1]: https://ci.d

[Pkg-javascript-devel] Bug#934712: node-mysql: CVE-2019-14939 - Issue closed uptream without changes

Control: tags -1 - fixed-upstream Control: tags -1 + moreinfo Hi all, remote issue[1] was closed without any change in a "locked and limited to collaborators conversation" Title changed from "LOAD DATA LOCAL INFILE option shouldn't be open by default." to "Question" Mitre issue isn't updated

Re: [Pkg-javascript-devel] RFS: node-async-limiter/1.0.1-1 [#935020] -- node-async-limiter - A module for limiting concurrent asynchronous actions in flight

Le 18/08/2019 à 17:28, Joseph Nuthalapati a écrit : > Hi Xavier, > > Thanks for sponsoring the package. > >> * move test from debian/rules to debian/tests/pkg-js/test, > > I couldn't find an example of how to do tests using pkg-js/test. > The example on the wik

Re: [Pkg-javascript-devel] Fwd: node-es6-promise failure

.window = {} > } > > But I am not sure how :/ > Could you take a look at it? > > > Best, > Utkarsh node-es6-promise build is bad: our dist/es6-promise.js file is built for browser (using webpack) not for node while package.json#main points to it. Upstream bu

Re: [Pkg-javascript-devel] RFS: node-async-limiter/1.0.1-1 [#935020] -- node-async-limiter - A module for limiting concurrent asynchronous actions in flight

Le 18/08/2019 à 15:52, Xavier a écrit : > Le 18/08/2019 à 13:40, Joseph Nuthalapati a écrit : >> Package: sponsorship-requests >> Severity: wishlist >> >> Dear mentors, >> >> I am looking for a sponsor for my package "node-async-limiter" >> &

Re: [Pkg-javascript-devel] RFS: node-async-limiter/1.0.1-1 [#935020] -- node-async-limiter - A module for limiting concurrent asynchronous actions in flight

ryptPad Hi, good job. TODO: * remove debian/tests/control and debian/tests/require * move test from debian/rules to debian/tests/pkg-js/test, debian/tests/pkg-js/test will contain only: mocha --reporter spec --check-leaks --bail test/ No need to add an override_dh_auto_test * join

[Pkg-javascript-devel] Bug#935029: pkg-js-tools: Don't build depends on any node module

Package: pkg-js-tools Version: 0.9.5 Severity: wishlist Hi all, I suggest to remove all node-* modules from build dependencies and enable build tests (grunt) only in autopkgtest tests. This will avoid some circular build dependencies. Only nodejs will stay in build deps. Do you agree? -- Pkg-j

[Pkg-javascript-devel] Bug#935016: Bug#935016: pkg-js-tools: An unannounced change in "debhelper" breaks pkg-js-tools

Le 18/08/2019 à 08:15, Xavier a écrit : > Le 18/08/2019 à 08:08, Niels Thykier a écrit : >> Control: tags -1 moreinfo >> >> On Sun, 18 Aug 2019 07:55:59 +0200 Xavier Guimard wrote: >>> Package: pkg-js-tools >>> Version: 0.9.5 >>> Severity: g

[Pkg-javascript-devel] Bug#935016: pkg-js-tools: An unannounced change in "debhelper" breaks pkg-js-tools

Le 18/08/2019 à 08:08, Niels Thykier a écrit : > Control: tags -1 moreinfo > > On Sun, 18 Aug 2019 07:55:59 +0200 Xavier Guimard wrote: >> Package: pkg-js-tools >> Version: 0.9.5 >> Severity: grave >> Justification: renders package unusable >> >>

[Pkg-javascript-devel] Bug#935016: pkg-js-tools: An unannounced change in "debhelper" breaks pkg-js-tools

Package: pkg-js-tools Version: 0.9.5 Severity: grave Justification: renders package unusable pkg-js-tools was based on add_command_options which disappears in Debhelper 12.5.1. This renders pkg-js-tools unusable. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net h

Re: [Pkg-javascript-devel] Looking for help in updating npm to new usptream version

ependency ? > > On Fri, Aug 16, 2019 at 12:32 PM Xavier <mailto:y...@debian.org>> wrote: > > Le 11/08/2019 à 18:30, Manas Kashyap a écrit : > > Hola,  > > I am Manas Kashyap, a Debian contributor and currently, I am > w

Re: [Pkg-javascript-devel] Looking for help in updating npm to new usptream version

modules which are > already packaged, so looking for more contributors to help in updating npm.  > Thank you  > Manas Kashyap Remove also node-gyp, update debian/copyright and apply my patches. Then push an MR to js-team/npm so that we can work together. Cheers

[Pkg-javascript-devel] Components quality plan

Hi all, To increase embedding quality and security, I plan to do this: * tools for easier embedding (~done in pkg-js-tools >= 0.9.5) + add-node-component + del-node-component + auto_configure: creates component links in node_modules and links between component if nee

Re: [Pkg-javascript-devel] Babel

Le 15/08/2019 à 09:04, Pirate Praveen a écrit : > > > On Thu, Aug 15, 2019 at 12:07 PM, Xavier wrote: >> Hi, "gulp build-babel-standalone" command succeeds here (7.5.5) with >> the following package: PACKAGE : DEB-VERSION => GOOD-VERSION >> -

Re: [Pkg-javascript-devel] Suggestions on ruby-task-list and node-deckar01-task-list

Le 15/08/2019 à 08:18, Pirate Praveen a écrit : > On 2019, ഓഗസ്റ്റ് 14 11:05:03 PM IST, Jonas Smedegaard > wrote: > > Quoting Pirate Praveen (2019-08-14 19:08:47) > > Hi ruby and js teams, task_list project [1] provides both ruby > and nodejs code from

[Pkg-javascript-devel] Babel

Hi, "gulp build-babel-standalone" command succeeds here (7.5.5) with the following package: PACKAGE : DEB-VERSION => GOOD-VERSION --- upgraded --- babel-loader : 7.1.5 => 8.0.6 base64-js : 1.3.0 => 1.3.1 chalk : 2.3.0 =>

Re: [Pkg-javascript-devel] De-embedding a component

Le 14/08/2019 à 14:55, Paolo Greppi a écrit : > The https://wiki.debian.org/Javascript/GroupSourcesTutorial page is great > but does not cover the reverse step, when you want to de-embed a component. > > This is useful if upstream drops that dependency or if it gets separately > packaged in Debian

[Pkg-javascript-devel] yui3 problems

- which repo is the good dependency of loggerhead - does JS Team want to clean and maintain this? (yadd advice is "**no**") Cheers, Xavier [1]: https://github.com/yui/yui3 [2]: https://github.com/davglass/nodejs-yui3 [3]: https://github.com/yui/nodejs-yui3

Re: [Pkg-javascript-devel] Remove unmaintained package

Le 14/08/2019 à 07:37, Xavier a écrit : > Le 09/08/2019 à 07:22, Xavier a écrit : >> Le 08/08/2019 à 18:25, Xavier a écrit : >>> Le 08/08/2019 à 09:31, Xavier a écrit : >>>> Le 08/08/2019 à 08:09, Xavier a écrit : >>>>> Le 08/08/2019 à 07:24, Xavier a é

[Pkg-javascript-devel] Bug#934734: RM: libv8-3.14 -- ROM; outdated and useless library

Package: ftp.debian.org Severity: normal Hi all, libv8-3.14 is an outdated library with many security issue [1]. It had one reverse dependency which is ROM-RM also (#934243, done). Then I think it should be removed from Debian. Cheers, Xavier [1]: https://bugs.debian.org/cgi-bin

[Pkg-javascript-devel] Bug#934732: RM: jscommunicator -- ROM; Orphaned upstream

Package: ftp.debian.org Severity: normal Hi all, jscommunicator has been removed from testing 3 years ago. 26 issues are opened upstream [1], but there is no changes for 4 years. jscommunicator has no reverse dependencies. That's why I think it should be removed from Debian. Cheers, X

[Pkg-javascript-devel] Bug#934730: RM: node-yawl -- ROM; orphaned upstream - FTBFS

Package: ftp.debian.org Severity: normal Hi all, node-yawl never entered to testing due to FTBFS. Issue posted to upstream [1], but nobody answers. node-yawl has no reverse dependencies. That's why I propose to remove it from Debian Cheers, Xavier [1]: https://github.com/andrewrk/node

Re: [Pkg-javascript-devel] Remove unmaintained package

Le 09/08/2019 à 07:22, Xavier a écrit : > Le 08/08/2019 à 18:25, Xavier a écrit : >> Le 08/08/2019 à 09:31, Xavier a écrit : >>> Le 08/08/2019 à 08:09, Xavier a écrit : >>>> Le 08/08/2019 à 07:24, Xavier a écrit : >>>>> Le 08/08/2019 à 07:11, Xavier

[Pkg-javascript-devel] Bug#934704: buster-pu: package node-lodash/4.17.11+dfsg-2+deb10u1

Package: release.debian.org Severity: normal Tags: buster User: release.debian@packages.debian.org Usertags: pu Hi all, node-lodash is vulnerable to prototype pollution (#933079, CVE-2019-10744). I imported upstream fix in the attached debdiff. Cheers, Xavier diff --git a/debian/changelog b

[Pkg-javascript-devel] Bug#933868: grunt should look for tasks in /usr/share/nodejs as well

Control: severity -1 normal Decreasing severity since no stable package installs something in /usr/share/nodejs (apt-file search /usr/share/nodejs returns nothing). Bug exists only for backports and can be workaround using a grunt backport. -- Pkg-javascript-devel mailing list Pkg-javascript-de

Re: [Pkg-javascript-devel] Bug#932956: ITP: node-node-sass -- Wrapper around libsass

Le 13/08/2019 à 00:16, Jérémy Lal a écrit : > > > Le lun. 12 août 2019 à 22:25, Xavier <mailto:y...@debian.org>> a écrit : > > Le 12/08/2019 à 22:21, Xavier a écrit : > > Le 12/08/2019 à 19:41, Nilesh Patra a écrit : > >> > >> &

Re: [Pkg-javascript-devel] Bug#932956: ITP: node-node-sass -- Wrapper around libsass

Le 12/08/2019 à 22:21, Xavier a écrit : > Le 12/08/2019 à 19:41, Nilesh Patra a écrit : >> >> >> >> Needed component are: async-foreach, gaze, get-stdin, js-base64, >> sass-graph, sass-spec, scss-tokenizer, stdout-stream, true-case-path. >> &quo

Re: [Pkg-javascript-devel] Bug#932956: ITP: node-node-sass -- Wrapper around libsass

never embed a library that already exist in debian. I tried to add "--libsass=auto", but then compilation is bad: proved by test: /usr/bin/node: symbol lookup error: /.../node-node-sass/vendor/linux-x64-64/binding.node: undefined

Re: [Pkg-javascript-devel] Bug#934456: Bug#934456: further automation ideas for add-node-component

Le 11/08/2019 à 16:15, Xavier a écrit : > Le 11/08/2019 à 12:08, Pirate Praveen a écrit : >> On 11/08/19 3:30 pm, Xavier wrote: >>> Then: >>> * -d (download) launches uscan -dd >>> * -s (source) launches uscan + dpkg-source -b . and (quilt pop -a && &g

[Pkg-javascript-devel] Bug#934456: Bug#934456: further automation ideas for add-node-component

Le 11/08/2019 à 12:08, Pirate Praveen a écrit : > On 11/08/19 3:30 pm, Xavier wrote: >> Then: >> * -d (download) launches uscan -dd >> * -s (source) launches uscan + dpkg-source -b . and (quilt pop -a && >> rm -rf .pc) >> * -i (import)

[Pkg-javascript-devel] Bug#934456: Bug#934456: further automation ideas for add-node-component

Le 11/08/2019 à 12:08, Pirate Praveen a écrit : > On 11/08/19 3:30 pm, Xavier wrote: >> Then: >> * -d (download) launches uscan -dd >> * -s (source) launches uscan + dpkg-source -b . and (quilt pop -a && >> rm -rf .pc) >> * -i (import)

[Pkg-javascript-devel] Bug#934456: Bug#934456: further automation ideas for add-node-component

Le 11/08/2019 à 10:52, Pirate Praveen a écrit : > package: pkg-js-tools > > version: 0.8.14 > > severity: wishlist > > > I hope we can add -u (uscan), -s (source), -i (import) options for uscan > -dd, dpkg-source -b . and (quilt pop -a && rm -rf .pc) gbp import-dsc > --pristine-tar + pristine-t

[Pkg-javascript-devel] Bug#908948: create an option to add dependencies as components like in node-tar

Hi, pkg-js-tools 0.8.14 adds a "add-node-component" command which updates both gbp.conf and debian/watch Usage: $ add-node-component foo $ add-node-component foo bar $ add-node-component -g foo $ add-node-component -g foo bar Option "-g" tags component as "group" instead of "ignore" -- Pkg-jav

Re: [Pkg-javascript-devel] Basic pkg-js-tools example

Le 10/08/2019 à 13:06, Utkarsh Gupta a écrit : > Hey, > > On Wed, Aug 7, 2019 at 1:29 PM Xavier <mailto:y...@debian.org>> wrote: > > Hi all, > > for most of node-* packages, you can simplify packaging like this: > https://salsa.debian.org/js-

[Pkg-javascript-devel] Bug#934144: Bad fix

Control: repoen -1 .desc files were omitted in 0.8.13 upload -- 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] Remove unmaintained package

Le 08/08/2019 à 18:25, Xavier a écrit : > Le 08/08/2019 à 09:31, Xavier a écrit : >> Le 08/08/2019 à 08:09, Xavier a écrit : >>> Le 08/08/2019 à 07:24, Xavier a écrit : >>>> Le 08/08/2019 à 07:11, Xavier a écrit : >>>>> Hi, >>>>> &g

Re: [Pkg-javascript-devel] Remove unmaintained package

Le 08/08/2019 à 09:31, Xavier a écrit : > Le 08/08/2019 à 08:09, Xavier a écrit : >> Le 08/08/2019 à 07:24, Xavier a écrit : >>> Le 08/08/2019 à 07:11, Xavier a écrit : >>>> Hi, >>>> >>>> looking at UDD, we have a some packages that were not i

Re: [Pkg-javascript-devel] Remove unmaintained package

Le 08/08/2019 à 08:09, Xavier a écrit : > Le 08/08/2019 à 07:24, Xavier a écrit : >> Le 08/08/2019 à 07:11, Xavier a écrit : >>> Hi, >>> >>> looking at UDD, we have a some packages that were not in testing for a >>> long time and could be considered

Re: [Pkg-javascript-devel] Remove unmaintained package

Le 08/08/2019 à 07:24, Xavier a écrit : > Le 08/08/2019 à 07:11, Xavier a écrit : >> Hi, >> >> looking at UDD, we have a some packages that were not in testing for a >> long time and could be considered as orphaned. >> If nobody disagree, I'll ask their remo

Re: [Pkg-javascript-devel] Remove unmaintained package

Le 08/08/2019 à 07:11, Xavier a écrit : > Hi, > > looking at UDD, we have a some packages that were not in testing for a > long time and could be considered as orphaned. > If nobody disagree, I'll ask their removal: Update: PACKAGETIME IN

[Pkg-javascript-devel] Remove unmaintained package

Hi, looking at UDD, we have a some packages that were not in testing for a long time and could be considered as orphaned. If no one disagree, I'll ask their removal: PACKAGETIME IN QUEUE * node-carto 2103 days * node-yawl1472 days * pdf.js

[Pkg-javascript-devel] auto build

Hi, auto build is ready in salsa. I think we could release it (in experimental) with little change: never fails so no need to do a transition. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript

[Pkg-javascript-devel] Bug#934141: jsbeautifier and node-js-beautify should provide alternatives

Le 07/08/2019 à 14:56, Xavier Guimard a écrit : > Package: jsbeautifier > Version: 1.6.4-7 > Severity: normal > > Hi all, > > both jsbeautifier and node-js-beautify come from the same upstream > source, the first provides js-beautify and the second html-beautify and &g

[Pkg-javascript-devel] rollup circular dependencies

things are more worst than previously said: - rollup build depends on acorn and rollup-plugin-buble - buble depends on acorn - rollup-plugin-buble depends on buble - buble build depends on rollup - acorn build depends on rollup - rollup build depends on itself https://wiki.debian.org/Javascr

[Pkg-javascript-devel] rollup circular dependencies

Hi all, things are worst than previously said: - rollup build depends on acorn and buble - buble depends on acorn - acorn build depends on rollup - rollup build depends on itself https://wiki.debian.org/Javascript/Circular/Dependencies updated -- Pkg-javascript-devel mailing list Pkg-javasc

[Pkg-javascript-devel] Fwd: Bug#934141: jsbeautifier and node-js-beautify should provide alternatives

> --- Message transféré > Sujet : Bug#934141: jsbeautifier and node-js-beautify should provide > alternatives > Date de renvoi : Wed, 07 Aug 2019 13:00:01 + > De (renvoi) : Xavier Guimard > Pour (renvoi) : debian-bugs-d...@lists.debian.org > Copie (renv

[Pkg-javascript-devel] Bug#934144: /usr/share/lintian/checks/pkg-perl/vcs.desc of pkg-perl-tools breaks lintian if LINTIAN_PROFILE=pkg-perl is set in .lintianrc

Hi, fixed in pkg-js-tools 0.8.12. I renamed also my tags to avoid install conflicts with pkg-perl-tools -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#931714: Not fixed

Control: reopen -1 Adding node-request in recommended dependencies is not enough: package is unusable without it -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Main package list

Hi all, please update this: https://wiki.debian.org/Javascript/Main/packages Cheers, Xavier -- 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] Basic pkg-js-tools example

Hi all, for most of node-* packages, you can simplify packaging like this: https://salsa.debian.org/js-team/node-pumpify/commit/416495cd -- 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#869626: node-ws: Please update to upstream version 3.0.0

Le 07/08/2019 à 07:53, Ying-Chun Liu (PaulLiu) a écrit : > Hi Jérémy, > > > Seems I still need to update this package to 3.0.0. > > Do you mind if I do the NMU ?? > > > BTW, upgrade to 3.0.0 means we have to also package wscat. > > /usr/bin/wscat is provided in node-ws 1.1.0 but now it is a s

Re: [Pkg-javascript-devel] pkg-js-tools auto_builder

Le 05/08/2019 à 23:58, Xavier a écrit : > Hi, > > I started auto_builder, it seems to work. I need some help to fix > $known_build_commands and $knwonBuildFiles and $knownCommandMap in > https://salsa.debian.org/js-team/pkg-js-tools/blob/experimental/dh_nodejs/Buildsystem/nodejs

[Pkg-javascript-devel] pkg-js-tools auto_builder

Hi, I started auto_builder, it seems to work. I need some help to fix $known_build_commands and $knwonBuildFiles and $knownCommandMap in https://salsa.debian.org/js-team/pkg-js-tools/blob/experimental/dh_nodejs/Buildsystem/nodejs.pm How it work ? 1 - check if a debian/nodejs/build exists and lau

[Pkg-javascript-devel] Bug#933956: pkg-js-tools: auto_installer does not replace "foo" by "foo.js" in "files" field

Package: pkg-js-tools Version: 0.8.10 Severity: normal To be fixed in 0.8.11 -- 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 acorn_6.1.1+ds+~0.3.1+~4.0.0+~1.0.0+~5.0.1+ds+~1.6.2+ds-1_amd64.changes

ackage. Hi, +1 using pkg-js-tools auto_installer, components will be installed automatically in usr/share/acorn/node_modules/ unless specified in debian/nodejs//install. Also if upstream provides a package-lock (or yarn.lock), you can safely use "ignore" in debian/watch for components installed in usr/share/acorn/node_modules/ Cheers, Xavier -- 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] Webpack 4 transition plan

Le 05/08/2019 à 11:25, Pirate Praveen a écrit : > On 2019-08-05 14:11, Xavier wrote: >> Hello, >> >> Could you take a look at >> https://buildd.debian.org/status/fetch.php?pkg=select2.js&arch=all&ver=4.0.7%7Edfsg1-2&stamp=1564925650&raw=0 >> >&g

Re: [Pkg-javascript-devel] ?==?utf-8?q? Webpack 4 transition plan

Hello, Could you take a look at https://buildd.debian.org/status/fetch.php?pkg=select2.js&arch=all&ver=4.0.7%7Edfsg1-2&stamp=1564925650&raw=0 I can't reproduce locally Le Lundi, Août 05, 2019 06:29 CEST, Pirate Praveen a écrit: > > > On 2019, ഓഗസ്റ്റ് 2 9:25:28 PM IST, Pirate Praveen >

[Pkg-javascript-devel] Bug#933862: Bug#933862: nodepath does not work with grunt plugins

Le 04/08/2019 à 16:07, Xavier a écrit : > Le 04/08/2019 à 15:59, Pirate Praveen a écrit : >> Package: pkg-js-tools >> version: 0.8.10 >> >> Example package, node-handlebars >> >> ln -s `nodepath grunt-webpack` node_modules >> intern

[Pkg-javascript-devel] Bug#933862: Bug#933862: nodepath does not work with grunt plugins

Le 04/08/2019 à 15:59, Pirate Praveen a écrit : > Package: pkg-js-tools > version: 0.8.10 > > Example package, node-handlebars > > ln -s `nodepath grunt-webpack` node_modules > internal/modules/cjs/loader.js:583 >     throw err; >     ^ > > Error: Cannot find module 'grunt-webpack' >     at Func

[Pkg-javascript-devel] Bug#933847: Bug#933847: pkg-js-tools should exclude .eslintrc* in any directory

Le 04/08/2019 à 13:25, Pirate Praveen a écrit : > Package: pkg-js-tools > version: 0.8.9 > severity: important > > Example packages: node-ajv, node-webpack > > Currently added an override to remove these. Fixed in 0.8.10, to be verified -- Pkg-javascript-devel mailing list Pkg-javascript-devel

[Pkg-javascript-devel] Bug#933847: Bug#933847: pkg-js-tools should exclude .eslintrc* in any directory

Le 04/08/2019 à 13:25, Pirate Praveen a écrit : > Package: pkg-js-tools > version: 0.8.9 > severity: important > > Example packages: node-ajv, node-webpack > > Currently added an override to remove these. Logically this files are removed except if they are included in a debian/nodejs/**/files or

Re: [Pkg-javascript-devel] Tip

Le 04/08/2019 à 07:54, Pirate Praveen a écrit : > > > On 2019, ഓഗസ്റ്റ് 4 1:05:42 AM IST, Utkarsh Gupta > wrote: >> Hey, >> >> On Sat, Aug 3, 2019 at 7:08 PM Xavier wrote: >> >>> Hi, >>> >>> when you need to link a node library

Re: [Pkg-javascript-devel] pkg-js-tools migration

Le 03/08/2019 à 15:48, Xavier a écrit : > Small query: do not change anything on the packages listed below until I > push them All are tested: - build with tests - lintian ~clean - autopkgtest Salsa repos are updated with changelogs up to date. > Le 02/08/2019 à 09:21, Xavier a écri

Re: [Pkg-javascript-devel] pkg-js-tools migration

Small query: do not change anything on the packages listed below until I push them Le 02/08/2019 à 09:21, Xavier a écrit : > Hi all, > > pkg-js-tools transition is ready in salsa. After few days (more tests > with pkg-js-tools 0.8.8), I'll upload packages [3]: no upstream

[Pkg-javascript-devel] Tip

h for more. Cheers, Xavier -- 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] pkg-js-tools migration

to do this next Monday if no one disagree. Take a look at this list to see if one must not be updated from master branch. NB: after this, debian/install must be removed when using "dh --with nodejs" (or adapted if more than one binary package, see [1]). npm2deb MR is also ready [2]. Che

[Pkg-javascript-devel] pkg-js-tools transition in progress

Le 30/07/2019 à 19:51, Xavier a écrit : > Hi all, > > I rebuilt the ~100 packages that uses pkg-js-tools using version 0.8.6 > (experimental), the main problem for unstable transition is that it > causes a double install for package that didn't migrate to > "/usr/

[Pkg-javascript-devel] Bug#933540: Bug#933540: Bug#933540: pkg-js-tools auto install does not work with multiple binary packages

Le 31/07/2019 à 20:15, Xavier a écrit : > Le 31/07/2019 à 13:52, Pirate Praveen a écrit : >> Package: pkg-js-tools >> Version: 0.8.6 >> Severity: wishlist >> >> I was trying to pkg-js-tools auto install option with >> node-fuzzaldrin-plus but it did not work

[Pkg-javascript-devel] Bug#933540: Bug#933540: pkg-js-tools auto install does not work with multiple binary packages

Le 31/07/2019 à 13:52, Pirate Praveen a écrit : > Package: pkg-js-tools > Version: 0.8.6 > Severity: wishlist > > I was trying to pkg-js-tools auto install option with > node-fuzzaldrin-plus but it did not work as it had libjs-fuzzaldrin-plus > also as a binary package. The files got copied to deb

Re: [Pkg-javascript-devel] Bug#933488: seems node-uglifyjs-webpack is installing to both /usr/lib and /usr/share

Le 31/07/2019 à 10:08, Xavier a écrit : > Le 31/07/2019 à 10:02, Pirate Praveen a écrit : >> ... > > Hello, > > this is the transition problem of pkg-js-tools. Rebuild with > pkg-js-tools from unstable or remove debian/install + pkg-js-tools >= 0.8.6 I already

[Pkg-javascript-devel] Bug#933488: Bug#933488: seems node-uglifyjs-webpack is installing to both /usr/lib and /usr/share

Le 31/07/2019 à 10:02, Pirate Praveen a écrit : > $ apt-file list node-uglifyjs-webpack-plugin > node-uglifyjs-webpack-plugin: > /usr/lib/nodejs/uglifyjs-webpack-plugin/dist/index.js > node-uglifyjs-webpack-plugin: > /usr/lib/nodejs/uglifyjs-webpack-plugin/lib/post_install.js > node-uglifyjs-webpac

[Pkg-javascript-devel] pkg-js-tools transition

n error for any node package that install something in /usr/lib/nodejs: now we use /usr/share/nodejs and /usr/lib//nodejs. Any comment ? Cheers, Xavier -- 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 auto install

Le 30/07/2019 à 09:34, Jérémy Lal a écrit : > > > Le mar. 30 juil. 2019 à 08:31, Xavier <mailto:y...@debian.org>> a écrit : > > Hi all, > > I continue to improve auto_install. Here is a resume (from doc). Do you > thinks it's in the right w

Re: [Pkg-javascript-devel] pkg-js-tools auto install

Le 30/07/2019 à 09:35, Pirate Praveen a écrit : > > > On 2019, ജൂലൈ 30 12:01:19 PM IST, Xavier wrote: >> Hi all, >> >> I continue to improve auto_install. Here is a resume (from doc). Do you >> thinks it's in the right way to provide an auto-installer

[Pkg-javascript-devel] pkg-js-tools auto install

Hi all, I continue to improve auto_install. Here is a resume (from doc). Do you thinks it's in the right way to provide an auto-installer? (this part is not published in experimental but ready and with tests on salsa repo) NB: debian/nodejs/ - - - 8< - - - pkg-js-tools provides: * dh_auto_config

[Pkg-javascript-devel] pkg-js-tools debhelper addon

packages in /usr/lib//nodejs instead of deprecated /usr/lib/nodejs, (arch-independent in /usr/share/nodejs). Then like Python/Perl packages, we won't need a debian/install file. Cheers, Xavier -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://a

[Pkg-javascript-devel] Bug#933194: Automate build commands from package.json gradually, one build tool at a time

Hello, I'll start doing this when pkg-js-tools 0.8.* will be in unstable to be able to do some test in experimental Cheers, Xavier -- 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#933254: Bug#933254: Auto detection of components is broken when used in webpack

Le 28/07/2019 à 10:01, Pirate Praveen a écrit : > Package: pkg-js-tools > Version: 0.8.2 > Severity: grave > > Reproducible in node-webpack master. > > dh_auto_configure --buildsystem=nodejs > mkdir node_modules mkdir webpack-cli/node_modules > ln -s ../eslint-scope node_modules/eslint-scope > ln

[Pkg-javascript-devel] Bug#933251: Bug#933251: DEB_BUILD_PROFILES=nocheck is ignored by pkg-js-tools

Le 28/07/2019 à 09:17, Pirate Praveen a écrit : > Package: pkg-js-tools > Version: 0.8.2 > Severity: important > > DEB_BUILD_OPTIONS=nocheck works, but both should be supported. Build > options don't filter build dependencies so we can't use it when circular > test only dependencies prevent builds

[Pkg-javascript-devel] Bug#933187: Bug#933187: Make it easy to embed new modules

Le 27/07/2019 à 14:08, Pirate Praveen a écrit : > Package: npm2deb > Version: 0.3.0-1 > Severity: wishlist > > Currently embedding a module involves updating watch, gbp.conf. > > It'd be nice to have "npm2deb embed module@version" option to automate > this. Watch file should lock it to major ve

[Pkg-javascript-devel] Bug#933179: node-yallist: iterator.js is missing

Package: node-yallist Version: 3.0.3-1 Severity: important node-yallist does not install iterator.js which make it partially unusable. Please fix install. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable') Architecture: amd6

[Pkg-javascript-devel] Bug#933124: Bug#933124: node-tar: build-depends on pkg-components that won't be in Bullseye unless it finds a new upstream maintainer

consider taking over its maintenance > upstream. > > Thanks in advance! > > Cheers, Package node-tar is ready in salsa.d.o. It uses pkg-js-tools 0.8.2 (experimental) instead of pkg-components to automatically install components. Please review and comment ;-) Cheers, Xavier --

[Pkg-javascript-devel] Bug#933171: pkg-js-tools: Provide a default installer

n/install. Transition will be easy since new behavior is automatically skipped if debian/install exists. Of course any comment is welcome. Cheers, Xavier -- 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] Fwd: pkg-js-tools_0.8.2_sourceonly.changes ACCEPTED into experimental

To test it, see last commit of js-team/node-mongodb, build and see the result (logs + debc) Courriel d’origine De : Debian FTP Masters Envoyé : 26 juillet 2019 20:20:12 GMT+02:00 À : Debian Javascript Maintainers , Xavier Guimard Objet : pkg-js

Re: [Pkg-javascript-devel] Bug#933007: Bug#933007: pkg-js-tools: Automatically link components in node_modules directory

Le 25/07/2019 à 20:00, Xavier a écrit : > Le 25/07/2019 à 19:45, Xavier Guimard a écrit : >> Package: pkg-js-tools >> Version: 0.7 >> Severity: wishlist >> >> When using components in node modules, the best way to use them is to >> install them in node_m

[Pkg-javascript-devel] Bug#933007: Bug#933007: pkg-js-tools: Automatically link components in node_modules directory

Le 25/07/2019 à 20:08, Pirate Praveen a écrit : > > > On 2019, ജൂലൈ 25 11:15:50 PM IST, Xavier Guimard wrote: >> Package: pkg-js-tools >> Version: 0.8.1 >> Severity: wishlist >> >> When using components in node modules, the best way to use them is to >

[Pkg-javascript-devel] Bug#933007: Bug#933007: pkg-js-tools: Automatically link components in node_modules directory

Le 25/07/2019 à 19:45, Xavier Guimard a écrit : > Package: pkg-js-tools > Version: 0.7 > Severity: wishlist > > When using components in node modules, the best way to use them is to > install them in node_modules/ directory. However, dpkg-source install > them at the top sou

[Pkg-javascript-devel] Bug#933007: pkg-js-tools: Automatically link components in node_modules directory

Package: pkg-js-tools Version: 0.8.1 Severity: wishlist When using components in node modules, the best way to use them is to install them in node_modules/ directory. However, dpkg-source install them at the top source directory under a directory named by "component" field value (debian/watch). T

Re: [Pkg-javascript-devel] Bug#932956: ITP: node-node-sass -- Wrapper around libsass

Le 25/07/2019 à 16:00, Xavier a écrit : > Le 25/07/2019 à 15:58, Xavier a écrit : >> Le 25/07/2019 à 15:49, Xavier a écrit : >>> Le 25/07/2019 à 12:01, Nilesh Patra a écrit : >>>> >>>> >>>> >>>> Hello, >>>>

Re: [Pkg-javascript-devel] Bug#932956: ITP: node-node-sass -- Wrapper around libsass

Le 25/07/2019 à 15:58, Xavier a écrit : > Le 25/07/2019 à 15:49, Xavier a écrit : >> Le 25/07/2019 à 12:01, Nilesh Patra a écrit : >>> >>> >>> >>> Hello, >>> >>> some things to do: >>>  - Architecture must be &qu

Re: [Pkg-javascript-devel] Bug#932956: ITP: node-node-sass -- Wrapper around libsass

Le 25/07/2019 à 15:49, Xavier a écrit : > Le 25/07/2019 à 12:01, Nilesh Patra a écrit : >> >> >> >> Hello, >> >> some things to do: >>  - Architecture must be "any", not "all" >>  - don't install .md files

Re: [Pkg-javascript-devel] Bug#932956: ITP: node-node-sass -- Wrapper around libsass

Le 25/07/2019 à 15:49, Xavier a écrit : > Le 25/07/2019 à 12:01, Nilesh Patra a écrit : >> >> >> >> Hello, >> >> some things to do: >>  - Architecture must be "any", not "all" >>  - don't install .md files

Re: [Pkg-javascript-devel] Bug#932956: ITP: node-node-sass -- Wrapper around libsass

Le 25/07/2019 à 12:01, Nilesh Patra a écrit : > > > > Hello, > > some things to do: >  - Architecture must be "any", not "all" >  - don't install .md files in /usr/lib/nodejs/node-sass >  - don't install LICENSE, COPYING,... in /usr/lib/nodejs/node-sass >  - take care of

Re: [Pkg-javascript-devel] The (long) way to update rollup

Thanks a lot ! Could you build rollup with 2 passes ? First with node, then copy package.json, bin/ and dist/ to node_modules/rollup with a link in node_modules/.bin ; then rebuild with this rollup Then we will be sure to have the same rollup than upstream Le 25 juillet 2019 12:40:32 GMT+02:00

Re: [Pkg-javascript-devel] Bug#932956: ITP: node-node-sass -- Wrapper around libsass

Le 25/07/2019 à 08:33, Xavier a écrit : > Le 25/07/2019 à 08:21, Nilesh Patra a écrit : >> Package: wnpp >> Severity: wishlist >> Owner: Nilesh mailto:npatra...@gmail.com>> >> X-Debbugs-CC: debian-de...@lists.debian.org >> <mailto:debian-de...@lists.debia

Re: [Pkg-javascript-devel] Bug#932956: ITP: node-node-sass -- Wrapper around libsass

Le 25/07/2019 à 08:21, Nilesh Patra a écrit : > Package: wnpp > Severity: wishlist > Owner: Nilesh mailto:npatra...@gmail.com>> > X-Debbugs-CC: debian-de...@lists.debian.org > > > * Package name    : node-node-sass >   Version         : 4.12.0 >   Upstream Au

[Pkg-javascript-devel] Remember: Source only uploads

Hi JS DD, some packages are blocked in unstable due to new policy: testing migration is possible only after a source-only-upload. I fixed some of them. See https://udd.debian.org/dmd/?email1=pkg-javascript-devel%40lists.alioth.debian.org&format=html, tags "testing migration"

Re: [Pkg-javascript-devel] The (long) way to update rollup

23/07/2019 à 21:03, Xavier a écrit : > My first results: > > 0.50.0 can build until 0.53.3 > 0.51.7 can build until 0.56.3 > 0.56.1 can build until 0.65.2 > 0.58.1 can build until 0.67.0 at least > > This versions seems not usable (npm install + npm run build failed):

Re: [Pkg-javascript-devel] The way to update rollup

, 0.60.2, 0.60.3, 0.60.4, 0.60.5, 0.60.6, 0.60.7, 0.61.0, 0.61.2, 0.64.0, 0.66.0, 0.66.1, 0.66.3, 0.68.0, 1.1.0 Le 23/07/2019 à 16:35, Xavier a écrit : > Hi all, > > following upstream package.json, the way to update rollup follows 35 steps: > > Min Max Required version &

<    3   4   5   6   7   8   9   10   11   >