Re: debugging "File does not exist: bundler/setup" under autopkgtest (was "Call for help!")

To: debian-ruby@lists.debian.org
Subject: Re: debugging "File does not exist: bundler/setup" under autopkgtest (was "Call for help!")
From: Joseph Herlant <aerostitch@debian.org>
Date: Fri, 23 Aug 2019 09:08:17 -0700
Message-id: <[🔎] CAPQicOwR+ruSHAfpN1iC5fiqTcFN4TfQrDuNpcK4a8L-gk=ecA@mail.gmail.com>
In-reply-to: <[🔎] 20190823110700.GA21950@debian.org>
References: <[🔎] a62501a3-64c9-baab-d9aa-b2b6bce1aef4@gmail.com> <[🔎] 20190822154128.GA31214@debian.org> <[🔎] CAPP0f958Pvn3dJDPsLvKKwB58-eV+CwysXOVp3PAPBUHhjKtuQ@mail.gmail.com> <[🔎] 20190823110700.GA21950@debian.org>

Hi Antonio,

Thanks for that awesome walk-though and findings!
Where would you stand on having gem2deb-test-runner moving out the
Gemfile.lock like it does with lib for autopkgtest mode?
I don't see a lot of value in keeping the Gemfile.lock in an
environment where the gems are system-packaged. (Happy to do a MR if
you think it would be a good path to use).

Thanks for your help,
Joseph

Reply to:

Follow-Ups:
- Re: debugging "File does not exist: bundler/setup" under autopkgtest (was "Call for help!")
  - From: Antonio Terceiro <terceiro@debian.org>

References:
- Call for help!
  - From: Utkarsh Gupta <guptautkarsh2102@gmail.com>
- Re: Call for help!
  - From: Antonio Terceiro <terceiro@debian.org>
- Re: Call for help!
  - From: Utkarsh Gupta <guptautkarsh2102@gmail.com>
- debugging "File does not exist: bundler/setup" under autopkgtest (was "Call for help!")
  - From: Antonio Terceiro <terceiro@debian.org>

Prev by Date: debugging "File does not exist: bundler/setup" under autopkgtest (was "Call for help!")
Next by Date: RFS: ruby-combustion
Previous by thread: debugging "File does not exist: bundler/setup" under autopkgtest (was "Call for help!")
Next by thread: Re: debugging "File does not exist: bundler/setup" under autopkgtest (was "Call for help!")
Index(es):
- Date
- Thread