[Pkg-javascript-devel] Bug#986117: yarnpkg is not compatible with node-proper-lockfile 3.0.0+

2021-03-29 Thread anomie
Package: yarnpkg Version: 1.22.10+~cs22.25.14-2 Yarn uses proper-lockfile to implement its `--mutex=file:whatever` option. Its package.json depends on proper-lockfile ^2.0.0, which had the calling convention lockfile.lock( file, options, callback ) In proper-lockfile 3.0.0 they removed that ca

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

2021-01-25 Thread anomie
On Sat, 23 Jan 2021 15:37:08 +0100 Paolo Greppi wrote: > you need to add the following as in my previous message: > >cd foo >yes '' | yarn init >cd .. Yes. The example was simplified to show exactly the bug at hand, not to fully work. I confirm that your patch fixes the bug I was se

[Pkg-javascript-devel] Bug#980775: yarnpkg is not compatible with node-uuid 7.0.0+

2021-01-21 Thread anomie
Package: yarnpkg Version: 1.22.10+~cs22.25.14-1 From https://www.npmjs.com/package/uuid/v/7.0.1#default-export-removed: > Default Export Removed > > uuid@3 was exporting the Version 4 UUID method as a default export: > > const uuid = require('uuid'); // <== REMOVED! > > This usage pattern was a

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

2020-10-26 Thread anomie
Package: node-mkdirp Version: 1.0.4-2 Severity: critical I don't know whether to report this against node-mkdirp for breaking compatibility, or yarnpkg for depending on "node-mkdirp (>= 0.5.1)" rather than "node-mkdirp (>= 0.5.1), node-mkdirp (<<1.0.0)". Either way, things are currently broken in