Re: Call for help!

2019-08-22 Thread Samyak Jain
On Fri, 23 Aug 2019, 02:46 Utkarsh Gupta, wrote: > Hey, > > On Thu, Aug 22, 2019 at 9:18 PM Antonio Terceiro > wrote: > >> On Wed, Aug 21, 2019 at 11:24:12PM +0530, Utkarsh Gupta wrote: >> > Hey, >> > >> > While working on some packages, I hit an obstacle pertaining bundler. >> > While we usuall

Re: Call for help!

2019-08-22 Thread Utkarsh Gupta
Hey, On Thu, Aug 22, 2019 at 9:18 PM Antonio Terceiro wrote: > On Wed, Aug 21, 2019 at 11:24:12PM +0530, Utkarsh Gupta wrote: > > Hey, > > > > While working on some packages, I hit an obstacle pertaining bundler. > > While we usually patched out bundler, ruby-combustion seems to be using > > bun

Re: Call for help!

2019-08-22 Thread Antonio Terceiro
On Wed, Aug 21, 2019 at 11:24:12PM +0530, Utkarsh Gupta wrote: > Hey, > > While working on some packages, I hit an obstacle pertaining bundler. > While we usually patched out bundler, ruby-combustion seems to be using > bundler. > Thus if any and every package that uses ruby-combustion is patched

Re: Call for help!

2019-08-22 Thread Joseph Herlant
So I spent some time trying to debug the issue but came up empty. The load path are really similar: During the build: - LOAD_PATH - /<>/spec /<>/spec /<>/lib /<>/debian/ruby-arbre/usr/lib/ruby/vendor_ruby . /usr/share/rubygems-integration/all/gems/did_you_mean-1.2.1/lib /usr/local/lib/sit

Re: Call for help!

2019-08-22 Thread Joseph Herlant
Hi Utkarsh, Looking at ruby arbre right now I'm able to reproduce your issue using gbp buildpackage --run-autopkgtest (with a fresh sbuild chroot for unstable). > Now, the packages using bundler and ruby-combustion, their autopkgtest > fails (build is perfectly fine!) saying: > "File does not exi