Re: ruby-pry-byebug: ships /usr/bin/rubocop, /usr/bin/bundle

No problem! If a ".gem" file comes with `bin/console` and `bin/setup` files, it's almost 100% of the times a bug upstream. I see that gem2deb automatically excludes these: https://salsa.debian.org/ruby-team/gem2deb/-/blob/f8a0eb655d990079f87c96eb96bd4073759d2b59/lib/gem2deb/gem_installer.rb#L2

Re: ruby-pry-byebug: ships /usr/bin/rubocop, /usr/bin/bundle

On Tue, Feb 25, 2020 at 12:24 pm, deivid wrote: These kind of files should never be shipped since they are only meant for development. The information about the executable files that should be shipped with a gem can be found in the gemspec. In this case,

Re: ruby-pry-byebug: ships /usr/bin/rubocop, /usr/bin/bundle

These kind of files should never be shipped since they are only meant for development. The information about the executable files that should be shipped with a gem can be found in the gemspec. In this case, https://github.com/deivid-rodriguez/pry-byebug/blob/6021d2c01b2d9d00bbf7caace7beab9bf31

Re: ruby-pry-byebug: ships /usr/bin/rubocop, /usr/bin/bundle

On Wed, 27 Nov 2019 15:57:30 +0100 Andreas Beckmann wrote: > during a test with piupart../ruby-shoulda-matchers_4.3.0.orig.tar.xz,s I noticed your package failed to install > because it tries to overwrite other packages files. > > From the attached log (scroll to the bottom...): > > Preparing