[Pkg-javascript-devel] Bug#1012021: Bug#1012021: unreproducible here

Il 29/05/22 21:34, Pirate Praveen ha scritto: On തി, മേയ് 30 2022 at 12:56:53 രാവിലെ +05:30:00 +05:30:00, Pirate Praveen wrote: On ഞാ, മേയ് 29 2022 at 09:34:45 രാവിലെ +02:00:00 +02:00:00, Paolo Greppi wrote: Hi Andreas! thanks for your report. To try to reproduce it, I set ... Finally

[Pkg-javascript-devel] Bug#1012021: unreproducible here

Hi Andreas! thanks for your report. To try to reproduce it, I set up multiarch for docker (https://github.com/multiarch/qemu-user-static) then: docker run --rm -it arm64v8/debian:unstable bash apt update apt upgrade apt install curl yarnpkg curl -o package.json https://salsa

Re: [Pkg-javascript-devel] Rebuilding of nodejs reverse dependencies

Hi Jérémy, Il 17/03/22 13:26, Jérémy Lal ha scritto: ... So I ended up installing a gitlab-runner with nspawn-runner and a semi-active server I maintain. I documented the process here: https://wiki.debian.org/Salsa/Doc/CustomRunners/SystemdNspawnRunner

Re: [Pkg-javascript-devel] Bug#980316: about corepack and yarnpkg

Hi all Il 09/01/22 21:59, Paolo Greppi ha scritto: I stumbled upon this thread related to packaging corepack for gentoo: https://github.com/nodejs/corepack/issues/76 We now have node 16 in experimental, but our package does not bundle corepack (as upstream does): https://packages.debian.org

Re: [Pkg-javascript-devel] RFH: puppeteer tests

On 14/01/22 09:48, Jérémy Lal wrote: Le ven. 14 janv. 2022 à 09:41, Yadd > a écrit : ... Hi, I started to modify your package. The problem for tests is that it launches chromium, then this requires X server. Unless the tests run chromium with the --headles

[Pkg-javascript-devel] Bug#980316: about corepack and yarnpkg

I stumbled upon this thread related to packaging corepack for gentoo: https://github.com/nodejs/corepack/issues/76 We now have node 16 in experimental, but our package does not bundle corepack (as upstream does): https://packages.debian.org/experimental/amd64/nodejs/filelist I propose that we

[Pkg-javascript-devel] Bug#1001532: Bug#1001532: yarnpkg: yarnpkg --version cannot find @babel/runtime/helpers module

Il 11/12/21 18:29, Brian Thompson ha scritto: Package: yarnpkg Severity: important Dear Maintainer, After install yarnpkg for the first time and running `yarnpkg --version`, I got the following error: Error: Cannot find module '@babel/runtime/helpers/interopRequireWildcard' I expected the pac

[Pkg-javascript-devel] Bug#991544: closing rathen than merging

See https://bugs.debian.org/985857 Paolo -- 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#991544: Bug#991544: please package bootstrap 5

Hi, Il 27/07/21 08:51, Daniel Baumann ha scritto: Package: twitter-bootstrap4 Hi, thanks a lot for maintaining bootstrap in Debian. Do you already have an ETA for bootstrap 5 (probably a new package in Debian I guess)? Regards, Daniel thanks for your request but twitter-bootstrap4 is no D

Re: [Pkg-javascript-devel] Processed: BTS housekeeping and severity adjustments

Il 31/05/21 23:33, Debian Bug Tracking System ha scritto: Processing commands for cont...@bugs.debian.org: severity 986117 serious Bug #986117 [yarnpkg] yarnpkg is not compatible with node-proper-lockfile 3.0.0+ Severity set to 'serious' from 'normal' ... Hu everybody, I have drafted a patch

[Pkg-javascript-devel] Bug#940704: I give up

Control: noowner -1 Control: tags -1 - pending Trying to make the upstream test suite, designed for jest 22, work with our jest 26 is tricky. Also some things defy intuition, i.e. I patch here: https://salsa.debian.org/js-team/node-yarnpkg/-/blob/wip/paolog/jest/debian/patches/20-jest-require-a

[Pkg-javascript-devel] Bug#981241: tracker.debian.org: please update uscan

Package: tracker.debian.org X-Debbugs-Cc: pkg-javascript-de...@lists.alioth.debian.org Severity: important For yarnpkg: https://tracker.debian.org/pkg/node-yarnpkg tracker.debian.org reports: uscan had problems while searching for a new upstream version: unrecognized option ctype=nodejs The

[Pkg-javascript-devel] Bug#940704: Bug#940704: next error

Dear Xavier, Il 27/01/21 06:30, Xavier ha scritto: Le 27/01/2021 à 00:14, Paolo Greppi a écrit : I fixed the error:     Cannot find module 'babel-preset-env' but I am not sure if the fix is 100% right. Now I get:     TypeError: Cannot read property 'mkdir' of und

[Pkg-javascript-devel] Bug#940704: next error

I fixed the error: Cannot find module 'babel-preset-env' but I am not sure if the fix is 100% right. Now I get: TypeError: Cannot read property 'mkdir' of undefined 5 | export default function(filename?: string): Promise { 6 | return new Promise((resolve, reject

[Pkg-javascript-devel] node-temp 0.9.4

Hi, I am preparing an update for node-temp to version 0.9.4, among other things it contain a fix to this issue: https://github.com/bruce/node-temp/issues/91 That will at some point surface in yarnpkg autopkgtest, which I am still struggling to set up (see https://bugs.debian.org/940704). The e

[Pkg-javascript-devel] node-i18next-xhr-backend is holding node-babel7 migration

According to: https://tracker.debian.org/pkg/node-babel7: Issues preventing migration: autopkgtest for node-i18next/19.8.2+dfsg-4 Actually I tried building node-i18text 19.8.4 on sid, and it works fine including autopkgtest. And from: https://tracker.debian.org/pkg/node-i18next Issues preventin

[Pkg-javascript-devel] Bug#940704: new error: Cannot find module 'babel-preset-env'

Hi, I think I fixed the error: Cannot find module 'babel-plugin-transform-inline-imports-commonjs' with this commit: https://salsa.debian.org/js-team/node-yarnpkg/-/commit/d055e01b6d1a7f6fad6df2ccdf6d0f7d01ddcbc2 but the tests still fail, all with this new error: FAIL __tests__/commands/li

[Pkg-javascript-devel] Bug#980775: your initial example also fails with upstream

I tried using the docker "official image" for node: docker pull node docker run -it --rm node bash mkdir -p test/foo cd test yes '' | yarn init yarn add file:foo yields: yarn add file:foo yarn add v1.22.5 info No lockfile found. [1/4] Resolving packages... [2/4] Fetching p

[Pkg-javascript-devel] Bug#980775: patch

With this WIP patch: https://salsa.debian.org/js-team/node-yarnpkg/-/blob/master/debian/patches/18-uuid.diff I can do: rm -rf /tmp/test mkdir -p /tmp/test/foo cd /tmp/test yes '' | yarn init cd foo yes '' | yarn init cd .. yarn add file:foo and get: yarn add

[Pkg-javascript-devel] Bug#979551: Bug#979551: node-babel7: update-alternatives set up fails

Il 08/01/21 11:35, Jonas Smedegaard ha scritto: Quoting Paolo Greppi (2021-01-08 08:46:36) I guess that's because the bullseye-slim image lacks the manpages. A Debian install with man pages excluded seems to be an unsupported system: Whatever hooks applied to do that trick should be ext

[Pkg-javascript-devel] Bug#979551: node-babel7: update-alternatives set up fails

Package: node-babel7 Version: 7.12.11+~cs150.141.84-3 Severity: important Dear Maintainer, installing node-babel7 on official debian "bullseye-slim" docker image fails like this: docker pull debian:bullseye-slim docker run --rm -it debian:bullseye-slim apt update && apt install -y --no-install

[Pkg-javascript-devel] Yarnpkg future

The good news of 2020 was the successful team effort (thanks again Akshay S Dinesh and Pirate Praveen !) to keep yarnpkg in bullseye. Tha bad news of 2021 has been these issues being closed by upstream: https://github.com/yarnpkg/yarn/issues/8081 https://github.com/yarnpkg/yarn/issues/8083 https

[Pkg-javascript-devel] Bug#940704: autopkgtests now failing

I have enabled he upstream test suite on salsa, it fails with many of these: FAIL __tests__/commands/install/integration.js ● Test suite failed to run Cannot find module 'babel-plugin-transform-inline-imports-commonjs' Require stack: ... See: https://salsa.debian.org/js-team/node-

[Pkg-javascript-devel] Bug#940704: some tests do pass

I have run jest in the yarnpkg source tree with: jest --ci __tests__/ having this jest.config.js to disable failing tests: module.exports = { testURL: "http://localhost/";, testPathIgnorePatterns: [ "/node_modules/", "/__tests__/index.js", "/__tests__/integration.js", "/__tes

[Pkg-javascript-devel] Bug#977781: Bug#977781: Bug#977781: real issue is, it does not pull not-yet-cached modules

Hi Akshay, many thanks for the debugging ! see below Il 22/12/20 06:06, Akshay S Dinesh ha scritto: There are some 4 pipes before the finish event. I'm looking through each one of them to see if there's a mismatch. It seems to be tar-fs Please see https://salsa.debian.org/js-team/node-yar

[Pkg-javascript-devel] Bug#977781: real issue is, it does not pull not-yet-cached modules

Hi Pirate, what you want to put in ~/.yarnrc.yml could be installed globally to /etc/yarn/config or /etc/yarnrc, but that does not actually fix it. I think the real issue is that it does not pull not-yet-cached modules. To reproduce: # clear cache rm -rf ~/.cache/yarn # actual test cd

[Pkg-javascript-devel] Bug#976081: Bug#976081: yarnpkg: Provide prebuilt yarnpkg in contrib

On Sun, 29 Nov 2020 18:02:16 +0530 Pirate Praveen wrote: Control: clone -1 -2 Control: retitle -2 "Provide prebuilt yarnpkg in contrib" On Sat, Nov 28, 2020 at 22:07, Paolo Greppi wrote: >> 3. Build it using 'deb >> https://snapshot.debian.org/archive/debian/20

[Pkg-javascript-devel] Bug#973741: Bug#973741: gitlab: Yarn hasn't been able to find a cache folder it can use

there is a 4th option, see below Il 28/11/20 20:28, Pirate Praveen ha scritto: ... So some options I can think, 1. Port yarn 1.x to build with babel 7 (but this has not been successfull) 2. Try to run ES6 code directly somehow, may be with newer nodejs and patches. I think Paolo tried this opt

[Pkg-javascript-devel] Bug#973741: Bug#973741: gitlab: Yarn hasn't been able to find a cache folder it can use

See below Il 28/11/20 20:28, Pirate Praveen ha scritto: On Thu, 19 Nov 2020 23:50:24 +0530 Pirate Praveen wrote: ... So some options I can think, 1. Port yarn 1.x to build with babel 7 (but this has not been successfull) 2. Try to run ES6 code directly somehow, may be with newer nodejs and pa

Re: [Pkg-javascript-devel] Bug#972952: Bug#972952: node-mkdirp 1.0 is incompatible with 0.5, breaks yarnpkg

Hi Xavier, Il 26/10/20 20:24, Xavier ha scritto: Le 26/10/2020 à 15:28, ano...@users.sourceforge.net a écrit : ... Hi JS Team, yarnpkg is not in testing due to babel problems. Do you agree to dicrease severity of this bug to allow mkdirp transition (or reassign this bug to node-yarnpkg) ?

Re: [Pkg-javascript-devel] please bring yarnpkg back to testing

Hi Pravi, see below Il 14/09/20 19:01, Pirate Praveen ha scritto: > > > On Mon, Sep 14, 2020 at 17:12, Paolo Greppi wrote: >> #960120 is keeping yarnpkg out of testing; there are two ways to resolve >> this: >> >> 1. work with upstream to fix this mess

Re: [Pkg-javascript-devel] please bring yarnpkg back to testing

Il 14/09/20 17:55, Xavier ha scritto: > Le 14/09/2020 à 17:12, Paolo Greppi a écrit : >> #960120 is keeping yarnpkg out of testing; there are two ways to resolve >> this: >> >> 1. work with upstream to fix this mess (not likely to happen as upstream >> seems

[Pkg-javascript-devel] please bring yarnpkg back to testing

#960120 is keeping yarnpkg out of testing; there are two ways to resolve this: 1. work with upstream to fix this mess (not likely to happen as upstream seems unresponsive) 2. revert the changes that caused the issue; the last successful salsa CI pipeline I can find is this one: https://salsa.de

Re: [Pkg-javascript-devel] How to switch to DEP14 automatically for > 1000 existing repositories

Hi Andreas, Il 11/09/20 12:16, Andreas Tille ha scritto: > Hi, > > in teams where I have lots of packages (summing up to more than 1000) > I've touched) we followed the gbp default and have branches > > master > upstream > pristine-tar > > and this is also the layout fixed in those

[Pkg-javascript-devel] Bug#960120: node-yarnpkg: I found an older commit that still builds

Il 15/08/20 14:00, Pirate Praveen ha scritto: >> With this build: >> https://salsa.debian.org/js-team/node-yarnpkg/-/jobs/915568#L2420 > >> I get a different error while building: >> [17:58:12] Starting 'build'... >> 2420[17:58:13] Error: [BABEL] >> /builds/js-team/node-yarnpkg/debian/output/node

[Pkg-javascript-devel] Bug#960120: different error during build

With this build: https://salsa.debian.org/js-team/node-yarnpkg/-/jobs/915568#L2420 I get a different error while building: [17:58:12] Starting 'build'... 2420[17:58:13] Error: [BABEL] /builds/js-team/node-yarnpkg/debian/output/node-yarnpkg-1.22.4/src/api.js: Cannot find module 'babel-plugin-tran

[Pkg-javascript-devel] Bug#964218: Bug#964218: node-yarnpkg: autopkgtest fails with node-uuid 8.2 from experimental - "Cannot read property 'v4' of undefined"

Updating that dependency is already in upsream's TODO list https://github.com/yarnpkg/yarn/issues/6829 .. but they seem to lag on updating dependencies. I guess it would require fixing against this breaking change: https://github.com/uuidjs/uuid/blob/master/CHANGELOG.md#-breaking-changes and upstr

Re: [Pkg-javascript-devel] Bug#961337: ITP: A secure runtime for JavaScript and TypeScript.

Il 29/06/20 21:27, Akshat Agarwal ha scritto: > Package: wnpp > Followup-For: Bug #961337 > Owner: Akshat Agarwal > > > * Package name: deno > Version : 1.1.2 > Upstream Author : Deno authors > * URL : https://github.com/denoland/deno > * License : MIT > Pro

[Pkg-javascript-devel] Bug#940511: Bug#940511: yarnpkg: Package symlink yarn -> yarnpkg

See below ... On Wed, 20 May 2020 18:08:29 +0200 =?UTF-8?Q?Ma=C3=ABl_Nison?= wrote: > Hi, I'm Maël, Yarn's lead maintainer. > > While cmdtest has a popcon score higher than the yarn package, it's mostly > because Yarn isn't traditionally installed using the Debian package. For > historical reas

[Pkg-javascript-devel] Bug#940704: first try with node-jest 24.9.0

With node-jest now in the NEW queue, I have started working on this here: https://salsa.debian.org/js-team/node-yarnpkg/-/tree/jest I have built jest from https://salsa.debian.org/js-team/node-jest assuming commit b9255f45c22c030b863e7d42aaf78c207db43478 will be tagged as 24.9.0+ds-2 (althoug

[Pkg-javascript-devel] Bug#958780: Bug#958780: do we really want to do this ?

see below ... Il 30/04/20 18:10, Pirate Praveen ha scritto: > ... > I have pushed my changes to babel7 branch and the error I get is, > > gulp build > [15:53:07] Local gulp not found in /<> > [15:53:07] Try running: npm install gulp > [15:53:07] Using globally installed gulp > [15:53:07] Using gu

[Pkg-javascript-devel] Bug#958780: do we really want to do this ?

My understanding is that node-gulp-babel v8 should be used with babel7. Same goes for node-babel-loader, you need v8 for babel7, but we only have node-babel-loader 7 in Debian. If we want babel6 to co-exist with babel7, then we don't want to just update node-gulp-babel and node-babel-loader to v

[Pkg-javascript-devel] Bug#958780: take ownership

owner 958780 Paolo Greppi -- 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] theia

Hi all, I was intrigued by the recent announcement of an alternative to vscode: https://theia-ide.org/ (the ITP for the latter is stuck: https://bugs.debian.org/898259) But also to package theia you'd need electron. To get out of this stalemate, I prototyped a wrapper based on a Qt WebEngine we

[Pkg-javascript-devel] Bug#927254: closed by Xavier Guimard (Bug#927254: fixed in vue-router.js 3.0.7+ds-1)

owser because I have no time to test it (for example in laminar UI). meskio, can you test laminar with the new build ? Thanks Paolo Il 24/03/20 17:38, meskio ha scritto: > Hello Paolo, > > Quoting Paolo Greppi (2019-10-31 18:39:16) >> Hi Dmitry, I have fixed the dangling symlin

[Pkg-javascript-devel] Bug#952656: related upstream bug + behavior of upstream-provided package

see: https://github.com/yarnpkg/yarn/issues/1390 upstream-provided package correctly reports the error: docker run --rm -it debian:buster-slim /bin/bash apt update && apt install -y curl gnupg2 curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add - echo "deb https://dl.yarnpkg.com/deb

[Pkg-javascript-devel] Bug#952656: how to reproduce in docker

1. hanging: docker run --rm -it debian:buster-slim /bin/bash apt update apt install -y --no-install-recommends yarnpkg yarnpkg add --verbose highlight.js output: yarn add v1.13.0 verbose 0.668 Checking for configuration file "/.npmrc". verbose 0.668 Checking for configuration file "/usr

[Pkg-javascript-devel] Bug#952656: yarnpkg: should depend on ca-certificates

Package: yarnpkg Version: 1.21.1-1 Severity: normal if ca-certificates is not installed, yarnpkg will hang or quit abruptly without any error message / error status. To reproduce: sudo apt install yarnpkg sudo apt remove ca-certificates cd $(mktemp -d) cat > package.json { "dependencies": {

Re: [Pkg-javascript-devel] nodejs-12 transition

Il 16/01/20 20:35, Pirate Praveen ha scritto: > > > On വ്യാ, Jan 16, 2020 at 13:27, Nilesh Patra wrote: >> Hi, >> I had been lately seeing discussions in the list regarding requiring >> transition for nodejs-12 to unstable. I tested all the reverse depends and >> this is the list of all failin

Re: [Pkg-javascript-devel] gulp 4 migration

Il 14/01/20 20:43, Pirate Praveen ha scritto:  I was able to build from experimental branch and got this error. This is probably a bug in gulp itself. > ... > node-get-value should be in Depends for gulp I think. > I got meta/build to build it too (see below) with the same error. Fo

[Pkg-javascript-devel] Bug#948994: gulp should Depend on node-get-value

Package: gulp Version: 4.0.2-4 Severity: normal Dear Maintainer, while building yarnpkg on experimental, it fails while executing the gulp command: ... gulp build [18:34:23] Local gulp not found in /builds/js-team/node-yarnpkg/debian/output/node-yarnpkg-1.21.1 [18:34:23] Try running: npm insta

Re: [Pkg-javascript-devel] gulp 4 migration

Il 14/01/20 18:59, Pirate Praveen ha scritto: > ... > Forgot to attach the log I guess, also pristine-tar branch is missing the > latest version. OK attached Nope pristine-tar has node-yarnpkg_1.2.1.orig*: https://salsa.debian.org/js-team/node-yarnpkg/tree/pristine-tar > I was able to build fro

Re: [Pkg-javascript-devel] gulp 4 migration

Il 13/01/20 10:04, Pirate Praveen ha scritto: >> ... >> What is the best oneliner to test a package targeting unstable with a mix of >> selected packages from experimental ? >> >> Preferably using https://salsa.debian.org/ruby-team/meta ... >> And what about telling salsa CI to do so for us ? >> >

Re: [Pkg-javascript-devel] gulp 4 migration

Il 13/01/20 07:10, Pirate Praveen ha scritto: > ... > Nopes. FTBFS is rc and people do periodic archive wide rebuilds and this can > get packages removed from testing. I prefer we fix at least important > packages before pushing gulp 4 to unstable. > > gulp package is not an end in itself, but t

[Pkg-javascript-devel] Bug#947760: Bug#947760: Bug#947760: why ?

Il 30/12/19 11:36, Xavier ha scritto: > ... > I think that npm is needed when a package has to be build locally. > That's why a "recommends" should be enough > Xavier, I have enabled salsa CI on node-es6-iterator repo and fixed it to run tests with yarnpkg so that the dependency on npm can be dr

[Pkg-javascript-devel] Bug#947760: why ?

Hi Xavier, I did this on sid: sudo apt install yarnpkg sudo apt remove npm sudo apt autoremove git clone https://github.com/yarnpkg/yarn cd yarn rm -rf node_modules yarnpkg This works fine and installs all of yarnpkg dependencies in node_modules dir. Can you provide a use case where it fails ?

[Pkg-javascript-devel] Bug#947184: yarnpkg and gulp 4, node-glob-stream 6 and node-micromatch 4

This is fixed by node-vinyl-fs 3.0.3-3 from experimental as that version is compatible with glob-stream 6.x: https://github.com/gulpjs/vinyl-fs/blob/7e223749ee2ada1abd3b2fb326178d8ad8f39f2c/package.json#L30 I tried building yarnpkg with node-micromatch, gulp and node-glob-stream from experimenta

[Pkg-javascript-devel] Bug#947184: node-vinyl-fs: makes yarnpkg FTBFS with node-glob-stream 6.1.0-2

Package: node-vinyl-fs Version: 2.4.4-1 Severity: important This package causes yarnpkg to FTBFS since node-glob-stream was updated. A sample build log is: https://salsa.debian.org/js-team/node-yarnpkg/-/jobs/468304 The relevant part is: ... gulp build [12:14:44] Local gulp not found in /builds

[Pkg-javascript-devel] Bug#947074: proposed fix

The proposed fix is now here: https://salsa.debian.org/js-team/node-yarnpkg/commit/ec80b4e923f8513824b978f2fe0e4b25990f7987 To make sure the build is reproducible, I have based it on this code: https://sources.debian.org/src/mime-support/3.64/debian/rules/?hl=74#L74 Probably node-glob-stream 6.1

[Pkg-javascript-devel] Bug#947074: upstream tarballs for certain components contain unreasonably timestamped files

Yes, those files get the timestamp from the upstream tarballs. To reproduce: dget https://deb.debian.org/debian/pool/main/n/node-yarnpkg/node-yarnpkg_1.21.1-1.dsc ls -R --full-time node-yarnpkg-1.21.1/ | egrep -v '( 2019-| 2018-| 2017-| 2016)' It could be fixed by re-uploading the tarballs with

[Pkg-javascript-devel] npm and yarnpkg vuln

https://blog.daniel-ruf.de/critical-design-flaw-npm-pnpm-yarn/ https://github.com/yarnpkg/yarn/issues/7761 I will look at updating yarnpkg to 1.21.1 ... P. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/

[Pkg-javascript-devel] Bug#945305: RM: node-graceful-readlink -- ROM; not used and unmaintained upstream

Package: ftp.debian.org Severity: normal This package has low popcon (4) and was a build-dep of node-commander, but that dependency was removed with version 2.11.0: https://github.com/tj/commander.js/blob/master/CHANGELOG.md#2110--2017-07-03 Also the upstream repo has last been updated 5 years a

[Pkg-javascript-devel] Bug#945306: RM: node-object-assign-sorted -- ROM; currently not used

Package: ftp.debian.org Severity: normal This package has low popcon (7) and is currently not used. According to the ITP (https://bugs.debian.org/849255) it was required for lerna which was a dependency of babel-cli. But in the meantime lerna is stuck at RFP (https://bugs.debian.org/849258) and

[Pkg-javascript-devel] Fwd: Bug#945302: Acknowledgement (RM: node-command-join -- ROM; currently not used)

FYI; I forgot to X-Debbugs-Cc here. P. Messaggio Inoltrato Oggetto: Bug#945302: Acknowledgement (RM: node-command-join -- ROM; currently not used) Data: Fri, 22 Nov 2019 19:06:07 + Mittente: Debian Bug Tracking System Rispondi-a: 945...@bugs.debian.org A: paolo.gre...@lib

[Pkg-javascript-devel] d/changelog and experimental

Hi fellow team members, I was wandering what is the best approach for d/changelog when releasing a package to unstable after it has been though a few iterations to experimental. It would seem that the right thing to do is to keep all experimental changelog entries, and add a new one for unstabl

Re: [Pkg-javascript-devel] [Fwd: Re: Packaging node-timezone]

See below On 15/11/19 05:28, Trout, Diane E. wrote: > ... > I think my habit was to push the tags after the package was actually > accepted since I thought moving a tag can cause conflicts. > > Also in the python team the usually leave the distribution as > UNRELEASED until the final upload and s

Re: [Pkg-javascript-devel] Packaging node-timezone

Hi Diane, see low and lower Paolo On 10/11/19 06:50, Diane Trout wrote: > Hi, > > In a renewed effort to try and package bokeh for Debian several > JavaScript dependencies should probably be packaged, and I'm fairly new > at dealing with JavaScript packaging. > > I started with timezone. https:

[Pkg-javascript-devel] Bug#927254: closed by Xavier Guimard (Bug#927254: fixed in vue-router.js 3.0.7+ds-1)

On Sat, 14 Sep 2019 09:53:18 + Dmitry Bogatov wrote: > ... > It does not build for me. Neither it builds on Salsa CI (I added > debian/.gitlab-ci.yml on branch `wip'). > > https://salsa.debian.org/js-team/vue-router.js/-/jobs/321533 > -- > Note, that I send and fetch email in batch, once in

[Pkg-javascript-devel] Obsoleted node modules

Hi ! I was looking at node modules I maintain with a low popocont count (< 10) 1. node-array-from is only used by node-command-join 2. node-babel-plugin-array-includes is a build-dep of yarnpkg 3. node-blob according to ITP https://bugs.debian.org/781478 node-blob it is required for node-engin

[Pkg-javascript-devel] yarnpkg 1.9.1 is ready for unstable

yarnpkg is listed here: https://wiki.debian.org/Javascript/Main/packages so I am pinging the team before uploading 1.9.1 to unstable. I manually tested the only run-time dep (gitlab) and it does not break it (yarnpkg install works). I double checked the embedded modules- they're 15 The versions

[Pkg-javascript-devel] npm tarballs can be trusted, was: Re: Bug#943389: Bug#943389: node-lodash: source package does not contain upstream source

Hi Jeremy, I am replying here to the side note. On 24/10/19 19:47, Jérémy Lal wrote: > Le jeu. 24 oct. 2019 à 19:33, Jonas Smedegaard > a écrit : > .. > Side note: downloading from npmjs.org should be avoided > and maybe a > good candidate for a lintian

Re: [Pkg-javascript-devel] Bug#935845: not an RC bug; fix is easy: upgrade embedded lodash.cli

Bringing this over to the mailing list ... On 23/10/19 22:07, Jonas Smedegaard wrote: > Quoting Paolo Greppi (2019-10-23 21:18:37) >> ... >> The reason is that the bundled version of lodash-cli is out of date: >> grep version lodash-cli/package.json >> "version&

[Pkg-javascript-devel] Bug#935845: not an RC bug; fix is easy: upgrade embedded lodash.cli

First, I tripped on this one while testing yarnpkg 1.19.1 from experimental. For the record, this is how I found that node-lodash was the culprit: node --trace-deprecation /usr/bin/yarnpkg install yarn install v1.19.1 [1/4] Resolving packages... (node:29081) [DEP0016] DeprecationWarning: 'root' is

[Pkg-javascript-devel] Bug#941119: BTW, that was on buster

... everything applies to buster: apt-cache policy pkg-js-tools pkg-js-tools: Installato: 0.9.16~bpo10+1 ... add-node-component --version 0.2 P. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-jav

[Pkg-javascript-devel] Bug#941119: fails when libjson-xs-perl is installed

with: cd `mktemp -d` salsa checkout node-is-directory --group js-team cd node-is-directory/ sudo apt install libjson-xs-perl add-node-component rollup-plugin-node-builtins Thread 1 terminated abnormally: Malformed upstream registry: JSON text must be an object or array (but found number, string,

Re: [Pkg-javascript-devel] strange behavior of gbp import-orig --uscan --pristine-tar

On 03/10/19 10:19, Xavier wrote: > Never use gbp --uscan, totally buggy. Préfet uscan, then gbp import-orig > ../xx.orig.tard.gz Thanks for the quick reply. It is indeed a git-buildpackage bug: https://bugs.debian.org/934200 For future reference, this worked: cd `mktemp -d` git clone https://sa

[Pkg-javascript-devel] strange behavior of gbp import-orig --uscan --pristine-tar

I do this: cd `mktemp -d` git clone https://salsa.debian.org/js-team/node-yarnpkg cd node-yarnpkg git checkout -b upstream origin/upstream git checkout upstream git pull git checkout master gbp import-orig --uscan --pristine-tar at the end of the process, the master branch is screwed: grep name

[Pkg-javascript-devel] Bug#941354: proposed fix

I have imported the upstream patch in a new version 1.13.0-3: https://salsa.debian.org/js-team/node-yarnpkg/commit/6808cd918e8c12182e14666c715bb1d372d82449/pipelines I have checked that it now uses https even if http links are present in yarn.lock as follows: mkdir /tmp/qw cd /tmp/qw yarnpkg add

[Pkg-javascript-devel] Bug#941354: upstream patch link

one way to address this is importing this as a debian/patch: https://github.com/yarnpkg/yarn/commit/2f08a7405cc3f6fe47c30293050bb0ac94850932 Paolo -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javas

[Pkg-javascript-devel] some progress towards packaging jest

Hi, it now builds on sid: https://salsa.debian.org/js-team/node-jest/pipelines/73174 but there's still a lot to do: 1) turn on tests of course (it tests itself) 2) this lintian message is worth investigating: P: node-jest-cli: image-file-in-usr-lib usr/lib/nodejs/jest-cli/build/assets/jest_log

[Pkg-javascript-devel] Bug#940704: yarnpkg: enable upstream test suite during build

Package: yarnpkg Version: 1.13.0-1 Severity: normal the package has autopkgtest enabled but there no test is run during the build it would be safer to enable the upstream test suite, but this requires jest; I have given it a try using jest 22.4.4 installed from a separate node_modules dir and go

[Pkg-javascript-devel] Fwd: node-yarnpkg_1.13.0-2_source.changes REJECTED

-yarnpkg_1.13.0-2_source.changes REJECTED Date: Tue, 17 Sep 2019 06:50:46 + From: Debian FTP Masters To: Debian Javascript Maintainers , Paolo Greppi ACL dm: not allowed to upload source package 'node-yarnpkg' === Please feel free to respond to this email if you don't

[Pkg-javascript-devel] Fwd: node-yarnpkg_1.13.0-2_source.changes REJECTED

: node-yarnpkg_1.13.0-2_source.changes REJECTED Date: Mon, 16 Sep 2019 18:49:47 + From: Debian FTP Masters To: Debian Javascript Maintainers , Paolo Greppi node-yarnpkg_1.13.0-2.dsc: Invalid size hash for node-yarnpkg_1.13.0.orig-npm-logical-tree.tar.gz: According to the control file the size

[Pkg-javascript-devel] Bug#940514: yarnpkg: implement bash autocompletion

Package: yarnpkg Version: 1.13.0-1 Severity: normal please implement bash autocompletion for yarnpkg as we have for example in npm. -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel:

[Pkg-javascript-devel] Bug#940511: there's a already a yarn binary in Debian

Hi Melvin, thanks for raising this issue again. We can't just symlink yarn to yarnpkg or rename yarnpkg -> yarn because there's a already a yarn binary in Debian, see: https://packages.debian.org/search?suite=sid§ion=all&arch=any&searchon=contents&keywords=yarn This was extensively debated in th

[Pkg-javascript-devel] potentially interesting for the team: deno runtime for JavaScript and TypeScript

https://deno.land/ https://youtu.be/z6JRlx5NC9E echo node | sed -r 's/\<(..)(..)\>/\2\1/g' P. -- 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] potentially interesting for the team: QuickJS Javascript Engine

https://bellard.org/quickjs/ https://odino.org/playing-with-quickjs/ P. -- 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] De-embedding a component

On 14/08/19 14:57, Xavier wrote: > 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

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

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. I have done that manually for node-yarnpkg/strict-uri

[Pkg-javascript-devel] Bug#933498: seems to work with no changes

I rebuilt yarnpkg 1.13 using webpack 4.7 from experimental and it worked fine. I manually tested the resulting package and its yarnpkg executable seems to work. From visual inspection the webpack config that we are using seems compliant with the requirements of webpack 4: https://salsa.debian.o

[Pkg-javascript-devel] automatically pulling vulnerabilities from snyk.io

After filing https://bugs.debian.org/932500 I realized it would be great to have some automation in place to automatically pull vulnerabilities from https://snyk.io and turn them into CVE bugs in BTS. Thoughts ? Paolo -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian

[Pkg-javascript-devel] Bug#932500: vulnerability: prototype pollution

Package: node-mixin-deep Version: 1.1.3-3 Severity: important Dear Maintainer, node-mixin-deep 1.1.3-3 is affected by a prototype pollution vulnerability: https://snyk.io/vuln/SNYK-JS-MIXINDEEP-450212 https://github.com/jonschlinkert/mixin-deep/issues/6 Please upgrade to either 1.3.2 or 2.0.1.

[Pkg-javascript-devel] Bug#930647: this is a timezone issue

nodejs -e 'dsv = require("."); console.log(dsv.csvFormat([{date: new Date(2018, 0, 1)}]));' TZ='UTC' nodejs -e 'dsv = require("."); console.log(dsv.csvFormat([{date: new Date(2018, 0, 1)}]));' TZ='EST' nodejs -e 'dsv = require("."); console.log(dsv.csvFormat([{date: new Date(2018, 0, 1)}]));' T

[Pkg-javascript-devel] uscan thinks yarnpkg 1.17.0 has been already released

as of today, upstream has tagged yarn 1.17.0 but marked it as "Pre-release": https://github.com/yarnpkg/yarn/releases (also see screenshot) but uscan says: uscan: Newest version of node-yarnpkg on remote site is 1.17.0, local version is 1.13.0 is this something we can fix by tweaking the watch

[Pkg-javascript-devel] electron packaging

I just filed a couple of RFPs for electron apps and immediately added this one as a blocker: https://bugs.debian.org/842420 So yes there are some trending messaging apps and code editors built with electron ! Packaging it would be a huge task also because it is a mixed-language project. slocco

[Pkg-javascript-devel] Bug#927254: Bug#927254: possible solution

On 10/06/19 20:03, Paolo Greppi wrote: ... Tomorrow I'll test the generated file inside laminar. If that works this is an acceptable solution. The last bit is to move this config change to debian/rollup-umd.js so that it does not impact all builds.. Paolo I tested with the non-min

[Pkg-javascript-devel] Bug#927254: Bug#927254: possible solution

On 11/06/19 08:03, Pirate Praveen wrote: I think rollup-plugin-commonjs will also work without extra options, see node-d3-fetch. rollup-plugin-commonjs is already there in the upstream rollup config: https://salsa.debian.org/js-team/vue-router.js/blob/master/build/configs.js#L4 P. -- Pkg-ja

[Pkg-javascript-devel] Bug#927254: possible solution

If I build manually the UMD version using the same command as in debian/rules: NODE_PATH=debian/node_modules/ rollup -m -c debian/rollup-umd.js I get this: /home/paolog/Sviluppo/debian/vue-router.js/src/index.js → dist/vue-router.js... (!) Unresolved dependencies https://github.com/rollup/rollu

[Pkg-javascript-devel] Bug#927254: reproducible, but ...

Hi, nice one ! It is reproducible when I use the laminar debs built from the WIP package here: https://salsa.debian.org/debian/laminar after these fixes: https://bugs.debian.org/919181#27 Once started, the laminar service dashboard should be reachable from localhost:8080 but it fails to load. I

[Pkg-javascript-devel] Bug#929829: Bug#929829: Bug#929829: Bug#929829: Bug#929829: gulp 4 cannot build node-babel 7 - Cannot convert undefined or null to object

On 06/06/19 07:30, Xavier wrote: ... My reducejs tool gives a new analysis: * updates needed: - gulp-babel : 7.0.1 => 8.0.0 - rollup-plugin-babel : 3.0.3 => 4.3.2 * downgraded modules to embed - process-nextick-args : 2.0.0 => 1.0.7 * problems: - build fails with our readabl

  1   2   3   >