Control: tags -1 patch
On Mon, 09 Aug 2021 01:35:43 +0530 Pirate Praveen
wrote:
> Adding,
> ruby/lib/google usr/lib/ruby/vendor_ruby
> to debian/ruby-google-protobuf.install makes require
'google/protobuf'
> to pass. This can be used as a workaround until we figure out w
On Mon, Aug 9, 2021 at 1:50 pm, Antonio Terceiro
wrote:
On Mon, Aug 09, 2021 at 01:35:43AM +0530, Pirate Praveen wrote:
On Mon, Aug 9, 2021 at 12:12 am, Pirate Praveen
wrote:
> [copying debian-ruby list]
>
> On Sun, 08 Aug 2021 22:08:39 +0530 Akshay S Dinesh
> wrote:
On Mon, Aug 9, 2021 at 12:12 am, Pirate Praveen
wrote:
[copying debian-ruby list]
On Sun, 08 Aug 2021 22:08:39 +0530 Akshay S Dinesh
wrote:
> Package: ruby-google-protobuf
> Version: 3.17.3-1
> Severity: grave
> Justification: renders package unusable
>
> Dear
[copying debian-ruby list]
On Sun, 08 Aug 2021 22:08:39 +0530 Akshay S Dinesh
wrote:
> Package: ruby-google-protobuf
> Version: 3.17.3-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> I was trying to install gitlab to reproduce #966653
>
> Installed
Control: clone -1 -2
Control: reassign -2 gitlab
On Sat, 10 Jul 2021 18:20:03 +0200 Jonas Smedegaard wrote:
> Package: gitlab-workhorse
> Version: 8.54.2+debian-1
> Severity: serious
> Justification: Policy 2.3
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> The SVG image
Control: retitle -1 FTBFS: Replace Autoprefixer browsers option to
Browserslist config
On Thu, 29 Jul 2021 17:19:34 +0200 Lucas Nussbaum
wrote:
> Source: twitter-bootstrap4
> Version: 4.5.2+dfsg1-6
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags:
Control: retitle -1 Unknown browser query `> 1%`. Maybe you are using
old Browserslist or made typo in query.
On Thu, 29 Jul 2021 17:14:42 +0200 Lucas Nussbaum
wrote:
> Source: node-superagent
> Version: 6.1.0-3
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
Package: diaspora
Version: 0.7.15.0-7
severity: grave
Processing triggers for diaspora (0.7.15.0-7~bpo11+1) ...
Updating bundler configuration for migration from diaspora-installer...
postinst called with unknown argument `triggered'
dpkg: error processing package diaspora (--configure):
Control: severity -1 important
On Mon, 12 Jul 2021 21:10:15 -0400 Ryan Kavanagh wrote:
> This bug seems to be, in part, due to a potentially (?) broken ruby
> upgrade behaviour. I've been running unstable on this laptop for ~6
> years, but still had
>
> ii ruby2.1 [ruby-interpreter] 2.1.5-4
>
Control: severity -1 important
Sat, 25 Jul 2020 00:29:54 +0530 Pirate Praveen
wrote:
> This package's autopkgtest and rebuilds failed with rails 6
currently in
> experimental. rails 6 will be uploaded to unstable in a weeks time,
so
> please make sure this package is ready fo
Control: severity -1 important
On Thu, 30 Jul 2020 19:18:09 +0530 Kartik Kulkarni
wrote:
> Hi,
>
> This package's autopkgtest and rebuilds failed with rails 6
currently in
> experimental. rails 6 will be uploaded to unstable in a weeks time,
so
> please make sure this package is ready for
On Wed, 27 Jan 2021 23:18:24 +0100 Andreas Beckmann
wrote:
> ruby-uglifier/experimental recently started to FTBFS, probably after
some
> build-dependency was updated:
I think switching to ruby-terser is a good idea (gitlab and diaspora
moved already). This should be a drop in replacement
On Sat, 03 Jul 2021 23:01:35 +0530 Pirate Praveen
wrote:
> I switched to rollup for generating umd and removed
add-module-exports
> plugin and it is working now. Possibly defining "autosize" global
with
> @babel/plugin-transform-modules-umd without add-module-exports
On Sat, 03 Jul 2021 18:11:20 +0530 Pirate Praveen
wrote:
> But this is babel 6 to babel 7 migration. The code transpiled by
babel
> 6 works fine, but moving to babel 7 broke it.
One possibility is that the add-module-exports plugin is not compatible
with babel 7's umd plugin (@babel/
On Sat, Jul 3, 2021 at 12:29 pm, Akshay S Dinesh
wrote:
https://stackoverflow.com/questions/33505992/babel-6-changes-how-it-exports-default
But most importantly
https://kentcdodds.com/blog/misunderstanding-es6-modules-upgrading-babel-tears-and-a-solution
But this is babel 6 to babel 7
Control: reopen -1
On Wed, 30 Jun 2021 22:40:13 +0530 Pirate Praveen
wrote:
> and this is working with diaspora. Thanks again for tracking down the
> issue.
Looks like I was wrong here and it is still failing with libjs-autosize
built with latest node-babel-plugin-add-module-exports.
On Wed, 30 Jun 2021 21:23:37 +0530 Pirate Praveen
wrote:
> $ reverse-depends -b node-babel-plugin-add-module-exports
> Reverse-Build-Depends
> * autosize.js
> * node-babel-plugin-lodash
> * node-colormin
> * node-css-loader
> * node-deep-for-each
> * node-es6-pro
On Wed, Jun 30, 2021 at 9:44 pm, Pirate Praveen
wrote:
On Wed, Jun 30, 2021 at 9:38 pm, Pirate Praveen
wrote:
Looks like we are already using the dist tarballs and does not
involve any build, we can just take the latest 1.0.4 from npmjs.com.
Scratch that, the new versions use babel
On Wed, Jun 30, 2021 at 9:38 pm, Pirate Praveen
wrote:
Looks like we are already using the dist tarballs and does not
involve any build, we can just take the latest 1.0.4 from npmjs.com.
Scratch that, the new versions use babel to build, so I think using
https://github.com/lijunle/babel
On Wed, Jun 30, 2021 at 9:30 pm, Pirate Praveen
wrote:
On Wed, Jun 30, 2021 at 8:27 pm, Akshay S Dinesh
wrote:
Either, update this plugin in Debian to the fork that's pushed only
to npm (or switch to
https://github.com/lijunle/babel-plugin-add-module-exports/ I guess)
I think we
On Wed, Jun 30, 2021 at 8:27 pm, Akshay S Dinesh
wrote:
This is most likely due to babel-plugin-add-module-exports being
broken.
See
https://github.com/59naga/babel-plugin-add-module-exports/issues/72
and
https://github.com/59naga/babel-plugin-add-module-exports/issues/80
and
Package: node-babel-plugin-add-module-exports
Version: 0.2.1-3
Severity: grave
Justification: creates broken build output
Control: forwarded -1
https://github.com/59naga/babel-plugin-add-module-exports/issues/73
Control: block 990458 by -1
Upstream has released a fix in major update. Since we
On Tue, 29 Jun 2021 23:54:30 +0530 Pirate Praveen
wrote:
> I can confirm libjs-autosize from buster works fine with diaspora.
So workaround is to install the buster version from snapshot.debian.org
http://snapshot.debian.org/archive/debian/20190209T090056Z/pool/main/a/autosize.js/li
On Tue, 29 Jun 2021 23:54:30 +0530 Pirate Praveen
wrote:
> I can confirm libjs-autosize from buster works fine with diaspora.
>
> Buster version has this,
>
> (function (global, factory) {
> if (typeof define === "function" && define.amd) {
>
Package: libjs-autosize
Severity: grave
Version: 4.0.2~dfsg1-5
Control: affects -1 ruby-rails-assets-autosize,diaspora
I think during transition to babel7 something broke.
This causes diaspora ui to break,
Uncaught ReferenceError: module is not defined
at
On Sat, 26 Jun 2021 07:51:18 +0200 Johannes Schauer Marin Rodrigues
wrote:
> Package: glances
> Version: 3.1.5-1
> Severity: serious
> Justification: Policy 2.2.1
>
> Hi,
>
> the source package contains:
>
> glances/outputs/static/public/glances.js
>
Control: forwarded -1
https://github.com/diaspora/diaspora_federation/pull/116
On Thu, 03 Dec 2020 23:25:20 +0530 Pirate Praveen
wrote:
> ruby-diaspora-federation ftbfs/fails autopkgtest with ruby-faraday
1.0
Reported upstream
https://github.com/diaspora/diaspora_federation/pull/116
Package: golang-uber-goleak
Version: 1.1.0-2
Severity: serious
This package ftbfs when built with gccgo-go (build log attached)
diff --git a/debian/control b/debian/control
index 90d37eb..9d17b02 100644
--- a/debian/control
+++ b/debian/control
@@ -6,7 +6,7 @@ Testsuite: autopkgtest-pkg-go
On Tue, 1 Jun 2021 16:41:51 +0200 Paolo Greppi
wrote:
> owner 986117 Paolo Greppi
> tag 986117 pending
Hi Paolo,
Can you upload it?
Thanks
Praveen
Package: ruby-spamcheck
Version: 0.1.0+git20210519.2084b44-2
Severity: grave
Control: block -1 by 966653
Since the only reverse dependency of ruby-spamcheck is gitlab and
gitlab does not work with debian's ruby-grpc package (see #966653),
dependency on ruby-grpc is removed. It will be added
Package: ruby-pg-query
Version: 2.0.3-1
Severity: grave
Control: affects -1 gitlab gitaly ruby-gitlab-labkit
gitlab-sidekiq service fails to start when ruby-google-protobuf package
is used, works with gem install -v 3.17.1 google-protobuf and removing
ruby-google-protobuf
Possibly the debian
Package: webpack
Version: 5.6.0+~cs6.4.0-1~exp2
Severity: serious
With webpack from experimental,
webpack --help
(node:251750) UnhandledPromiseRejectionWarning: Error: Cannot find
module 'array-back'
Require stack:
- /usr/share/nodejs/webpack/node_modules/command-line-usage/index.js
-
Control: tag -1 pending
Hello,
Bug #985336 in diaspora-installer reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
On Wed, 19 May 2021 22:12:59 +0200 Paul Gevers
wrote:
> Hi,
>
> On Sat, 15 May 2021 11:18:31 + Debian FTP Masters
> wrote:
> > rails (2:6.0.3.7+dfsg-1) unstable; urgency=high
> > .
> >* Upload to unstable directly.
> >* New upstream version 6.0.3.7+dfsg. (Closes: #988214)
> >
On Mon, 10 May 2021 09:53:05 +0200 Jan Wagner wrote:
> reopen 985336
> thx
>
> As 0.7.15.0+debian does not incorporate the changes done by
> 0.7.14.0+debian2+nmu1 and 0.7.14.0+debian2+nmu2 (where are the
> changelogs?) this bug is present in 0.7.15.0+debian again!
Since the changes for the
On Thu, 11 Feb 2021 18:40:58 +0100 Salvatore Bonaccorso
wrote:
> The following vulnerability was published for ruby-carrierwave.
>
> CVE-2021-21288[0]:
> | CarrierWave is an open-source RubyGem which provides a simple and
> | flexible way to upload files from Ruby applications. In CarrierWave
>
On Tue, 16 Mar 2021 13:24:10 +0100 Kristof Csillag
wrote:
> Package: gitaly
> Followup-For: Bug #983874
>
> I am seeing the same thing. This also makes gitlab unusable.
Keeping all moving parts working together in unstable is not possible
during freeze and transitions.
> Is there any update
://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986286
It is already fixed in unstable, but due to freeze, testing migration will take
20 days. Would it be possible to give an exception to upload the version from
unstable to buster-backports ?
Thanks
Praveen
--
Sent from my Android device with K-9 Mail. Please
On Sun, 2 May 2021 23:24:36 +0200 =?UTF-8?Q?Stefan_B=c3=bchler?=
wrote:
> Package: node-jade
> Version: 1.11.0+~cs4.1.0-1
> Severity: grave
>
> Hi,
>
> https://www.npmjs.com/package/jade says last release was 6 years ago
and
> it got replaced by pug.
>
> Also it doesn't work anymore in
On 2021, ഏപ്രിൽ 29 12:36:57 PM IST, Dragos Jarca
wrote:
>Package: gitlab
>Version: 13.10.4+ds1-1
>Severity: grave
>Justification: renders package unusable
>
>Dear Maintainer,
>
>When upgrading to gitlab 13.10.4 I have this error:
>
>gitlab_production database is not empty, skipping gitlab
On Sun, 18 Apr 2021 15:04:56 +0200 Salvatore Bonaccorso
wrote:
> Hi,
>
> On Sat, Apr 17, 2021 at 10:34:24PM +0530, Pirate Praveen wrote:
> >
> >
> > On Sat, Apr 17, 2021 at 10:16 pm, Utkarsh Gupta
wrote:
> > > Makes sense. Probably the time to RM ruby-re
On Sat, Apr 17, 2021 at 10:16 pm, Utkarsh Gupta
wrote:
Makes sense. Probably the time to RM ruby-rexml from the archive is
*now*?
Requested removal from archive in #987101
On Mon, 12 Apr 2021 12:05:29 +0200 Moritz Muehlenhoff
wrote:
>
https://www.ruby-lang.org/en/news/2021/04/05/xml-round-trip-vulnerability-in-rexml-cve-2021-28965/
>
> Why is there a separate package duplicating rexml from src:ruby2.7
in bullseye?
I think the separate package was introduced
Control: forwarded -1 https://github.com/diaspora/diaspora/issues/8229
On Fri, 02 Apr 2021 14:21:14 +0200 Andreas Beckmann
> Fetching gem metadata from https://gems.diasporafoundation.org/..
> Fetching gem metadata from https://rubygems.org/..
> [ESC][31mYour bundle is locked to
On Wed, 24 Mar 2021 12:44:28 +0530 Pirate Praveen
wrote:
> On Tue, 23 Mar 2021 21:31:28 + Mike Gabriel
wrote:
> > Package: ruby-licensee
> > Version: 9.14.1-1
> > Severity: grave
> > X-Debbugs-Cc: prav...@debian.org
> >
> > The ruby-licens
On Tue, 23 Mar 2021 21:31:28 + Mike Gabriel
wrote:
> Package: ruby-licensee
> Version: 9.14.1-1
> Severity: grave
> X-Debbugs-Cc: prav...@debian.org
>
> The ruby-licensee package as currently found in Debian experimental
> lacks the entire library folder of the licensee Gem. These files,
[Ccing debian-release]
On Wed, 17 Feb 2021 14:01:40 + Julian Gilbey wrote:
> On Sun, Feb 14, 2021 at 02:26:30PM +0100, Jonas Smedegaard wrote:
> > I still recommend to request release team to ignore for this release
> > instead of lowering sverity, but don't care anough about this
t@omv:~# apt-show-versions -a ruby-pg-query
>ruby-pg-query not installed (not available)
ruby-pg-query is available people.debian. org/~praveen/staging. This was
mentioned in wiki for gitlab 13.8.
>On 11.03.2021 18:23, Pirate Praveen wrote:
>> On Mon, 11 Jan 2021 18:10:34 +020
On Mon, 11 Jan 2021 18:10:34 +0200 Dragos Jarca
wrote:
> Just to know, in previous version I have some trouble with licensee,
and
> I do the following to solve the problem:
>
> gitaly(13.4.6+dfsg1-2) and gitlab(13.4.7-2) have in Gemfile:
>
> gem 'rugged', '~> 0.28'
> ...
> gem 'licensee', '~>
On 2021, മാർച്ച് 9 12:56:44 AM IST, Mike Gabriel
wrote:
>Package: gitlab
>Version: 13.7.8+ds1-1~fto10+1
>Severity: serious
>
>Hi Praveen,
>
>here comes the other issue I am facing. Occurred with 13.7.7 and also
>occurs with 13.7.8:
>
>When I open a Git repos
On 2021, മാർച്ച് 8 1:24:48 AM IST, Antonio Terceiro wrote:
>On Sun, Mar 07, 2021 at 11:01:16PM +0530, Pirate Praveen wrote:
>> [adding release team]
>>
>> On Sun, Mar 7, 2021 at 10:49 pm, Utkarsh Gupta wrote:
>> > Hi Praveen,
>> >
>> >
[adding release team]
On Sun, Mar 7, 2021 at 10:49 pm, Utkarsh Gupta
wrote:
Hi Praveen,
On Sun, Mar 7, 2021 at 10:15 PM Pirate Praveen
wrote:
It looks like we will have to remove ruby-vcr and we will have to
disable tests for the following packages. I don't think there is
another way
It looks like we will have to remove ruby-vcr and we will have to
disable tests for the following packages. I don't think there is
another way, thoughts?
No reverse dependencies.
reverse-depends -b ruby-vcr
Reverse-Build-Depends
* nanoc
* ruby-coveralls
* ruby-graphlient
* ruby-mixlib-install
On Thu, 04 Feb 2021 20:49:39 +0200 Adrian Bunk wrote:
> /usr/lib/ruby/2.7.0/net/http.rb:960:in `initialize': Failed to open
TCP connection to codeload.github.com:443 (Network is unreachable -
connect(2) for "codeload.github.com" port 443) (Errno::ENETUNREACH)
>from
On 2021, മാർച്ച് 4 9:31:42 PM IST, Mike Gabriel
wrote:
>Control: tags -1 patch
>
>Hi Praveen,
>
>On Mi 03 Mär 2021 16:12:47 CET, Pirate Praveen wrote:
>
>> On 2021, മാർച്ച് 3 8:17:44 PM IST, Mike Gabriel
>> wrote:
>>> Hi Praveen,
>>>
>
On 2021, മാർച്ച് 3 8:17:44 PM IST, Mike Gabriel
wrote:
>Hi Praveen,
>
>On Mi 03 Mär 2021 15:38:46 CET, Pirate Praveen wrote:
>
>> On 2021, മാർച്ച് 3 7:54:13 PM IST, Mike Gabriel
>> wrote:
>>> Package: gitlab
>>> Version: 13.7.7-2~fto10+1
>>&
On 2021, മാർച്ച് 3 7:54:13 PM IST, Mike Gabriel
wrote:
>Package: gitlab
>Version: 13.7.7-2~fto10+1
>Severity: serious
>
>Hi Praveen,
>
>I can't upgrade gitlab from 13.4.7-2~fto10+1, I get the below error
>messages (webpack and ttf fonts). Don't wonder about the /srv
On 2021, മാർച്ച് 3 4:20:32 PM IST, Andreas Beckmann wrote:
>Package: gitlab
>Version: 13.4.7-2
>Severity: serious
>User: debian...@lists.debian.org
>Usertags: piuparts
>
>Hi,
>
>during a test with piuparts I noticed your package failed to install. As
>per definition of the release team this
Package: gitlab
Severity: grave
Control: forwarded -1 https://github.com/yarnpkg/berry/issues/2384
This seems to be fixed in master but there is no release yet.
On Sun, 13 Dec 2020 21:30:41 +0100 Jonas Smedegaard wrote:
> Package: node-uglifyjs-webpack-plugin
> Version: 1.3.0-9
> Severity: serious
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> node-uglifyjs-webpack-plugin is dead since 1.5 years, already carries a
> patch to not actually use
On 2021, ഫെബ്രുവരി 14 2:55:33 PM IST, Jonas Smedegaard wrote:
>Quoting Pirate Praveen (2021-02-14 08:32:08)
>>
>>
>> On 2021, ഫെബ്രുവരി 14 12:44:09 PM IST, Julian Gilbey wrote:
>> >webpack depends on node-uglifyjs-webpack-plugin, which in turn has a
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
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
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
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 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
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,
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
://gitlab.lxc/praveen/test
The UI has this error message,
An error occurred while fetching folder content.
The browser error console has this,
Failed to load resource: the server responded with a status of 500
(Internal Server Error)
commons-pages.projects.show-pages.projects.tree.show.1cb74241
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
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.
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: 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.
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: 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
/GroupSourcesTutorial
I think Praveen locked the dependency on tar-fs to version 1.x in
https://salsa.debian.org/js-team/node-yarnpkg/-/commit/8f44f7d238f4330b89d3b62c2cc369bb909459a6
I'm unsure if that's because upstream yarn mentions 1.x tar-fs as
dependency or because there are other dependencies to 1.x tar
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
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: └
On Mon, Dec 21, 2020 at 1:37 am, Pirate Praveen
wrote:
On Mon, 21 Dec 2020 00:39:35 +0530 Pirate Praveen
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
On Mon, 21 Dec 2020 00:39:35 +0530 Pirate Praveen
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.
Though this is sufficient to install yarn 2 (berry).
$ yarnpkg set vers
Package: yarnpkg
Version: 1.22.10+~cs18.39.16-1
Severity: serious
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 have fixed the faulty autopkgtest which now exposes the failure.
Control: forwarded -1 https://gitlab.com/gitlab-org/gitaly/-/issues/2856
On Tue, 8 Dec 2020 10:55:52 +0100 Sebastian Ramacher
wrote:
> golang-gopkg-libgit2-git2go.v28 will be removed as part of the
libgit2
> transition. So please switch to golang-gopkg-libgit2-git2go.v30-dev.
This updated
On Sun, 28 Jul 2019 19:26:12 +0530 Pirate Praveen
wrote:
> It stalled for a long time and we restarted work on it recently. We
are in the process of getting server space to setup dak.
Just adding this information here,
Debian FastTrack is live for some time and instructions to inst
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,
>
Control: tags -1 pending
On Wed, 2 Dec 2020 22:11:27 +0100 Paul Gevers wrote:
> I love tests. As one of the maintainers of the ci.debian.net
> infrastructure, I really do. However, with my Release Team member hat
> on, I'm asking you to stop Build-Depending on qunit-selenium which
you
> need
Package: pristine-tar,git-buildpackage,devscripts
Control: found -1 pristine-tar/1.49
Control: found -1 devscripts/2.20.5
Control: found -1 git-buildpackage/0.9.20
severity: serious
I'm filing against all 3 possible packages which might have a bug here.
Example package node-mermaid. It fails on
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 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
Control: reopen -1
On Fri, Dec 4, 2020 at 19:52, Xavier Guimard
wrote:
Control: tag -1 pending
Hello,
Bug #976310 in node-css-loader reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
101 - 200 of 933 matches
Mail list logo
