On 2021, ഫെബ്രുവരി 14 12:44:09 PM IST, Julian Gilbey wrote:
>Source: node-webpack
>Version: 4.43.0-6
>Severity: serious
>
>webpack depends on node-uglifyjs-webpack-plugin, which in turn has a
>serious bug report against it because it is abandoned upstream.
We should reduce severity of that
On 2021, ഫെബ്രുവരി 13 8:19:52 PM IST, Chris Hofstaedtler
wrote:
>Hi,
>
>* Debian Bug Tracking System [210213 14:48]:
>> #980580: ruby-ruby2ruby: FTBFS: ERROR: Test "ruby2.7" failed: RuntimeError:
>> unknown arg type nil
>
>have you noticed the autopkgtest failures on all archs?
Yes, it
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen
Packaging of https://rubygems.org/gems/gitlab-experiment
Dependency of gitlab 13.7
Package: ruby-graphlient
Version: 0.5.0-3
Severity: important
Currently tests are disabled because it fails on buildd but unable to
reproduce the failure locally. It'd be good to enable it once it
migrates to testing.
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen
Packaging of https://rubygems.org/gems/asciidoctor-kroki
Dependency of gitlab 13.7
On 2021, ഫെബ്രുവരി 4 12:10:44 AM IST, Eric Van Buggenhaut
wrote:
>Package: gitlab
>Version: 13.5.7-1~fto+1
>Severity: important
>
>Dear Maintainer,
>
>I have been unable to complete an install of gitlab:
>
># apt -t buster-backports install gitlab/buster-fasttrack
On Tue, 02 Feb 2021 14:26:24 +0530 Pirate Praveen
wrote:
> Reproduce the issue during upgrade on a clean machine. Installed
gitlab
> 13.5.7 then tried to upgrade to 13.6.5 and the error happened.
>
> If anyone would like to have a look I can share access to a test
> machine
On Mon, Feb 1, 2021 at 3:22 pm, Pirate Praveen
wrote:
A clean install went fine. So probably something bad on my local test
machine.
Reproduce the issue during upgrade on a clean machine. Installed gitlab
13.5.7 then tried to upgrade to 13.6.5 and the error happened.
If anyone would
A clean install went fine. So probably something bad on my local test
machine.
Package: gitlab
Severity: important
Control: tags -1 help
When trying to update gitlab to 13.6.5 from
https://people.debian.org/~praveen/fasttrack-staging/ installation
fails with this error.
https://wiki.debian.org/gitlab#Buster_Fast_Track_Staging has steps to
reproduce this.
==
Package: ftp.debian.org
X-DebBugs-CC: debian-r...@lists.debian.org
In debian ruby_parser was originally packaged under ruby-parser instead
of ruby-ruby-parser but we renamed ruby-parser to ruby-ruby-parser
making the old ruby-parser obsolete. All reverse dependencies are
updated already to
package: wnpp
severity: wishlist
Packaging of https://rubygems.org/gems/scientist
Indirect dependency of gitlab 13.7 (via gitlab-experiment)
On 2021, ജനുവരി 27 9:41:47 PM IST, Pirate Praveen
wrote:
>Crashes in both X11 and Wayland on gnome 3.
Just tested with Window Maker and this time it did not crash. But video was
just showing black screen.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
On 2021, ജനുവരി 27 7:35:24 PM IST, Boris Pek wrote:
>Hi,
>
>> Justification: voip is a new feature, there are still other
>> improvements worth an upgrade
>>
>> I got this crash using nheko built using an older gcc 10 *till we have
>> gcc 10.3 is in the archive)
>>
>> You can use
gstreamer1.0-vaapi should be in Depends
Package: nheko
Version: 0.8.0-1
Severity: important
Justification: voip is a new feature, there are still other
improvements worth an upgrade
I got this crash using nheko built using an older gcc 10 *till we have
gcc 10.3 is in the archive)
You can use
Control: tags -1 pending
Added these two to Depends,
+ , gstreamer1.0-nice
+ , gstreamer1.0-qt5
gstreamer1.0-qt5 includes qmlgl
Package: nheko
Version: 0.8.0-1
Severity: important
I built nheko using an older gcc-10 from snapshot.debian.org (let me
know if anyone want to try this, I can push it to a repo till gcc-10 is
fixed in the archive).
currently nheko is missing a dependency on gspreamer nice plugins
it is
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen
Packaging of https://rubygems.org/gems/gitlab-pg_query
Dependency of gitlab 13.6
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen
Packaging on https://rubygems.org/gems/graphlient
a dependency of gitlab 13.6
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen
Packaging on https://rubygems.org/gems/graphql-errors
Build dependency of graphlient (which is a dependency of gitlab 13.6)
On 2021, ജനുവരി 20 2:17:50 AM IST, Maximilian Stein wrote:
>
>> Someone else reported the artifacts issue was resolved in 13.5.6. See
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968626#40
>>
>Oh, sorry, i didn't mean artifact upload (bug 968626), but the Gitlab
>internal artifacts
On Mon, 11 Jan 2021 19:55:18 +0100 Lars Kruse
wrote:
> after upgrading from 13.4.7-2~fto10+1 to 13.5.6-1~fto10+1, every
issue
> view shows the following error message at the top:
>
> Failed to load sidebar lock status
Fixed in 13.5.7 in fasttrack-staging, will upload to fasttrack after
On Tue, Jan 19, 2021 at 7:52 pm, Maximilian Stein wrote:
Some good news finally.
After I switched to using only yarn for all modules (use unpatched
package.json) webpack is working fine. Now I will try to add back
the packaged modules one by one so we can know which module broke
it.
Control: reopen -1
Control: severity -1 important
Control: tags -1 help
On Tue, Jan 19, 2021 at 6:54 pm, Debian Bug Tracking System
wrote:
Your message dated Tue, 19 Jan 2021 18:50:13 +
with message-id
and subject line Bug#980406: fixed in node-xterm 3.8.1+~cs0.9.0-1
has caused the
Control: reassign -1 vmdb2
On Tue, Jan 19, 2021 at 6:08 pm, Julien Cristau
wrote:
On Sat, Dec 19, 2020 at 04:02:57PM +0530, Pirate Praveen wrote:
Package: vmdb2,xauth
Severity: wishlist
Control: block 913997 by -1
Hi,
Would you be open to change the yarn command if cmdtest renames
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen
Packaging on https://rubygems.org/gems/rack-test
Build dependency of graphlient (which is a dependency of gitlab 13.6)
On Tue, Jan 19, 2021 at 5:06 pm, Xavier wrote:
Le 19/01/2021 à 15:04, Pirate Praveen a écrit :
On Tue, Jan 19, 2021 at 2:24 pm, Pirate Praveen
wrote:
Control: severity -1 serious
I was able to use xterm 3.8.1 from nmpjs.com with gitlab without
any
issues. So this is a bug
On Tue, Jan 19, 2021 at 2:24 pm, Pirate Praveen
wrote:
Control: severity -1 serious
I was able to use xterm 3.8.1 from nmpjs.com with gitlab without any
issues. So this is a bug in node-xterm debian build.
Trying to switch to rollup instead of browserify-lite, but tsc itself
is failing
Control: severity -1 serious
I was able to use xterm 3.8.1 from nmpjs.com with gitlab without any
issues. So this is a bug in node-xterm debian build.
On 2021, ജനുവരി 19 2:46:30 AM IST, Xavier wrote:
>Le 18/01/2021 à 18:47, Pirate Praveen a écrit :
>Maintaining an unsupported version means taking the risk to be unable to
>backport a security fix during stable life and LTS (we already have many
>examples).
>_Before freeze_,
On Tue, 19 Jan 2021 00:29:18 +0100 Christian Kastner wrote:
> Hi all,
>
> On Sat, 19 Dec 2020 Pirate Praveen wrote:>> Renaming the binary is
> harder, because there are at least two
> >> packages that use yarn from cmdtest during the build: gitano and
> >>
Package: node-xterm
Version: 3.8.1-4
Severity: important
When using packaged version of node-xterm in gitlab, the browser error
console has these errors and it break web IDE of gitlab (the progress
circle keeps spinning).
Source map error: Error: JSON.parse: unexpected character at line 1
On Mon, Jan 18, 2021 at 2:28 pm, Antonio Terceiro
wrote:
But the fact is that all the other reverse dependencies that used any
plugin now need to be changed accordingly. Otherwise we can just wait
for their chart features to break in subtle ways in the face of users.
Not specific to this
Control: severity -1 important
On Mon, 11 Jan 2021 18:39:31 +0100 Xavier wrote:
> Hi all,
>
> Bullseye freeze is coming and we still have problems with
node-request
> removal. In particular, node-jsdom is not easy to patch. I tried a
patch
> (not approved by upstream) but it needs a lot of
Some good news finally.
After I switched to using only yarn for all modules (use unpatched
package.json) webpack is working fine. Now I will try to add back the
packaged modules one by one so we can know which module broke it.
I will upload 13.5.7 to fasttrack now.
clipanion needs @wessberg/rollup-plugin-ts as build dependency
Package: yarnpkg
Version: 1.22.10+~cs22.25.14-1
Severity: important
Control: block 956423 by -1
Yarn 1.x branch is not receiving any updates upstream. We somehow
managed to get it build with newer versions of build dependencies for
bullseye, but we are not able to remove dependency on request
Package: leaflet-markercluster
Version: 1.4.1~dfsg-9
Severity: important
As tracked in
https://wiki.debian.org/Javascript/Nodejs/Transitions/Rollup-plugin-json-legacy-rm
and notified in
https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2021-January/050132.html
It'd be good to
Package: leaflet
Version: 1.7.1~dfsg-2
Severity: important
As tracked in
https://wiki.debian.org/Javascript/Nodejs/Transitions/Rollup-plugin-json-legacy-rm
and notified in
https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2021-January/050132.html
It'd be good to drop the
Package: wnpp
severity: wishlist
Owner: Pirate Praveen
Packaging of https://rubygems.org/gems/graphql-client
Dependency of gitlab 13.6
Package: aspcud,aptitude
severity: important
When trying to build node-buble (and any other package that build
depends on node-acorn provided as a virtual package by
node-debbundle-acorn in buster-backports)
(I)Distcheck: Cudf Universe: 61258 packages
(I)Distcheck: --checkonly specified,
Package: node-yaml,pkg-js-tools
Severity: important
When building node-yaml with nocheck build profile, the build fails
dh binary
dh_update_autotools_config
dh_autoreconf
dh_auto_configure --buildsystem=nodejs
mkdir node_modules
internal/modules/cjs/loader.js:638
throw err;
^
On Wed, Jan 13, 2021 at 12:22 pm, Xavier wrote:
CC to pkg-javascript-devel for node-yarnpkg elements
We can try to update yarnpkg to version 2 by building corepack [1].
I need help with these packages,
New modules: clipanion terser-webpack-plugin ts-loader
@zkochan/cmd-shim
Update
On 2021, ജനുവരി 11 7:00:11 PM IST, Dragos Jarca
wrote:
>Package: gitlab
>Followup-For: Bug #979563
>
>Dear Maintainer,
>
>My instance work great after upgrade to 13.5.6.1!
>
>I can see the content of folder and files on UI.
>I can fetch, push, etc.
>I added versions off packages if I use,
On 2021, ജനുവരി 11 12:17:15 AM IST, Antoine Le Gonidec
wrote:
>I see a new update (13.5.6) is available through fasttrack-staging. Is it
>supposed to include a fix for the missing assets issue discussed here, or
>would it probably still trigger it?
It still has that bug, but includes some
On 2021, ജനുവരി 10 10:45:45 PM IST, Maximilian Stein wrote:
>Is there anything else that we could try to workaround the issues?
>
Try copying that directory from older versions ?
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Control: tags -1 help
Control: forwarded -1 https://gitlab.com/gitlab-org/gitaly/-/issues/2856
Control: retitle -1 rugged/libgit2 1.x breaks gitlab
On Fri, 08 Jan 2021 17:49:07 +0530 Pirate Praveen
wrote:
> Uploaded gitlab 13.5.6 to experimental for more testing, but some
core
> fe
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen
X-Debbugs-CC: debian-de...@lists.debian.org
* Package name : node-babel-plugin-lodash
Version : 3.3.4
Upstream Author : Graeme Yeates
(https://github.com/megawac)
* URL : https://github.com/lodash/babel-plugin-lodash#readme
* License
Package: gitlab
Version: 13.5.6-1
Severity: grave
Uploaded gitlab 13.5.6 to experimental for more testing, but some core
features are broken, likely due to new version of rugged/libgit2
already in debian which upstream does not support yet.
When visiting any project, for example,
On Fri, Jan 8, 2021 at 12:44 pm, Jonas Smedegaard
wrote:
I don't understand - how is node-babel7 affected by how yarnpkg
declares
(build-)dependencies against it?
node-babel7 will still be affected by the update-alternatives bug when
manpages missing.
What I suggest is to improve the
On Fri, Jan 8, 2021 at 12:06 pm, Jonas Smedegaard
wrote:
Quoting Pirate Praveen (2021-01-08 11:55:14)
On 2021, ജനുവരി 8 1:16:36 PM IST, Paolo Greppi
wrote:
>BTW, why is node-babel7 a run-time dependency of yarnpkg ?
>Should it not just be a build-dep ?
>
It needs @babe
On 2021, ജനുവരി 8 1:16:36 PM IST, Paolo Greppi wrote:
>BTW, why is node-babel7 a run-time dependency of yarnpkg ?
>Should it not just be a build-dep ?
>
It needs @babel/runtime which is currently part of node-babel7. I think yadd
already uploaded a version of node-babel7 with separate
Control: forwarded -1 https://github.com/lodash/lodash/issues/5051
Even upstream build is broken.
yarnpkg build:fp-modules is also generating only 104 files.
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 Thu, Jan 7, 2021 at 6:55 pm, Pirate Praveen
wrote:
I found another error while trying to update to gitlab 13.5 which I
think could be an issue here.
You can try to build from master-13.5 branch of gitlab. Or probably
try this patch in master branch or current version in unstable (or I
On Wed, Jan 6, 2021 at 4:04 pm, Maximilian Stein wrote:
So, I got the asset compilation running, but I had to workaround some
issues, including broken symlinks to js
libs:_
cd /usr/share/gitlab
# move locale.static elsewhere
mv
On Wed, Jan 6, 2021 at 10:24 am, Maximilian Stein wrote:
>Unfortunately updating css-loader and postcss did not fix this issue
:(
Can I somehow help to untangle this issue? Are there any workarounds
maybe?
One things I can think of is to get gitlab-rake gitlab:assets:compile
working
Package: golang-gopkg-libgit2-git2go.v31
Version: 31.4.3-2
Severity: important
It now provides versioned import path in upstream itself
https://salsa.debian.org/go-team/packages/golang-gopkg-libgit2-git2go/-/blob/3968f20c39f0902693aef2587600e79b9ed2fe48/go.mod
module
On Fri, 18 Dec 2020 23:17:16 +0100 Jonas Smedegaard wrote:
> Package: node-postcss
> Version: 7.0.34-1
> Severity: wishlist
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> I need these postcss-related modules not yet in Debian:
>
> postcss-css-variables
I just looked at this and it
On Fri, 18 Dec 2020 23:10:30 +0100 Jonas Smedegaard wrote:
> I need these postcss-related modules not yet in Debian:
>
> postcss-loader
Since it uses babel to build, I think it'd be better to package it
separately.
> postcss-preset-env
This is using rollup as a build system and has a
package: libjs-source-map
version: 0.7.0++dfsg2+really.0.6.1-4
severity: grave
Control: affects -1 ruby-terser
Upstream npmjs.com dist tarball has the following at the top of
dist/source-map.min.js
!function(e,n){"object"==typeof exports&&"object"==typeof
Package: node-rollup-plugin-json
Version: 4.1.0+repack+~4.0.0-2
Severity: important
Owner: Pirate Praveen
To reduce the maintenance burden, I plan to remove the legacy component
from this package similar to earlier transitions done for node-resolve,
babel, commonjs and alias plugins.
Control: tags -1 pending
I have fixed both issues (silent build failure and actual ftbfs due to
rollup plugins change) in master-6.0 branch as quilt push -a did not
succeed in master branch.
Package: rails
Version: 2:6.0.3.4+dfsg-2
Severity: serious
When I rebuilt all the packages during the rollup plugin transitions,
rails did not ftbfs, even though the rollup command actually failed.
cd activestorage; mkdir node_modules; \
ln -s rollup-plugin-commonjs node_modules; rollup -c;
Control: reassign -1 node-postcss-minify-font-values
On Sat, 02 Jan 2021 21:48:11 +0530 Pirate Praveen
wrote:
> Package: node-postcss-filter-plugins,node-postcss-minify-font-values
> Severity: serious
>
> Already filed request for removal. Filing rc bug in case the removal
> ta
Package: node-postcss-filter-plugins,node-postcss-minify-font-values
Severity: serious
Already filed request for removal. Filing rc bug in case the removal
takes longer than auto removal from testing for node-postcss 8 testing
migration.
Package: node-regexpp
Version: 3.1.0-4
Git repo of this package is empty. Please push the git repo to salsa.
Control: fixed -1 17.0.0+repack-1
On Sat, 02 Jan 2021 16:39:48 +0530 Pirate Praveen
wrote:
> I plan to remove the embedded copy of legacy plugin (similar to how
it
> was done for node-resolve and babel plugins) for bullseye. It is
mostly
> a one line patch and we have to maintain
Package: node-rollup-plugin-commonjs
Version: 15.1.0+~9.3.4-2
Severity: important
Owner: Pirate Praveen
I plan to remove the embedded copy of legacy plugin (similar to how it
was done for node-resolve and babel plugins) for bullseye. It is mostly
a one line patch and we have to maintain only
Package: node-rollup-plugin-babel
Version: 5.2.1+repack+~4.4.0-2
Severity: important
I think we should try to remove the embedded copy of legacy plugin to
reduce maintenance for bullseye (similar to how we did node-resolve
plugin).
lintian reports these errors, so it looks like a bug in
mk-origtargz/uscan
E: node-rollup-plugin-node-resolve source:
source-includes-file-in-files-excluded util/test.js
Package: devscripts
Version: 2.20.5
Example package to reproduce this issue: node-rollup-plugin-node-resolve
This package is a monoropo and included multiple node modules in a
single git repo, but we only want to include a single directory in the
orig.tar.
I added the following lines to
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
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 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]
Package: ftp.debian.org
Severity: normal
Incompatible with node-postcss 8.x and unmaintained upstream. No
reverse (build) dependencies.
Please remove this package from the archive to allow migration of
node-postcss 8 to testing.
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
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.
Package: ftp.debian.org
Severity: normal
Incompatible with node-postcss 8.x (rc bug #978123 and blocking
migration of node-postcss 8.x to testing) and unmaintained upstream. No
reverse (build) dependencies.
Please remove this package from the archive.
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
Control: forwarded -1
https://github.com/ai/autoprefixer-rails/issues/199
On Fri, 25 Dec 2020 14:51:34 +0530 Pirate Praveen
wrote:
> Even though the build now succeed, it is producing a broken output.
Size of autoprefixer.js dropped from 4.5 mb to 900 kb. It should bundle
post
Control: reopen -1
On Thu, 24 Dec 2020 20:44:50 +0530 Pirate Praveen
wrote:
> It is fixed by changing the order of plugins used in rollup.config.js,
> rollup-plugin-polyfills should come before commonjs and node-resolve
> plugins.
Even though the build now succeed, it is producing
Control: reassign -1 mocha
On Mon, 21 Dec 2020 01:40:48 +0100 Andreas Beckmann wrote:
> Package: mocha,node-postcss
Fixed in mocha.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
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 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:
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
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:
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
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.
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.
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
Package: devscripts
Version: 2.20.5
severity: important
For node-yarnpkg, package.json has
"normalize-url": "^2.0.0",
But without forcing version 2 like
https://registry.npmjs.org/normalize-url/-/normalize-url-(2[\d\.]+)@ARCHIVE_EXT@
checksum
it downloads the latest version 5.3.0 negating
Control: tags -1 pending
On Tue, Dec 22, 2020 at 1:20 pm, Akshay S Dinesh
wrote:
gbp:error: upstream/1.22.10+_cs18.39.16 is not a valid treeish
indeed your fork only has 33 tags, whereas js-team/node-yarnpkg has
37.
Please pull those tags and push them to your fork, then force
restart
Package: devscripts
Version: 2.20.5
Severity: wishlist
Currently ctype=nodejs read package.json to download matching versions
but it does not work for dependencies not present in package.json
(dependencies of other components we embed). Finding these versions
from yarn.lock or
On Mon, 21 Dec 2020 14:24:57 +0530 Pirate Praveen
wrote:
> >I think the real issue is that it does not pull not-yet-cached
modules.
>
> I think the failure is after it downloaded. I can see some files in
~/.cache/yarn created after it is cleaned after yarnpkg add. Could it
Package: gitlab
Version: 13.4.7-2
Severity: important
Control: block -1 by 977781
Control: forwarded -1 https://github.com/yarnpkg/berry/issues/2258
yarnpkg is currently broken in unstable. A work around is to update to
yarn 2, but its node-modules plugin refuse to work with node_modules as
a
On 2020, ഡിസംബർ 21 1:46:31 PM IST, Paolo Greppi wrote:
>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 agree, I wanted to see if it can be used to update to yarn 2 (so yarnpkg just
On Mon, 21 Dec 2020 13:15:46 +0530 Akshay S Dinesh wrote:
> > Since yarnpkg add command did not return an error, the autpkgtest was
> > succeeding even though it did not add any modules to node_modules
> > directory.
> >
>
>
> I did a bisect (sort of).
>
> Removing cache is not an issue
On Mon, Dec 21, 2020 at 1:46 am, Pirate Praveen
wrote:
We need to create ~/.yarnrc.yml to create node_modules directory.
$ cat ~/.yarnrc.yml
nodeLinker: "node-modules"
$ yarnpkg install
\➤ YN: ┌ Resolution step
➤ YN: └ Completed
➤ YN: ┌ Fetch step
➤ YN: └
401 - 500 of 3480 matches
Mail list logo
