Control: clone -1 -2
Control: reassign -2 node-css-loader
Control: retitle -2 many dependencies in the archive differ by major
versions
On Fri, Dec 4, 2020 at 02:35, Pirate Praveen
wrote:
I will try to get css-loader from debian working with gitlab as a
proper fix.
With css-loader 3
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
Package: ruby-diaspora-federation
Severity: serious
Version: 0.2.6-2
ruby-diaspora-federation ftbfs/fails autopkgtest with ruby-faraday 1.0
/usr/lib/ruby/2.7.0/rubygems/dependency.rb:313:in `to_specs': Could not
find 'faraday' (< 0.18.0, >= 0.9.0) - did find: [faraday-1.1.0]
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, 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
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 Wed, 02 Dec 2020 21:59:22 +0530 Pirate Praveen
wrote:
> On 2020, ഡിസംബർ 2 9:33:04 PM IST, Utkarsh Gupta
wrote:
> >for faraday v1.x. I'll raise the issue upstream but you probably
need
> >to consider adding Breaks.
Once you raise an issue, please add forwarded. Though I do
Package: ruby-azure-storage
Version: 0.15.0~preview-2
Severity: serious
Autopkgtest fails with error (rebuild should see the same failure)
/usr/lib/ruby/2.7.0/rubygems/dependency.rb:313:in `to_specs': Could not
find 'faraday' (~> 0.9) - did find: [faraday-1.1.0]
(Gem::MissingSpecVersionError)
Package: ruby-azure-core
Version: 0.1.15-1
Severity: serious
Autopkgtest failed with this error (rebuild should see the same error)
/usr/lib/ruby/2.7.0/rubygems/dependency.rb:313:in `to_specs': Could not
find 'faraday' (~> 0.9) - did find: [faraday-1.1.0]
(Gem::MissingSpecVersionError)
Full
On 2020, ഡിസംബർ 2 9:33:04 PM IST, Utkarsh Gupta wrote:
>Hi Praveen,
>
>On Wed, Dec 2, 2020 at 8:06 PM Pirate Praveen wrote:
>> I can see there is already a patch for relaxing faraday.
>> https://salsa.debian.org/puppet-team/ruby-puppet-forge/-/blob/master/debian/patches/
Package: ruby-puppet-forge
Version: 2.3.2-1
Severity: serious
autopkgtest is failing with ruby-faraday-middleware 1.0.
/usr/lib/ruby/2.7.0/rubygems/dependency.rb:313:in `to_specs': Could not
find 'faraday_middleware' (< 0.14.0, >= 0.9.0) - did find:
[faraday_middleware-1.0.0]
Control: reassign -1 ruby-bundler
Control: done -1
Control: fixed -1 3.2.0~rc.2-4
On Sun, 08 Nov 2020 18:55:21 +0200 Adrian Bunk wrote:
> Source: gitaly
> Version: 13.3.9+dfsg-1
> Severity: serious
> Tags: ftbfs
>
> https://buildd.debian.org/status/package.php?p=gitaly=sid
>
This is caused 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
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).
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
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
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
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
Package: ruby-kubelcient
Version: 4.6.0-1
Severity: serious
Control: forwarded -1 https://github.com/abonas/kubeclient/issues/483
ruby-kubeclient started failing debci and ftbfs recently.
TestResourceQuota#test_get_from_json_v1 = 0.01 s = .
KubeclientConfigTest#test_user_token =
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 want to see yarn in debian bullseye will have to
fix it.
On 2020, നവംബർ 19 11:01:11 PM IST, Michael Prokop wrote:
>Hi,
>
>* Pirate Praveen [Thu Nov 19, 2020 at 03:05:13PM +0530]:
>
>> As you already found out, the problem is in node-yarnpkg. The fix is
>> a bit hard though as node-yarnpkg currently ftbfs due to babel 7
&g
Control: reassign -1 node-yarnpkg
Control: affects -1 gitlab
On Wed, 4 Nov 2020 12:22:30 +0200 Dragos Jarca
wrote:
> Dear Maintainer,
>
> Upgrade to 13.3.8.1 failed:
>
> Installing node modules...
> + runuser -u gitlab -- sh -c install -d /var/lib/gitlab/.node_modules
> + runuser -u gitlab --
On 2020, നവംബർ 9 8:28:17 AM IST, Daniel Leidert wrote:
>Package: diaspora
>Version: 0.7.9.0+dfsg-4
>Severity: grave
>
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA512
>
>While investigating the other RC issue I discovered that diaspora is
>uninstallable in Sid:
>
>The following packages have
Control: reassign -1 node-bootstrap-switch
Control: affects -1 ruby-bootstrap-switch-rails
On Wed, 23 Sep 2020 15:48:00 +0530 Pirate Praveen
wrote:
> Package: ruby-bootstrap-switch-rails
Reassigning to node-bootstrap-switch, we need to upload 3.3.4+really3.3.3 as
this bug is not fi
Package: diaspora
Version: 0.7.14.0-7
Severity: grave
Control: forwarded -1 https://github.com/diaspora/diaspora/issues/8158
Attaching screenshot of broken aspect selection list. This is possibly
caused by newer version of jquery in debian (upstream is still using
jquery 3.4.1 and we are
, there is no error shown
in browser console this time.
Fixing this issue will help us include diaspora in FreedomBox too.
Thanks
Praveen
Package: diaspora
Version: 0.7.14.0-6
Severity: grave
Control: tags -1 help
Using instructions from
https://wiki.debian.org/Diaspora/#Buster_Fasttrack.2Fpersonal_repo I
have setup the diaspora pod, but comment box is broken, the html code
for submit button is shown as content inside the text
On Thu, Oct 1, 2020 at 09:44, Xavier wrote:
Upstream source are really missing, only repacked files are available.
Relevant bug: https://github.com/Rich-Harris/locate-character/issues/6
Attaching the diff between the two dist tarballs. Only addition seems
to be that of typings and
On 2020, ഒക്ടോബർ 1 12:23:20 PM IST, Xavier Guimard wrote:
>Package: node-locate-character
>Version: 2.0.5-1
>Severity: serious
>Justification: source-is-missing
>
>2.0.5 is packaged from npm registry temporarily to be able to build
>rollup 2. Upstream didn't push 2.0.5 source in git repo
Control: tag -1 pending
On 2020, സെപ്റ്റംബർ 24 5:13:53 PM IST, Pirate Praveen
wrote:
>After trying different options of both webpack and rollup, finally
>found this
>https://github.com/ai/autoprefixer-rails/blob/master/build/rollup.config.js
>
>I will try using this now.
Jishn
On Sun, Sep 20, 2020 at 16:10, Pirate Praveen
wrote:
On Sun, Sep 20, 2020 at 15:51, Nilesh Patra
wrote:
I've seen these almost same buffer based errors before - with
webpack specifically - and manually creating a symlink helped. I
did the same in this case and the build passes
Package: ruby-bootstrap-switch-rails
Version: 3.3.4-1
Severity: grave
Control: forwarded -1
https://github.com/Bttstrp/bootstrap-switch/issues/691
It does not seem to be fixed in 3.3.5 as well
(https://github.com/diaspora/diaspora/pull/8149)
So we need to downgrade it to 3.3.3 which works.
On Tue, Sep 22, 2020 at 13:21, Xavier wrote:
Looks good to me too. We could perhaps list the "bigger transitions"
(nodejs, babel, bubble, rollup)
Included a link to that page already :)
On Mon, Sep 21, 2020 at 11:53, Jonas Smedegaard wrote:
Quoting Pirate Praveen (2020-09-21 09:15:46)
If you simply mean a loose "don't break reverse dependencies!" and
write
some suggestions down on a wiki page, then I fully agree: That is
common
for Debian in general.
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,
On 2020, സെപ്റ്റംബർ 21 12:38:37 AM IST, Xavier Guimard wrote:
>Package: rollup
>Version: 1.12.0-2
>Severity: serious
>Tags: ftbfs
>Justification: Policy 7.7.7
>
>node-rollup 1.12.0 can't be build with current typescript (4.0.2). It
>requires tsc 3.4.5 (tested with success). Output:
I think
On Sun, Sep 20, 2020 at 15:51, Nilesh Patra wrote:
I've seen these almost same buffer based errors before - with webpack
specifically - and manually creating a symlink helped. I did the same
in this case and the build passes with "Buffer: true"
I've pushed the commit to the same webpack
Control: tags -1 help
On Sun, Sep 20, 2020 at 14:44, Pirate Praveen
wrote:
The warning now changes to,
(!) Missing shims for Node.js built-ins
Creating a browser bundle that depends on 'path', 'url' and 'os'. You
might need to include
https://www.npmjs.com/package/rollup-plugin-node
Control: reassign -1 libjs-autoprefixer
Control: found -1 8.6.5-2
On Sun, Sep 20, 2020 at 14:28, Pirate Praveen
wrote:
ruby-autoprefixer-rails links to autoprefixer.js provided by
libjs-autoprefixer.
ls -l
/usr/share/rubygems-integration/all/gems/autoprefixer-rails-8.6.5/vendor
reassign -1 libjs-autoprefixer
found -1 8.6.5-2
On Fri, Sep 18, 2020 at 19:57, Pirate Praveen
wrote:
Control: reassign -1 ruby-autoprefixer-rails
Control: found -1 8.6.5+dfsg-3
After replacing sass-rails, execjs and autoprefixer-rails (taking
clues from the error log) with versions from
Control: reassign -1 ruby-autoprefixer-rails
Control: found -1 8.6.5+dfsg-3
After replacing sass-rails, execjs and autoprefixer-rails (taking clues
from the error log) with versions from rubygems.org, I found
autoprefixer-rails version installed from rubygems.org fixes this
issue, so the bug
Package: diaspora
Version: 0.7.14.0-2
Severity: grave
Using packages from
https://wiki.debian.org/Diaspora#Buster_Fasttrack.2Fpersonal_repo
(as rails 5 in not available in unstable/experimental) installation
fails with
Bundle complete! 101 Gemfile dependencies, 223 gems now installed.
Use
Control: reassign -1 node-handlebars
Control: affects -1 ruby-handlebars-assets
Control: found -1 3:4.7.6-2
> I debugged this case and looked into the FTBFS of
ruby-handlebas-assets. I
> checked out the upstream git repository and it tests just fine even
when I
> raise the haml and rake gem
Control: severity -1 wishlist
On Sun, Sep 6, 2020 at 13:59, Jonas Smedegaard wrote:
Package: node-entities
Version: 2.0.2-2
Severity: serious
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
node-* packages must depend on nodejs -
libjs-* need not (when _only_ targeting browser use).
*
Package: ruby-oj
Version: 3.10.13-1
Severity: serious
Control: forwarded -1 https://github.com/ohler55/oj/issues/610
Failed to build on official buildd with error
1) Failure:
CustomJuice#test_float_parse_fast
[/<>/test/test_custom.rb:129]:
Expected: "12.12345678901235"
Actual:
control: severity -1 normal
control: tags -1 unreproducible
downgrade severity as it built in debian buildd and not reproducible in
sbuild
Package: redmine
Version: 4.0.7-1
Severity: serious
User: pkg-ruby-extras-maintain...@lists.alioth.debian.org
Usertags: rails6-transition
redmine autopkgtest fails with rails 6. Full log
https://ci.debian.net/data/autopkgtest/testing/amd64/r/redmine/6840219/log.gz
package: debmake
version: 4.3.2-1
severity: grave
Using pretty-ms node module as example. debmake 4.3.2-1 worked.
(debian-sid)pravi@ilvala2:~/packaging/node-pretty-ms-7.0.0$ debmake
I: set parameters
I: sanity check of parameters
I: pkg="node-pretty-ms", ver="7.0.0", rev="1"
I: *** start
b/ruby/vendor_ruby/minitest.rb:164:in `__run'
/usr/lib/ruby/vendor_ruby/minitest.rb:141:in `run'
/usr/lib/ruby/vendor_ruby/minitest.rb:68:in `block in autorun'
32 runs, 3 assertions, 0 failures, 30 errors, 0 skips
Full log
https://people.debian.org/~praveen/rails6-meta-build/buildlogs/ruby-has-scope.log
m'
from -e:1:in `'
Full log is
https://people.debian.org/~praveen/rails6-meta-build/buildlogs/ruby-diaspora-federation-rails.log
Control: reassign -1 libsass
Control: affects -1 gitlab
Seems like a regression in libsass.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
dpkg-buildpackage
-
Command: dpkg-buildpackage -us -uc -rfakeroot
dpkg-buildpackage: info: source package ruby-net-dns
dpkg-buildpackage: info: source version 0.9.1-2
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Pirate Praveen
nd: dpkg-buildpackage -us -uc -rfakeroot
dpkg-buildpackage: info: source package ruby-net-dns
dpkg-buildpackage: info: source version 0.9.1-2
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Pirate Praveen
dpkg-source --before-build .
dpkg-buildpack
> With this build:
> https://salsa.debian.org/js-team/node-yarnpkg/-/jobs/915568#L2420
> I get a different error while building:
> [17:58:12] Starting 'build'...
> 2420[17:58:13] Error: [BABEL]
/builds/js-team/node-yarnpkg/debian/output/node-yarnpkg-1.22.4/src/api.js:
Cannot find module
>
Control: tag -1 pending
Hello,
Bug #965218 in ruby-sentry-raven 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:
Package: ruby-kramdown-parser-gfm
Version: 1.1.0-1~exp1
Severity: serious
Control: affects -1 ruby-cucumber-core
On a clean sid chroot with ruby-karmdown 2.3.0-3 added, it fails with
this error message. So reuploading this package to unstable is blocked
and it results in ruby-cucumber-core
Control: reassign -1 ruby-grpc
Control: found -1 1.30.2-2
If I replace ruby-grpc package with grpc gem from rubygems.org,
gitlab/gitaly crash is fixed.
On Wed, Aug 12, 2020 at 11:53, dragos.ja...@dynamicpuzzle.ro wrote:
Hi
I installed packages, but have another err:
Installing node modules...
yarn install v1.22.4
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
error An unexpected error occurred:
On Wed, Aug 12, 2020 at 08:38, dragos.ja...@dynamicpuzzle.ro wrote:
Hi
Access violation persists.
Tried to downgrade grpc, but have dependency problems.
Use http://snapshot.debian.org/package/protobuf/3.11.4-5/ and
http://snapshot.debian.org/package/grpc/1.26.0-3/
You need
Control: clone -1 -2
Control: retitle -2 "ruby-sidekiq 6 makes gitlab uninstallable"
Control: reassign -2 gitlab
On Tue, Aug 11, 2020 at 16:08, Pirate Praveen
wrote:
On Tue, Aug 11, 2020 at 13:35, dragos.ja...@dynamicpuzzle.ro wrote:
dpkg -i ruby-sidekiq_5.2.7+dfsg-1_all.deb dpk
On Tue, Aug 11, 2020 at 13:35, dragos.ja...@dynamicpuzzle.ro wrote:
dpkg -i ruby-sidekiq_5.2.7+dfsg-1_all.deb dpkg: warning: downgrading
ruby-sidekiq from 6.0.4+dfsg-2 to 5.2.7+dfsg-1 (Reading database ...
411139 files and directories currently installed.) Preparing to
unpack
On Tue, Aug 11, 2020 at 13:11, dragos.ja...@dynamicpuzzle.ro wrote:
Hi Praveen
I installed 13.2.3,but have problems on configure with sidekiq*
versions:
Bundler could not find compatible versions for gem "sidekiq": In
Gemfile: sidekiq gitlab-sidekiq-fetcher was resolved to 0.
On Sun, Aug 9, 2020 at 23:54, Pirate Praveen
wrote:
From the previous comment on this bug, it appears to be caused by
ruby-google-protobuf and ruby-grpc.
Can you try the new gitlab version I just uploaded?
I can also reproduce the crash now. Try with older protobuf/grpc
From the previous comment on this bug, it appears to be caused by
ruby-google-protobuf and ruby-grpc.
Can you try the new gitlab version I just uploaded?
Since there are many templates here, I have started
https://git.fosscommunity.in/debian-ruby/TaskTracker/-/issues/168 to
track status of each template.
Control: tag -1 pending
Hello,
Bug #966938 in ruby-devise 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:
7
-I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib
/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec
--pattern ./spec/\*\*/\*_spec.rb --format documentation failed
Full log
https://people.debian.org/~p
On Tue, Aug 4, 2020 at 00:25, Pirate Praveen
wrote:
This was fixed in ruby-webpacker 4.2.2-3. Now the autopkgtest is
passing.
It took almost a whole day to troubleshoot and fix this.
with ruby-webpacker 4.2.2-3 and ruby-webdrivers 4.4.1-1 in NEW, passed
as local debs,
Run options
Control: tags -1 pending
On Mon, Aug 3, 2020 at 23:31, Pirate Praveen
wrote:
After skipping check for nodejs and yarn version checks in
ruby-webpacker, I get this error. This looks like a bug in
ruby-webpacker, it may be missing the required files in the binary
package.
This was fixed
On Mon, Aug 3, 2020 at 21:43, Pirate Praveen
wrote:
This seems strange as rails metapackage has a dependency on webpack,
and yarnpkg which should pull nodejs.
After skipping check for nodejs and yarn version checks in
ruby-webpacker, I get this error. This looks like a bug in
ruby
On Mon, Aug 3, 2020 at 20:12, Pirate Praveen
wrote:
Once ruby-webpacker and ruby-webdrivers clears NEW creating new rails
app will work.
Now some tests for the newly created app fails. I think running rails
webpacker:install will fix it.
+ rails webpacker:install
Warning: Running `gem
Once ruby-webpacker and ruby-webdrivers clears NEW creating new rails
app will work.
Now some tests for the newly created app fails. I think running rails
webpacker:install will fix it.
+ rake test
/usr/lib/ruby/vendor_ruby/capybara/selector/filter_set.rb:115: warning:
Using the last
Could not find gem 'webpacker (~> 4.0)' in any of the gem sources
listed in your
Gemfile.
debian/patches/0001-Be-careful-with-that-bundler.patch
We can reproduce this by just running
rails new foo
$ rails new foo
create
create README.md
create Rakefile
create .ruby-version
create config.ru
create .gitignore
create Gemfile
run git init from "."
Initialized empty Git repository in /tmp/foo/.git/
Package: rails
Version: 6.0.3.2+dfsg-4
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/arm64/r/ruby-rails-assets-autosize/6520761/log.gz
(same error in rails as well other autopkgtest failures)
run bundle install --local
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
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 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 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.
On 2020, ജൂലൈ 21 9:45:50 AM IST, peter green wrote:
>>
>> Last blockers for removal:
>>
>> 1. node-yarnpkg - #960120 - should be patched/fixed for 1.x or switch
>> to 'berry'/2.x (supports babel 7) in time for bullseye
>> 2. libjs-webrtc-adapte - #959798 - browserify-lite can be replaced by
Control: tags -1 help
On Sun, 23 Feb 2020 08:45:32 +0100 Lucas Nussbaum
wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):
> > LoadError:
> > cannot load such file -- rspec/rails
This looks like a failure started with
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, 23 Feb 2020 08:43:58 +0100 Lucas Nussbaum
wrote:
> Source: ruby-browser
> Version: 2.5.3-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: buster sid
> Usertags: ftbfs-20200222 ftbfs-buster
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
>
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, ജൂലൈ 1 1:57:21 AM IST, Niko Tyni wrote:
>Source: gitaly
>Version: 1.78.0+dfsg-2
>Severity: serious
>Tags: ftbfs
>
>This package fails to build on current sid.
The version in experimental works, but it is blocked by rails 6 transition.
Around first week of August, we plan to upload
Package: ubuntu-dev-tools
Version: 0.176
Severity: grave
Justification: ships a broken command
reverse-depends command queries qa.ubuntuwire.org which is down. This
is a very useful command and we should get the service up again or
possibly run on debian infra if it is down permanently.
On Sun, Jun 14, 2020 at 7:31 am, Mike Hommey wrote:
On Thu, Jun 11, 2020 at 03:22:40PM +0530, Pirate Praveen wrote:
On Thu, 25 Jul 2019 12:10:45 +0200 Johannes Rohr
wrote:
> It would be great to have firefox (or the next firefox-esr) in
> buster-backports, as it has importa
On Thu, 25 Jul 2019 12:10:45 +0200 Johannes Rohr wrote:
> It would be great to have firefox (or the next firefox-esr) in
> buster-backports, as it has important new functionality relevant for
> privacy and data protection, such as the multi account containers
> function. However, this bug
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).
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 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
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
fixed 9.7.6-1
thanks
On Sun, May 3, 2020 at 2:57 pm, Lucas Nussbaum wrote:
During a rebuild of all packages in sid, your package failed to build
on amd64.
Fixed in 9.7.6-1
Control: tags -1 pending
On Sun, May 3, 2020 at 2:57 pm, Lucas Nussbaum wrote:
During a rebuild of all packages in sid, your package failed to build
on amd64.
Fix for building with node-gulp-babel 8.0 is ready in git and will be
uploaded soon.
On Fri, May 1, 2020 at 12:06 am, Pirate Praveen
wrote:
at least
packages/babel-plugin-transform-runtime/scripts/build-dist.js should
be run during build to fix this.
I think it is safer to run make build.
I got make build to run without babel-standalone target, it still did
201 - 300 of 933 matches
Mail list logo
