Bug#972702: ruby-bundler: dependency resolution fails for compiled gems

2020-10-29 Thread Antonio Terceiro
On Thu, Oct 29, 2020 at 01:21:03PM +0100, David Rodríguez wrote: > El 29/10/20 a las 13:14, Antonio Terceiro escribió: > > > On Thu, Oct 29, 2020 at 11:17:59AM +0100, David Rodríguez wrote: > > > Hi! > > > > > > Just to clarify why I prefer the second solution, I think what debian > > > does is

Bug#972702: ruby-bundler: dependency resolution fails for compiled gems

2020-10-29 Thread Antonio Terceiro
On Thu, Oct 29, 2020 at 11:17:59AM +0100, David Rodríguez wrote: > Hi! > > Just to clarify why I prefer the second solution, I think what debian does is > shipping precompiled versions of extensions, so technically the gemspec > shipped in the debian should include no extensions at all. This is

Bug#972702: ruby-bundler: dependency resolution fails for compiled gems

2020-10-29 Thread deivid
El 29/10/20 a las 13:14, Antonio Terceiro escribió: On Thu, Oct 29, 2020 at 11:17:59AM +0100, David Rodríguez wrote: Hi! Just to clarify why I prefer the second solution, I think what debian does is shipping precompiled versions of extensions, so technically the gemspec shipped in the debian

Bug#972702: ruby-bundler: dependency resolution fails for compiled gems

2020-10-29 Thread deivid
Hi! Just to clarify why I prefer the second solution, I think what debian does is shipping precompiled versions of extensions, so technically the gemspec shipped in the debian should include no extensions at all. This is something some upstream gems already do. Take, for example, google-protob

Bug#972702: ruby-bundler: dependency resolution fails for compiled gems

2020-10-28 Thread Antonio Terceiro
On Wed, Oct 28, 2020 at 07:02:06PM -0300, Lucas Kanashiro wrote: > Thanks to David Rodriguez (our dear bundler upstream maintainer :) I was > able to workaround the bug locally and understand a bit better what is going > on. > > The source of this problem is this commit: > > https://github.com/ru

Bug#972702: ruby-bundler: dependency resolution fails for compiled gems

2020-10-28 Thread Lucas Kanashiro
Thanks to David Rodriguez (our dear bundler upstream maintainer :) I was able to workaround the bug locally and understand a bit better what is going on. The source of this problem is this commit: https://github.com/rubygems/rubygems/commit/226ec115fe503bcc93bffdf5cd3e8a668890b4d8 Quoting Dav

Bug#972702: ruby-bundler: dependency resolution fails for compiled gems

2020-10-28 Thread Lucas Kanashiro
Running the same command with verbose enabled tells us that bundler ignores the ffi gem because it's missing extensions: root@rubygems-test:~/test# bundle --local --verbose Running `bundle install --local --verbose` with bundler 2.2.0.rc.1 Don't run Bundler as root. Bundler can ask for sudo if i

Bug#972702: ruby-bundler: dependency resolution fails for compiled gems

2020-10-24 Thread Lucas Kanashiro
It seems the search path is not right in this newer ruby-bundler version. Using the following Gemfile and running 'bundle --local' works fine. root@rubygems-test:~/test# cat Gemfile path "/usr/share/rubygems-integration/2.7.0" do   gem 'ffi' end root@rubygems-test:~/test# bundle --local Don't run

Bug#972702: ruby-bundler: dependency resolution fails for compiled gems

2020-10-22 Thread Antonio Terceiro
Package: ruby-bundler Version: 2.2.0~rc.1 Severity: grave Justification: renders package unusable 8<8<8<- $ cat Gemfile source 'https://rubygems.org' gem 'ffi' $ bundle --local Could not find gem 'ffi' in any of the gem sources listed