On Sun, Jul 12, 2020 at 12:52, Jonas Smedegaard wrote:
I think that when we declare only¹ lower bounds, we do avoid the
biggest
headache of nodejs failing to transition - and reduce the problem to
each package requiring a binNMU being flagged as such.
Please others chime in if you think I
On Fri, Jul 3, 2020 at 23:09, Paolo Greppi
wrote:
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:
On Thu, Jun 25, 2020 at 01:41, Pirate Praveen
wrote:
On Tue, Jun 23, 2020 at 2:40 pm, Sean Whitton
wrote:
Thanks. I think at this point we probably need to wait to hear from
Bastian, who processed the REJECT. In the meantime, it would be
good to
reupload with the reason
On 2020, ജൂലൈ 4 2:39:27 AM IST, Paolo Greppi wrote:
>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:
Package: node-yarnpkg
Version: 1.22.4-3
Severity: important
Full build log is attached. This was run in a clean and uptodate lxc
container using salsa.debian.org/ruby-team/meta/build script.
autopkgtest [18:26:50]: version 5.10
autopkgtest [18:26:50]: host ilvala2; command line:
Package: node-node-rest-client
Version: 2.5.0-4
Severity: important
This package's autopkgtest failed with node-uuid 8.2 in experimental
with error
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './v1' is not
defined by "exports" in /usr/share/nodejs/uuid/package.json
Full
--+
Unpack source
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 3.0 (quilt)
Source: node-http-signature
Binary: node-http-signature
Architecture: all
Version: 1.3.2-1
Maintainer: Debian Javascript Maint
Package: node-request
Version: 2.88.1-4
Severity: important
Build fails with this error when building with node-uuid 8.2.0-1 in
experimental.
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './v4' is not
defined by "exp
orts" in /usr/share/nodejs/uuid/package.json
Full build log
On Tue, Jun 23, 2020 at 2:40 pm, Sean Whitton
wrote:
Hello,
On Tue 23 Jun 2020 at 01:47AM +02, Jonas Smedegaard wrote:
Quoting Sean Whitton (2020-06-22 23:26:37)
Would someone want to use libjs-katex without nodejs installed?
Yes: Pandoc can produce output which uses katex rendered
On 2020, ജൂൺ 23 2:56:37 AM IST, Sean Whitton wrote:
>Hello Pirate,
>
>On Mon 22 Jun 2020 at 12:58AM +0530, Pirate Praveen wrote:
>
>> We usually use Provides instead of splitting when we can remove the Depends
>> on the interpreter. For example node-clipboard pro
ainer has consciously
>> chosen to use a binary package split to solve a problem and that's a
>> reasonable way to go about solving the problem, we'll sign off on it.
>
>Thanks for the clarification, Sean.
>
>I think that was quite helpful. I will let Pirate Praveen continue fro
On 2020, ജൂൺ 21 10:17:57 PM IST, Sean Whitton wrote:
>[speaking as an FTP team member, not ctte member, though this is *not*
>an official statement made on behalf of the whole FTP team]
>
>Hello Jonas,
>
>On Sun 21 Jun 2020 at 10:48AM +02, Jonas Smedegaard wrote:
>
>> Could you please elaborate
On 2020, ജൂൺ 19 1:40:09 AM IST, Bastian Blank
wrote:
>
>The introduces an unnecessary split into katex and libjs-katex.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934948#54
* User-facing executable programs associated with a library should usually be
packaged in a non-library binary
On 2020, ജൂൺ 16 7:46:01 AM IST, Daniel Ring wrote:
>Control: reopen 962037
>Control: reopen 962039
>
>Sorry about closing the bugs early, I'm used to close-on-commit instead
>of close-on-release and I forgot Debian handles things differently. I
>updated Rainloop's changelog on Salsa to
On Mon, Jun 15, 2020 at 4:07 pm, Pirate Praveen
wrote:
Please don't invent your own methods and follow the standards used by
the rest of the team. If everyone invents their own methods to embed,
that makes it unnecessarily hard to collaborate as a team. I don't
think the rest of the js
On Mon, Jun 15, 2020 at 4:07 pm, Pirate Praveen
wrote:
You don't have to upload broken packages to unstable. You can wait
till less.js lands in unstable to upload your changes to
experimental. The idea is to give you a chance to fix your package
before it actually breaks.
Also please
to the Rainloop repository on
salsa.d.o. Rainloop now builds successfully on current unstable with
node-less from experimental.
Thanks, I can upload it to unstable.
-- Daniel
On 6/5/2020 9:02 AM, Pirate Praveen wrote:
On Fri, Jun 5, 2020 at 5:11 pm, Pirate Praveen
wrote:
On Fri, Jun 5, 2020
On Fri, Jun 5, 2020 at 5:11 pm, Pirate Praveen
wrote:
On Fri, Jun 5, 2020 at 3:10 pm, Pirate Praveen
wrote:
This is likely broken by node-merge-stream update from 1.0 to 2.0.
node-merge-stream is a build dependeny of node-autolinker.
Tried building with autolinker 3.x in embed
On Fri, Jun 5, 2020 at 3:10 pm, Pirate Praveen
wrote:
This is likely broken by node-merge-stream update from 1.0 to 2.0.
node-merge-stream is a build dependeny of node-autolinker.
Tried building with autolinker 3.x in embed-autolinker-3 branch, but
the same failure.
I tried to run
On Fri, Jun 5, 2020 at 11:54 am, Pirate Praveen
wrote:
On Fri, Jun 5, 2020 at 11:36 am, Pirate Praveen
wrote:
I have reproduced the same error with less npm dist tarball in
embed-less-npm-dist-tar branch of rainloop in salsa, so reassigning
back to rainloop.
[05:52:23] Finished
On Fri, Jun 5, 2020 at 11:36 am, Pirate Praveen
wrote:
I have reproduced the same error with less npm dist tarball in
embed-less-npm-dist-tar branch of rainloop in salsa, so reassigning
back to rainloop.
[05:52:23] Finished 'lightgalleryFontsCopy' after 497 ms
[05:52:23] Finished
Control: reassign -1 rainloop
Control: retitle -1 rainloop ftbfs with node-less 3.11.2 in experimental
On Wed, Jun 3, 2020 at 1:27 am, Pirate Praveen
wrote:
We could try building rainloop with npm version of less 3.11.2 to
confirm if it is rainloop that needs updating or less that needs
On 2020, മേയ് 21 1:08:32 PM IST, Pirate Praveen
wrote:
>
>
>On 2020, മേയ് 21 2:34:43 AM IST, Xavier wrote:
>>Hi all,
>>
>>here is the current result given by dak. Still to fix:
>> * libjs-webrtc-adapter
>
>This can be fixed by switching from browserif
On Wed, Jun 3, 2020 at 12:29 am, Pirate Praveen
wrote:
On Tue, Jun 2, 2020 at 10:33 pm, Pirate Praveen
wrote:
I'm trying to close the gap between upstream build and our builds by
using rollup to generate cjs file as well, but build fails with
this error.
/usr/bin/node -e
On Tue, Jun 2, 2020 at 10:33 pm, Pirate Praveen
wrote:
I'm trying to close the gap between upstream build and our builds by
using rollup to generate cjs file as well, but build fails with this
error.
/usr/bin/node -e require\(\"./.\"\)
/home/pravi/forge/js-team/le
On Tue, Jun 2, 2020 at 6:56 pm, Pirate Praveen
wrote:
Control: tags -1 help
Hi Daniel,
Would it be possible to skip using gulp-less and use lessc command
directly, like I did in node-katex (skipped less-loader and used
lessc command) ?
See the following commands,
https
Control: tags -1 help
Hi Daniel,
Would it be possible to skip using gulp-less and use lessc command
directly, like I did in node-katex (skipped less-loader and used lessc
command) ?
See the following commands,
at 4:30 pm, Pirate Praveen
wrote:
While at it, please also use components via watch + uscan or add them
to debian/build_modules (both of the moethods will have the modules
linked to node_modules directory during build when pkg-js-tools is
used) so we can easily track their versions and update
While at it, please also use components via watch + uscan or add them
to debian/build_modules (both of the moethods will have the modules
linked to node_modules directory during build when pkg-js-tools is
used) so we can easily track their versions and update them when
required. Currently we
Package: rainloop
Version: 1.14.0-1
Severity: important
rainloop ftbfs with node-less 3.11.1 currently in experimental.
[18:45:47] 'cssMainBuild' errored after 4.15 s
[18:45:47] TypeError: less.render is not a function
at DestroyableTransform._transform
(/<>/debian/build/gulp-less.js:39:10)
On Mon, Jun 1, 2020 at 10:04 pm, Jonas Smedegaard
wrote:
Sorry for my lack of response!
Please remove me as uploader and take over maintenance of the
package: I
no longer have any special interest in it.
Thanks for the reply and maintianing it till now. I will remove you as
uploader
On 2020, മേയ് 20 1:21:55 AM IST, Pirate Praveen
wrote:
>
>
>On Wed, May 20, 2020 at 12:41 am, Pirate Praveen
> wrote:
>> After adding node-clone dependency to node-less, all rebuilds passed.
>
>With manpage added, umd/browser file generated properly and minifie
Control: forwarded -1 https://github.com/LeoIannacone/npm2deb/issues/84
On Sat, May 30, 2020 at 6:13 pm, Wookey wrote:
Package: npm2deb
Version: 0.3.0-4
Severity: important
Running npm2deb create npm-run
produced:
node-npm-run and node-npm-run-5.0.1
node-npm-run-5.0.1 contained the module
On Mon, May 25, 2020 at 10:51 am, Jérémy Lal
wrote:
It's ready to be built, but not ready to go in testing:
https://buildd.debian.org/status/package.php?p=nodejs=experimental
- amd64 some tests won't pass because of network issues
I never figured why some build servers fail on this, and
Most of the times upstreams don't support packaging, but some of them (rarely)
do ask what they can do make our life easier. So I noted down some points here.
Please contribute.
https://wiki.debian.org/Javascript/Nodejs/BestUpstreamPractices
--
Sent from my Android device with K-9 Mail. Please
On 2020, മേയ് 21 2:34:43 AM IST, Xavier wrote:
>Hi all,
>
>here is the current result given by dak. Still to fix:
> * libjs-webrtc-adapter
This can be fixed by switching from browserify-lite to webpack (or possibly
rollup too which is lighter than webpack). I have a proof of concept commit in
Control: block -1 by 961005
This is fixed in git along with update to 0.10.2 but blocked by
node-less (need new upstream version).
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
On Wed, May 20, 2020 at 11:03 am, Xavier wrote:
Le 20/05/2020 à 10:53, Pirate Praveen a écrit :
Package: pkg-js-tools
Version: 0.9.36
Severity: wishlist
Currently we use debian/build_modules to add build only modules, but
that is manual and we cannot use uscan like other components
Package: pkg-js-tools
Version: 0.9.36
Severity: wishlist
Currently we use debian/build_modules to add build only modules, but
that is manual and we cannot use uscan like other components. Can we
add an option to watch file to specify a component is build-only and
need not be installed in the
Control: tags -1 pending
Control: block -1 by 961005
This is ready in git with new upstream version, but needs new version
of node-less and node-mini-css-extract-plugin from NEW. If you are keen
to test it right now, you can get the deb from
https://people.debian.org/~praveen/new/
--
On Wed, May 20, 2020 at 12:24 am, Pirate Praveen
wrote:
I tested the reverse (build) dependencies and this is the result.
raintpl and webassets did not have any autopkgtests defined.
node-bootstrap-tour, searx, roundcube and roundcube-plugins-extra
rebuild failed - missing dependency
On Tue, May 19, 2020 at 8:05 pm, Pirate Praveen
wrote:
Finally managed to build less.js 3.11 with babeljs and pushed it to
master-3 and upstream-3 branches. This branch is just a proof of
concept at this point. You can adapt and test/imporve it further.
I was able to successfully build
Control: retitle -1 node-ignore: Build with babel version 7
Control: fixed -1 5.1.4-5
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
with node-less built from salsa master-3 branch and
node-mini-css-extract-plugin from NEW, node-katex 0.10 is ready in
salsa master. Once these blockers are cleared node-katex can be
uploaded.
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
On Tue, May 19, 2020 at 7:25 pm, Pirate Praveen
wrote:
I'm trying to build 3.11.1 version (latest) but the build system
seems unnecessarily complicated. They have a Gruntfile but is not
easily clear how to run just the build task (gulp dist looked like
the answer but it did not really work
On Tue, May 19, 2020 at 2:12 pm, Pirate Praveen
wrote:
On Tue, May 19, 2020 at 2:03 pm, Pirate Praveen
wrote:
Only image-size is missing from runtime dependencies,
image-size 0.5.0 seems a simple module that can be embedded (newer
versions use typescript and needs build).
I'm
On Tue, May 19, 2020 at 2:03 pm, Pirate Praveen
wrote:
Only image-size is missing from runtime dependencies,
image-size 0.5.0 seems a simple module that can be embedded (newer
versions use typescript and needs build).
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth
On Tue, May 19, 2020 at 1:40 pm, Pirate Praveen
wrote:
I'm trying to update node-katex to 0.10 and it needs less 3.9.0 (at
least)
Only image-size is missing from runtime dependencies, and probably some
of the missing build dependencies (*eslint*, grunt-* could be ignored
for now, those
Package: node-katex
Version: 0.8.3+dfsg-2
Severity: wishlist
Control: block -1 by 960300
Control: block -1 by 960944
Control: block -1 by 805289
I have started the work in salsa master. It needs
node-mini-css-extract-plugin, node-less-loader both in NEW and a newer
version node-less (at least
I'm trying to update node-katex to 0.10 and it needs less 3.9.0 (at
least)
When building with current version of less, it gives the following error
+ lessc ./src/katex.less
TypeError: sys.print is not a function
at /usr/lib/nodejs/less/bin/lessc:384:25
at tree.importVisitor.finish [as
On 2020, മേയ് 18 5:34:41 PM IST, Pirate Praveen
wrote:
>
>
>On Sat, May 16, 2020 at 8:39 pm, Daniel Ring wrote:
>> I updated the Rainloop package on Salsa; please take a look at it,
>> and sponsor an upload to the archive if you think it's ready.
>>
>
>Th
On Sun, May 17, 2020 at 9:29 pm, Xavier wrote:
Control: blocked -1 by 952335
Hi all,
node-babel7 7.9.6 seems ready but it needs node-commander 4.
node-commander upgrade is blocked by #952335 (uglify-js needs
node-commander 2)
Can we upload this to experimental till uglify-js is fixed in
Package: npm2deb
Version: 0.3.0-4
Severity: important
$ npm2deb create less-loader@4.0
Traceback (most recent call last):
File "/usr/bin/npm2deb", line 7, in
sys.exit(main(sys.argv))
File "/usr/lib/python3/dist-packages/npm2deb/scripts.py", line 157,
in main
args.func(args)
File
On Sat, May 16, 2020 at 8:39 pm, Daniel Ring wrote:
I updated the Rainloop package on Salsa; please take a look at it,
and sponsor an upload to the archive if you think it's ready.
Thanks for the fix, I have uploaded it.
The previous version became unbuildable as its dependencies were
https://salsa.debian.org/js-team/node-clone/-/blob/master/clone.js#L109
I think we may need to embed older version of buffer module in
node-libs-browser
For this particular case you can try embedding buffer module version 4.x as
browsers need an equivalent module to features present only in
On Sun, May 17, 2020 at 1:02 am, Pirate Praveen
wrote:
On Sun, May 17, 2020 at 12:40 am, Pirate Praveen
wrote:
okay, not there fully. It was still using
babel-plugin-transform-strict-mode from babel 6
I pushed my changes to master branch and now autopkgtest fails
autopkgtest [19:30
On Sun, May 17, 2020 at 12:40 am, Pirate Praveen
wrote:
okay, not there fully. It was still using
babel-plugin-transform-strict-mode from babel 6
I pushed my changes to master branch and now autopkgtest fails
autopkgtest [19:30:29]: test yarn: [---
yarn install v1.22.4
On Sun, May 17, 2020 at 12:24 am, Pirate Praveen
wrote:
Control: tags -1 pneding
On Sat, May 16, 2020 at 11:59 pm, Pirate Praveen
wrote:
On Sat, May 16, 2020 at 11:48 pm, Pirate Praveen
wrote:
The author of the plugin suggests using another plugin from babel 7,
but that did
Control: tags -1 pneding
On Sat, May 16, 2020 at 11:59 pm, Pirate Praveen
wrote:
On Sat, May 16, 2020 at 11:48 pm, Pirate Praveen
wrote:
The author of the plugin suggests using another plugin from babel 7,
but that did not work.
https://github.com/zertosh/babel-plugin-transform-inline
On Sat, May 16, 2020 at 11:48 pm, Pirate Praveen
wrote:
On Thu, May 14, 2020 at 3:12 pm, Pirate Praveen
wrote:
$ yarnpkg
/usr/share/nodejs/@babel/runtime/helpers/inherits.js:5
throw new TypeError("Super expression must either be null or a
function");
^
TypeEr
On Thu, May 14, 2020 at 3:12 pm, Pirate Praveen
wrote:
$ yarnpkg
/usr/share/nodejs/@babel/runtime/helpers/inherits.js:5
throw new TypeError("Super expression must either be null or a
function");
^
TypeError: Super expression must either be null or a function
at _inher
Package: node-babel
Version: 6.26.0+repack-4
Severity: serious
Control: block -1 by 960120
Control: block -1 by 959798
Control: block -1 by 960021
src:node-babel (babel 6.x) is replaced by src:node-babel7 (babel 7.x)
and src:node-babel should not be part of bullseye.
The status of this
On Sun, May 10, 2020 at 12:35 am, Pirate Praveen
wrote:
More todo: 11 runtime reverse dependencies of node-babel 7 (some of
them could be removed). 5 reverse build dependencies of node-babylon
and 5 reverse build dependencies for
node-babel-plugin-add-module-exports.
I think we are just
On Thu, May 14, 2020 at 5:30 pm, Jonas Smedegaard
wrote:
No, fails.
The package now checks unit tests during build, and switching to
Babel 7
causes one of those to fail:
not ok 69 Log suppression "before each" hook for "does not call
console.log by default"
Cannot find module ./utils
On Thu, May 14, 2020 at 5:58 pm, Pirate Praveen
wrote:
On Thu, May 14, 2020 at 1:38 pm, Xavier wrote:
Le 14/05/2020 à 13:36, Xavier a écrit :
Le 14/05/2020 à 13:28, Xavier a écrit :
Hi,
looking at node-es6-promise: problem is not in reverse
dependencies but
in node-es6
On Thu, May 14, 2020 at 1:38 pm, Xavier wrote:
Le 14/05/2020 à 13:36, Xavier a écrit :
Le 14/05/2020 à 13:28, Xavier a écrit :
Hi,
looking at node-es6-promise: problem is not in reverse
dependencies but
in node-es6-promise itself:
`require("es6-promise").Promise` is undefined
On Thu, May 14, 2020 at 1:12 pm, Jonas Smedegaard
wrote:
retitle -1 libjs-webrtc-adapter: Build with babel version 7
tags -1 +help -patch
Quoting Pirate Praveen (2020-05-05 15:11:31)
I'm planning to upload node-grunt-babel 8.0 in unstable (it is in
experimental currently). I have fixed
$ yarnpkg
/usr/share/nodejs/@babel/runtime/helpers/inherits.js:5
throw new TypeError("Super expression must either be null or a
function");
^
TypeError: Super expression must either be null or a function
at _inherits
(/usr/share/nodejs/@babel/runtime/helpers/inherits.js:5:11)
at
Package: src:acorn
Version: 6.2.1+ds+~cs11.24.3-2
Severity: important
Control: block 960433 by -1
We'd like to remove src:node-babel from the archive in favor of
src:node-babel7. [1]
node-babel-helper-builder-react-jsx - BLOCKED by
node-babel-plugin-transform-react-jsx
On Tue, May 12, 2020 at 2:25 pm, Xavier wrote:
Le 12/05/2020 à 13:06, Pirate Praveen a écrit :
On Tue, May 12, 2020 at 10:58 am, Xavier wrote:
I fixed it using a simple buffer.js which requires node's
"buffer". Now
build is OK but simple "require" test warns:
On Tue, May 12, 2020 at 10:58 am, Xavier wrote:
I fixed it using a simple buffer.js which requires node's "buffer".
Now
build is OK but simple "require" test warns:
I think we will have to tell webpack to use
https://www.npmjs.com/package/buffer module here.
Package: pkg-js-tools
Version: 0.9.35
Severity: important
I think git stash before adding component should be tried only when
there is uncommitted changes.
$ add-node-component -ifu babel-plugin-version-inline
Components added: babel-plugin-version-inline
add-node-component: Newest version of
On 2020, മേയ് 12 4:06:33 AM IST, Xavier wrote:
>ERROR in ./src/crypto/aes.js
>Module not found: Error: Can't resolve './../../buffer' in
>'/<>/src/crypto'
> @ ./src/crypto/aes.js 1:0-25
> @ ./src/crypto/SecretStorage.js
> @ ./src/crypto/index.js
> @ ./src/client.js
> @ ./src/matrix.js
> @
On Mon, May 11, 2020 at 2:27 pm, Xavier wrote:
I fixed partially node-matrix-js-sdk but I failed to configure
debian/webpack.config.js. So node-* is ready but not libjs-*
Can someone take a look ?
Did you include this patch?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933662
--
On Mon, May 11, 2020 at 5:27 pm, Pirate Praveen
wrote:
On Mon, May 11, 2020 at 11:55 am, Pirate Praveen
wrote:
With babel 6, they use node-babel-preset-stage-0 which is not
available in babel 7, we need to specify the plugins from that
preset explicitly.
btw this works with nodejs
On Mon, May 11, 2020 at 11:55 am, Pirate Praveen
wrote:
With babel 6, they use node-babel-preset-stage-0 which is not
available in babel 7, we need to specify the plugins from that preset
explicitly.
btw this works with nodejs 12 from experimental
--
Pkg-javascript-devel mailing list
On 2020, മേയ് 11 2:12:08 PM IST, Xavier wrote:
>Hi,
>
>if no one disagree, I'm going to remove:
> * node-babel-preset-es2015-loose
> * node-babel-plugin-precompile-charcodes
For these two, I have filed RM already.
node-babel-plugin-transform-define - 960177
On 2020, മേയ് 11 2:19:01 AM IST, Xavier wrote:
>Le 10/05/2020 à 21:23, Pirate Praveen a écrit :
>>
>>
>> On Sat, May 9, 2020 at 10:54 pm, Xavier wrote:
>>> Thanks for your awesome work!
>>
>> Thanks to you, Jonas and Nilesh too for helping.
>
On Sat, May 9, 2020 at 10:54 pm, Xavier wrote:
Thanks for your awesome work!
Thanks to you, Jonas and Nilesh too for helping.
Can somoene check babel7 branch in node-yarnpkg? It builds fine but I
probably need to include some specific plugins from stage-0 preset. It
builds fine, but when
Control: severity -1 serious
Raising severity since it ftbfs in unstable now.
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
On Wed, May 6, 2020 at 8:26 pm, Pirate Praveen
wrote:
You can see the status on migration at
https://wiki.debian.org/Javascript/Nodejs/Transitions/Babel7
Roughly 33 of them are reverse build dependencies of
node-rollup-plugin-babel, node-gulp-babel, node-grunt-babel and
node-babel-loader
On Sat, May 9, 2020 at 9:30 pm, Pirate Praveen
wrote:
With node-babel-loader >= 8.0 in experimental, build fails with
node ./scripts/build-webpack.js
Unhandled rejection TypeError: fileDependencies.map is not a function
It seems this failure is already present in the current version,
Package: node-yarnpkg
Version: 1.22.4-3
Severity: important
Similar to #958780,
With node-babel-loader >= 8.0 in experimental, build fails with
node ./scripts/build-webpack.js
Unhandled rejection TypeError: fileDependencies.map is not a function
at compiler.run
Control: reopen -1
On Sat, May 9, 2020 at 2:39 pm, Debian Bug Tracking System
wrote:
Your message dated Sat, 09 May 2020 14:37:31 +
with message-id
and subject line Bug#960101: fixed in node-jsonld 1.6.2-4
has caused the Debian Bug report #960101,
regarding node-jsonld,
Package: node-jsonld,node-rdf-canonize
Severity: important
Hi Jonas,
Babel 6 will be replaced by Babel 7 (node-babel7) in bullseye. So
please update your package to build with Babel 7.
Please build depend on node-babel-loader (>= 8.0~) which depends on
node-babel7 and drop all other current
On Sat, May 9, 2020 at 1:47 pm, Jonas Smedegaard wrote:
Yes, my mistake: ESLint build-depend on (and suggest)
node-babel-code-frame (not node-babel-eslint).
Question remain: How is ESLint affected by the babel transition?
We cannot remove node-babel 6 from the archive until eslint remove
On Sat, May 9, 2020 at 1:24 pm, Jonas Smedegaard wrote:
Quoting Pirate Praveen (2020-05-09 13:08:28)
Babel 6 will be replaced by Babel 7 (node-babel7) in bullseye. So
please update your package to build with Babel 7.
ESLint does not depend or build-depend on babel.
It does build-depend
Package: eslint
Version: 5.16.0~dfsg-4
Severity: important
Hi Jonas,
Babel 6 will be replaced by Babel 7 (node-babel7) in bullseye. So
please update your package to build with Babel 7.
Current status of this transition is at
https://wiki.debian.org/Javascript/Nodejs/Transitions/Babel7
As
Package: node-trust-json-document
Version: 0.1.4~dfsg-5
Severity: important
Hi Jonas,
Babel 6 will be replaced by Babel 7 (node-babel7) in bullseye. So
please update your package to build with Babel 7.
Current status of this transition is at
Package: jsbundle-web-interfaces
Version: 1.1.0+~2.0.1~ds+~6.0.0+~0~20180821-1
Severity: important
Hi Jonas,
Babel 6 will be replaced by Babel 7 (node-babel7) in bullseye. So
please update your package to build with Babel 7.
Current status of this transition is at
Package: node-ignore
Version: 5.1.4-4
Severity: important
Hi Daniel,
Babel 6 will be replaced by Babel 7 (node-babel7) in bullseye. So
please update your package to build with Babel 7.
node-babel-plugin-transform-decorators-legacy is not required in babel
7 as noted by upstream readme =>
Package: node-ignore
Version: 5.1.4-4
Severity: important
Hi Jonas,
Babel 6 will be replaced by Babel 7 (node-babel7) in bullseye. So
please update your package to build with Babel 7.
Current status of this transition is at
https://wiki.debian.org/Javascript/Nodejs/Transitions/Babel7
As
Package: node-preact
Version: 8.2.5-2
Severity: important
When this package was uploaded to archive, rollup was not packaged so
babel was used to just transpile. Now that rollup is packaged, we
should build it with rollup.
Note: We will need to package @rollup/plugin-virtual (currently it
On Wed, May 6, 2020 at 10:47 pm, Nilesh Patra
wrote:
Hi,
I needed "@types/react" for node-react-audio-player, as a part of
babel-loader transitions.
I added that in and ran the debian/get-orig-source.sh script.
This downloaded a few new versions, all of which have been updated in
Package: node-webpack-merge
Version: 2.2.0-3
Severity: important
Control: tags -1 patch
Babel 6 will be replaced by Babel 7 (node-babel7) in bullseye. I have
fixed this package to build with babel 7 in babel7 branch.
hi team,
We now have babel 7 in bullseye and babel 6 is already unmaintained
upstream. So I'd like to remove babel 6 from the archive. For this, we
need to port all packages currently build depending on babel 6 to build
with babel 7.
You can see the status on migration at
Control: severity -1 serious
As discussed in irc, node-grunt-babel 8.0 is in unstable now.
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Package: libjs-webrtc-adapter
Version: 7.5.1~ds-1
Severity: important
Control: tags -1 patch
Hi Jonas,
I'm planning to upload node-grunt-babel 8.0 in unstable (it is in
experimental currently). I have fixed all the reverse build
dependencies and this is the only remaining blocker. I have
On Mon, May 4, 2020 at 9:52 am, Xavier wrote:
# BUILD MODULES
Additional needed build modules:
* @rollup/plugin-json
* @rollup/
Why? Can't we use the packaged versions and adapt rollup.config.js?
* browserify-fs
* buffer-es6
* jest-worker
* process-es6
* rollup-plugin-node-builtins
I don't think removing nodejs dependency when there is a command
interface is policy compliant. In case of pure libraries it is a not a
problem since the application that depends on the library will have a
dependency on nodejs. But in this case, pegjs command will not work
without nodejs
301 - 400 of 992 matches
Mail list logo
