On 2020, സെപ്റ്റംബർ 21 3:37:01 AM IST, Jonas Smedegaard wrote:
>> I think we should create a release team within js team to handle it
>> like how release team works for transitions.
>
>What do you mean more concretely?
>
>That only a smaller elite group should (approve) upload to unstable, and
On 2020, ഒക്ടോബർ 25 10:09:13 AM IST, Debian testing watch
wrote:
>FYI: The status of the node-rollup-plugin-inject source package
>in Debian's testing distribution has changed.
>
> Previous version: (not in testing)
> Current version: 4.0.2+~3.0.2-1
Are we going to maintain legacy
[Adding pkg-javascript-devel list]
On 2020, ഒക്ടോബർ 26 12:14:08 AM IST, Daniel Leidert
wrote:
>Hi,
>
>the jekyll build fails at the moment because livereload.js created in the
>override_dh_auto_build target is not created. The creation prints some
>warnings:
>
>> make[1]: Entering directory
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
--+
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-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
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:
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:
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 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 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 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
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, ജൂൺ 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
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 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
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 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
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, ജൂൺ 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, മേയ് 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
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 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
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 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 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 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 2020, ജൂലൈ 17 12:12:09 PM IST, Adrian Bunk wrote:
>Source: node-rollup-plugin-buble
>Version: 0.19.8-2
>Severity: serious
>Tags: ftbfs
>Control: block 960748 by -1
>
>node-rollup-plugin-buble build depends on the babeljs provides
>that will not be in bullseye due to #960748.
I think we
On Sun, Jul 26, 2020 at 19:35, Adrian Bunk wrote:
On Sun, Jul 26, 2020 at 09:55:47PM +0530, Pirate Praveen wrote:
I'm wondering if this will require another bootstraping cycle as
node-babel7
autopkgtest is also broken and it depends on itself.
If the problem is in node-lodash and gets
I'm wondering if this will require another bootstraping cycle as
node-babel7 autopkgtest is also broken and it depends on itself.
--
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 Sun, Jul 26, 2020 at 22:24, Pirate Praveen
wrote:
Babel build situation is indeed a mess.
It is even worse than I estimated. We can no longer build it with npm
DEB_BUILD_PROFILES=pkg.node-babel7.npm sbuild
...
HOME=`pwd` npm i
npm ERR! code EUNSUPPORTEDPROTOCOL
npm ERR! Unsupported
On Thu, Jul 23, 2020 at 21:10, Thorsten Alteholz
wrote:
Hi,
according to LICENSE the copyright holder is "JS Foundation and other
contributors".
Probably upstream can shed some light on this.
Fixed an reuploaded. npm2deb takes Author in package.json as copyright
holder by default,
On 2020, ജൂലൈ 27 1:42:32 AM IST, Nicolas Mora wrote:
>I'm not sure yet if this would fix the bug but in all the build log
>errors, I see that the file /usr/share/nodejs/lodash/_baseOrderBy.js is
>always the source of the error.
>
>The file _baseOrderBy.js in the package seems buggy for an
Control: reopen -1
On Mon, Jul 27, 2020 at 00:32, Pirate Praveen
wrote:
This did not fix the issue :( So we have to reopen this bug once the
upload reaches the archive (which will close this bug as fixed).
Thanks to the brave new world of embedding eveything and reducing the
number of js
On Sun, Jul 26, 2020 at 22:43, Pirate Praveen
wrote:
On Sun, Jul 26, 2020 at 22:24, Pirate Praveen
wrote:
Babel build situation is indeed a mess.
It is even worse than I estimated. We can no longer build it with npm
DEB_BUILD_PROFILES=pkg.node-babel7.npm sbuild
...
HOME=`pwd` npm i
On 2020, ജൂലൈ 12 11:30:09 AM IST, Sean Whitton
wrote:
>
>+--+
>| REJECT reasoning |
>+--+
>
>test/fixtures/commonmark/spec.txt is under a different license.
Fixed and reuploaded.
>+--+
>|Other comments|
Control: forwarded -1
https://github.com/lodash-archive/lodash-cli/pull/141
On Sun, Jul 26, 2020 at 16:12, Nicolas Mora
wrote:
I'm not sure yet if this would fix the bug but in all the build log
errors, I see that the file /usr/share/nodejs/lodash/_baseOrderBy.js
is
always the source of
Package: node-postcss-filter-plugins
Version: 2.0.2-3
Severity: serious
autopkgtest fails with stderr output
postcss.plugin was deprecated. Migration guide:
https://evilmartians.com/chronicles/postcss-8-plugin-migration
This was reported on the team mailing list [1] and tracked in postcss 8
Package: pkg-js-tools,node-css-loader
Severity: wishlist
node-css-loader autopkgtest fails because of a deprecation warning in
stderr. In manual autopkgtest, we can easily add Restrictions:
allow-stderr, provide a way to pass this to autopkgtest-pkg-nodejs
tests too.
--
Pkg-javascript-devel
Package: node-rollup-plugin-node-resolve
Version: 10.0.0+repack+~4.2.4-1
severity: important
At least autoprefixer-rails build is broken with version 10.
https://github.com/ai/autoprefixer-rails/pull/200#issuecomment-751924645
Probably more builds are silently broken.
While at it, I think we
On Tue, Dec 29, 2020 at 20:02, Ben Finney wrote:
Control: found -1 webpack/4.43.0-6
On 16-Jun-2020, Ben Finney wrote:
On 18-May-2020, Pirate Praveen wrote:
>
https://salsa.debian.org/js-team/node-clone/-/blob/master/clone.js#L109
> I think we may need to embed older version of
Control: reassign -1 node-css-loader
Control: retitle -1 autopkgtest regression due to stderr
On Sat, Dec 26, 2020 at 10:50, Xavier wrote:
Le 26/12/2020 à 10:45, Pirate Praveen a écrit :
Package: pkg-js-tools,node-css-loader
Severity: wishlist
node-css-loader autopkgtest fails because
On Fri, 25 Dec 2020 20:58:20 +0530 Pirate Praveen
wrote:
> Now with updated @rollup/plugin-node-resolve
>
> (debian-sid)pravi@ilvala2:~/forge/js-team/autoprefixer-rails-10.1.0.0/build$
> yarnpkg upgrade @rollup/plugin-node-resolve@^10.0.0
> yarn upgrade v1.22.10
> [1/4]
Hi,
I'd like to remove embedded copy of rollup-plugin-node-resolve from
bullseye and port all modules to use @rollup/plugin-node-resolve
I have rebuilt all the reverse dependencies and you can see the list of
packages that failed at
On Wed, Jan 6, 2021 at 7:54 pm, Pirate Praveen
wrote:
I'm trying to build corepack and it is progressing well. We will need
to package some dependencies (clipanion, terser-webpack-plugin,
ts-loader etc). I will report how it goes as I make progress.
Good news. I got a working yarn 2 build
Package: node-lodash
Version: 4.17.20+dfsg+~cs8.31.172-1
Severity: important
Control: affects -1 gitlab
Control: tags -1 help
gitlab package from salsa master-13.5 branch fails with this error
during installation.
ERROR in
/environments/components/environments_table.vue?vue=script=js&
On Mon, 23 Nov 2020 12:11:25 +0100 Xavier wrote:
> Control: tags -1 + moreinfo
>
> Hi,
>
> I'm unable to reproduce this bug after many tries
>
>
DEB_BUILD_PROFILES=nocheck sbuild
is failing for node-vinyl-fs in sid as well.
--
Pkg-javascript-devel mailing list
On Sun, Dec 6, 2020 at 11:37, Jonas Smedegaard wrote:
Sorry, I was unclear. Let me try rephrase to clarify:
ftpmaster strongly dislikes (i.e. they will reject) too tiny source
packages, but ftpmaster does not actively encourage (even if they
might
tolerate) duplicate code.
My point was
On Thu, Dec 3, 2020 at 11:53, Jonas Smedegaard wrote:
Please use Debbugs...
Debian has an issue tracker called debbugs. Despite its name it can
also track other kinds of issues than bugs, including the interest and
eventual preliminary work preparing a new package, before the package
is
On Tue, 01 Dec 2020 00:39:18 +0530 Pirate Praveen
wrote:
>
>
> On Tue, Dec 1, 2020 at 00:28, Pirate Praveen
> wrote:
> >
> >
> > On Mon, Nov 30, 2020 at 19:46, Paolo Greppi
> > wrote:
> >> The resulting package was not installable due to
n
Control: fixed -1 1.22.4-4
On Mon, 09 Nov 2020 22:00:53 +0530 Pirate Praveen
wrote:
> This is caused by node-mkdirp transition, but node-yarnpkg is ftbfs
currently (caused by node-babel/node-babel7 transition) which makes it
hard to fix.
Fixed in last uplod.
--
Pkg-javascript-de
Control: fixed -1 1.22.4-4
On Tue, 27 Oct 2020 07:41:34 +0100 Xavier wrote:
> migration from mkdirp 0.53 to 1.0.x is easy but I'm not able to patch
> yarnpkg since build already fails for some babel reasons.
This is fixed in the last upload, though we need to build it using
On Thu, 12 Nov 2020 16:25:14 +0100 Xavier Guimard
wrote:
> node-uuid breaks dependent package with error like:
>
> Package subpath './v1' is not defined by "exports" in
/usr/share/nodejs/uuid/package.json
>
> (same error with any of v{1,2,3,4}.js)
I have seen similar error in gitlab as
On Mon, 07 Dec 2020 18:25:26 +0530 Pirate Praveen
wrote:
> I suspect this is caused when a package is expecting an older version
> of uuid, for example node-copy-webpack-plugin, which expects uuid
3.x.
I think uuid itself had a bug, with uuid 8.3.1, I don't see this issue
now.
Control: reassign -1 node-copy-webpack-plugin
On Sun, 12 Jul 2020 15:43:19 +0530 Pirate Praveen
wrote:
> I tried fixing this in babel6 branch (as master is broken - I found
it
> broke after merging babel 7 branch), but autopkgtest still fails with
> the same error. Can you che
Control: reopen -1
Control: reassign -1 gitlab
On Mon, 07 Dec 2020 13:49:55 + Debian FTP Masters
wrote:
> Source: node-copy-webpack-plugin
> Source-Version: 5.1.2+~cs9.0.2-2
> Done: Pirate Praveen
>
> We believe that the bug you reported is fixed in the latest version
On Mon, 07 Dec 2020 23:00:56 +0530 Pirate Praveen
wrote:
> So if we fix node-request to work with newer uuid or probably remove
> the dependency on node-request in yarnpkg, I hope we can fix this
issue.
I have fixed node-request to work with uuid 8.x API and yarnpkg is
fixed now.
Control: reassign -1 node-request
Control: fixed -1 2.88-5
On Mon, Dec 7, 2020 at 23:27, Pirate Praveen
wrote:
On Mon, 07 Dec 2020 23:00:56 +0530 Pirate Praveen
wrote:
> So if we fix node-request to work with newer uuid or probably remove
> the dependency on node-request in yarnpkg,
On Thu, Dec 3, 2020 at 19:17, Jonas Smedegaard wrote:
My understanding is that ftpmasters dislike small *source* packages.
Small source packages is a burden in *every* package tracking in
Debian.
Small binary packages is also a burden in *some* package tracking.
Zero-size binary packages
Control: reopen -1
Control: reassign -1 gitlab
On Thu, Dec 3, 2020 at 10:14, Xavier wrote:
Does gitlab use `npm install` ? If so, we just have to fix
node-compression-webpack-plugin/package.json
This is indeed caused by mix of schema-utils 2 and 3. Version 2 is
pulled by yarn and version 3
On 2020, ഡിസംബർ 3 10:03:18 PM IST, Xavier wrote:
>I'm not in favor of your proposal: if I need a node-very-few-module
>which is provided by a package with many dependencies, I'm not happy to
>depend on it. To apply that, we should then choose with precaution in
>which package we will embed each
Package: pkg-js-tools
Version: 0.9.53
Severity: wishlist
It would be nice to have a test in pkg-js-tools to make sure the
dependencies mentioned in package.json of a module is not differing by
a major version.
Example node-css-loader. See
package: pdf.js
version: 2.6.347+dfsg-2
severity: wishlist
There is a node module pdfjs-dist
https://www.npmjs.com/package/pdfjs-dist which includes a prebuilt
version of pdf.js. gitlab needs this (currently it is pulled from
npmjs.com via yarn), so it would be good if pdfjs-dist can be
hi,
I have fixed node-request to work with node-uuid 8 API and it also
fixed yarnpkg/gitlab. I'd like to upload node-uuid 8.x to unstable in
the coming days. Help is welcome to ensure every package is fixed with
this version. Please see the patch in node-request for how to do it.
Also uuid 8
On 2020, ഡിസംബർ 8 10:53:26 AM IST, Andrius Merkys wrote:
>Hello,
>
>On 2020-12-07 20:46, Pirate Praveen wrote:
>> I have fixed node-request to work with node-uuid 8 API and it also fixed
>> yarnpkg/gitlab.
>
>Does this mean node-request is going to be part of bull
On Tue, Dec 8, 2020 at 00:16, Pirate Praveen
wrote:
I think we should also rebuild reverse dependencies too,
I did a rebuild and here is the results,
rebuild node-ajv-keywords... PASS
autopkgtest node-redis ... PASS
autopkgtest node-request
On Tue, Dec 8, 2020 at 13:45, Jonas Smedegaard wrote:
Thanks for raising that concern, Andrius.
An RC bug has already been filed for that purpose, however:
bug#956423.
I did not see an auto removal notice against it at tracker.debian.org
so I thought the severity might be lower than rc.
Package: node-fastcgi
Version: 1.3.3-3
Severity: important
Control: block 956423 by -1
Control: tags -1 patch
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './v4' is not
defined by "exports" in /usr/share/nodejs/uuid/package.json
Full log attached.
This is caused by embedded copy of
On Tue, Dec 8, 2020 at 19:44, Pirate Praveen
wrote:
autopkgtest node-copy-webpack-plugin ... FAIL
rebuild node-copy-webpack-plugin ... FAIL
rebuild node-fastcgi ... FAIL
rebuild node-http-signature ... FAIL
autopkgtest node-node-rest-client... FAIL
On Tue, Nov 24, 2020 at 13:32, Mattia Rizzolo wrote:
Just a note:
On Tue, Nov 24, 2020 at 04:55:02PM +0530, Pirate Praveen wrote:
DEB_BUILD_PROFILES=nocheck sbuild
If you sepcify nocheck in _PROFILES you also *MUST* specify nocheck in
_OPTIONS. See the relevant line in
https
On Wed, Dec 9, 2020 at 18:24, Debian FTP Masters
wrote:
There was an uncaught exception when processing your upload:
Traceback (most recent call last):
File "/srv/ftp-master.debian.org/dak/daklib/archive.py", line 109,
in _install_file
On Mon, Nov 30, 2020 at 19:35, Jonas Smedegaard wrote:
Btw, it seems you need to push latest changes to git for yarnpkg
The recent changes are in master-1 branch as we could not fix the
master branch (attempted to build with babel 7 without success).
--
Pkg-javascript-devel mailing list
On Mon, Nov 30, 2020 at 18:32, Jonas Smedegaard wrote:
Package: yarnpkg
Version: 1.22.4-4
Severity: grave
Justification: renders package unusable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
yarnpkg depends on node-node-uuid.
node-node-uuid was deprecated 2 yars ago, replaced by
On Tue, Dec 1, 2020 at 00:28, Pirate Praveen
wrote:
On Mon, Nov 30, 2020 at 19:46, Paolo Greppi
wrote:
The resulting package was not installable due to node-babel-runtime
missing from testing
May be we can add babel-runtime as a component? (it is going to
contrib anyway)
Or see
On Mon, Nov 30, 2020 at 19:46, Paolo Greppi
wrote:
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
Package: node-compression-webpack-plugin
Version: 3.0.1-3
Severity: serious
Control: affects -1 gitlab
Installation of gitlab started failing with the following error. I
think this is related to the recent update of node-schema-utils.
Webpacking...
On Thu, Dec 3, 2020 at 10:14, Xavier wrote:
_schemaUtils.validate *is* a function when using schema-utils ≥
3.
Problem is probably somewhere else
Does gitlab use `npm install` ? If so, we just have to fix
node-compression-webpack-plugin/package.json
yes, it uses yarnpkg install. Can
On Thu, Dec 3, 2020 at 10:13, Xavier wrote:
_schemaUtils.validate *is* a function when using schema-utils ≥ 3.
Problem is probably somewhere else
I think it is because css-loader is installed from npm which would pull
node-schema-loader 2.x. I could not get node-css-loader working last
On Thu, 19 Nov 2020 23:50:24 +0530 Pirate Praveen
wrote:
>
>
> On Thu, Nov 19, 2020 at 18:58, Xavier wrote:
> > we opened bugs to upstream repo and are waiting for...
>
> I don't think upstream will make any significant changes to 1.x
branch
> any more. Someone who wa
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/20200502T085134Z sid
main' (the last version that builds in sid) and embed the built
files in
Control: reopen -1
Control: notfixed -1 1.22.4-4
On Sun, 29 Nov 2020 18:02:16 +0530 Pirate Praveen
wrote:
> I have a created a new branch master-contrib in salsa and pushed my
> changes.
> Please review the changes and if it looks good, we can upload it.
Also
> we can move thi
On Sun, 13 Dec 2020 21:30:41 +0100 Jonas Smedegaard wrote:
> It seems this package has only one reverse dependency (webpack) and
two
> reverse build-dependencies (node-chai and node-webpack).
>
> Seems it is time to replace this package with its successor,
>
Package: node-babel7
Version: 7.12.10+~cs150.141.83-1
Severity: wishlist
Currently it only has package.json in
/usr/share/nodejs/@babel/standalone
I'd like to use it for @gitlab/ui module.
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
On Fri, Dec 18, 2020 at 12:41, Xavier wrote:
Hi,
I still see one problem: yarnpkg seems to depends on
node-babel-plugin-transform-strict-mode
Thanks for checking, with
babel-plugin-transform-inline-imports-commonjs removed, we can remove
this build dependency. I will remove it in the
On Thu, 10 Dec 2020 21:22:49 +0530 Pirate Praveen
wrote:
> node-request-promise has no reverse (build) dependencies, so I think
we
> can request removal.
Filed request for removal from archive.
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://
Control: fixed -1 2.88.1-3
On Sat, 24 Nov 2018 07:26:26 +0100 Paolo Greppi
wrote:
> This package contains an embedded copy of node-uuid 3.3.2 which is
unnecessary now that we have it in the archive:
> https://packages.debian.org/sid/node-uuid
>
> The embedded copy should be removed and a
Hi,
The tests are running fine for node-vue-style-loader during build but
it fails during autopkgtest because the module is shipping esm files
directly.
It has a .babelrc file which jest uses during build to transform the
modules, but during autopkgtest, lib is a symlink to
Control: retitle -1 missing dependency node-environment-flags
Control: clone -1 -2
Control: retitle -2 node-yargs missing dependency on
node-define-property
Control: reassign -2 node-yargs
On Sun, 13 Dec 2020 02:06:42 +0530 Pirate Praveen
> When trying to run mocha using babeljs-node comm
Package: node-vue-style-loader
Version: 4.1.2-1
severity: wishlist
As continuation of
https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2020-December/048394.html
I tried running the test with babeljs-node after embedding missing
node-environment-flags in debian/test/test_modules
Package: node-babel7
Version: 7.12.9+~cs150.130.99-1
Severity: important
When trying to run mocha using babeljs-node command, it fails to find
the modules installed in global nodejs directories.
pravi@mahishi:~/forge/js-team/node-window-size$ babeljs-node
/usr/bin/mocha -R spec
Package: webpack,node-compression-webpack-plugin
Version: 4.43.0-6
Severity: serious
To reproduce this issue,
run
jest --ci test/CompressionPlugin.test.js
in node-compression-webpack-plugin
● CompressionPlugin › should work and show compress assets in stats
TypeError: callback must be a
On Wed, Dec 23, 2020 at 16:06, Jonas Smedegaard wrote:
memfs? Is Nodejs module "memfs" in Debian, or are you talking about
something else here?
memfs is used by compression-webpack-plugin for tests, but it is not
yet packaged.
--
Pkg-javascript-devel mailing list
Control: tags -1 pending
On Tue, 22 Dec 2020 16:25:36 +0100 Andreas Beckmann
wrote:
> debian/autoprefixer.js → dist/autoprefixer.js...
> [!] Error: Could not load path (imported by
./../usr/share/nodejs/postcss/lib/map-generator.js): ENOENT: no such
file or directory, open 'path'
> Error:
Package: node-schema-utils
Version: 3.0.0-3
Severity: important
schema-utils mentions "@types/json-schema": "^7.0.6" as a dependency in
its package.json but it is not available in debian.
It should probably be added to node-json-schema and added as a
dependency to node-schema-utils.
--
Control: block -1 by 977900
Control: tag 977900 help
On Sat, 19 Dec 2020 23:21:20 +0530 Pirate Praveen
wrote:
> I'd like to update css-loader to latest upstream release/postcss 8
> transition before I work on this.
node-postcss 8 transition is blocked by an ftbfs bug in
node-autopr
On Thu, Dec 24, 2020 at 19:50, Paolo Greppi
wrote:
I have run jest in the yarnpkg source tree with:
jest --ci __tests__/
You can add this to debian/tests/pkg-js/test
having this jest.config.js to disable failing tests:
and include this as a patch.
module.exports = {
testURL:
Package: node-autoprefixer
Version: 10.1.0+~cs11.3.2.0-1
Severity: wishlist
Now node-autoprefixer includes autoprefixer-rails as a component in
source package (for its build directory). We can build
ruby-autoprefixer-rails binary package from the same source and drop
libjs-autoprefixer (there
On Mon, Sep 28, 2020 at 8:01 pm, Pirate Praveen
wrote:
Hi,
I have uploaded node-postcss 8.0.5-1 to experimental.
I have started
https://wiki.debian.org/Javascript/Nodejs/Transitions/PostCSS8 to
track progress of this transition. Help is welcome.
With all reverse dependencies fixed
Control: retitle rainloop: ftbfs with node-postcss 8.0
Control: severity -1 serious
On Mon, 28 Sep 2020 21:21:26 +0530 Pirate Praveen
wrote:
>
> node-postcss 8.x will be uploaded to unstable when node-css-loader is
> ready (there is already an upstream pull request and hopef
On Fri, Dec 18, 2020 at 17:28, Jonas Smedegaard wrote:
Package: jest
Version: 26.6.3+repack+~cs61.38.31-2
Followup-For: Bug #977670
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Control: reoen -1
Control: retitle -1 jest: should explicitly (build-)depend on needed
babel modules
Thanks
701 - 800 of 992 matches
Mail list logo
