From: deivid.rodriguez@...
Date: 2019-02-13T16:09:42+00:00
Subject: [ruby-core:91532] [Ruby trunk Bug#15582] default/bundler-1.17.2.gemspec has no file list

Issue #15582 has been updated by deivid (David Rodr��guez).


Yes, since rubygems 2.6.1 ships with rubygems 3.0.1, running `gem update --system` will update to the latest version (3.0.2) and force reinstallation of the default bundler gem.

However, I have noticed that other default gems suffer from this issue, for example the `etc` gem. In that case, a workaround is to reinstall the same version of the default gem, for example, `gem install etc:1.0.1 --default`.

----------------------------------------
Bug #15582: default/bundler-1.17.2.gemspec has no file list
https://bugs.ruby-lang.org/issues/15582#change-76791

* Author: mame (Yusuke Endoh)
* Status: Closed
* Priority: Normal
* Assignee: hsbt (Hiroshi SHIBATA)
* Target version: 
* ruby -v: ruby 2.6.1p33 (2019-01-30 revision 66950) [x86_64-linux]
* Backport: 2.4: DONTNEED, 2.5: DONTNEED, 2.6: REQUIRED
----------------------------------------
Ruby 2.6.1's *prefix*/lib/ruby/gems/2.6.0/specifications/default/bundler-1.17.2.gemspec seems wrong.

```
  s.files = ["bundler.rb".freeze, "exe/bundle".freeze, "exe/bundler".freeze]
```

It should have "bundler/setup.rb", "bundler/version.rb", etc.

This causes a trouble depending upon the order of `require` when a different version of bundler is installed:

```
$ gem list bundler

*** LOCAL GEMS ***

bundler (1.17.3, default: 1.17.2)

$ ruby -e 'require "bundler/version"; require "bundler"; p Bundler::VERSION'
"1.17.2"

$ ruby -e 'require "bundler"; require "bundler/version"; p Bundler::VERSION'
"1.17.3"
```

---Files--------------------------------
15582-bundler-gemspec.patch (5.17 KB)


-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>