Age | Commit message (Collapse) | Author |
|
If one upgrades the default copy of Bundler through `gem update
--system`, and then reinstalls Ruby without removing the previous copy.
Then the new installation will have a correct default bundler gemspec,
but a higher copy installed in site_dir.
This causes a crash when running Bundler and prints the bug report
template.
This could probably be fixed in Ruby install script, by removing any
previous Bundler default copies, but if the problem is already there, I
think it's best to print a proper user error.
https://github.com/rubygems/rubygems/commit/ada6de765d
|
|
[Bug #20421]
The bug was fixed in Ruby 3.3 via 9dcdffb8bf8a3654fd78bf1a58b30c8e13888a7a
|
|
This gets in the middle if we ever start allowing to build as if using a
different RubyGems version than the one being run.
This could be useful to make `gem rebuild` a little more usable, and
it's already done by Bundler specs which already make this method a noop
when they need this.
I'm not sure forcefully setting this, even if user explicitly specified
something else is helpful.
Since this could potentially prevent gems explicitly setting a constant
RubyGems version from building, I changed the error of incorrect
RubyGems version from a hard error to a warning, since it will start
happening in those cases if we stop overwriting the version.
https://github.com/rubygems/rubygems/commit/45676af80d
|
|
For that particular spec, the empty lines' presence is not relevant.
So let's remove them to make the spec easier to maintain.
|
|
|
|
|
|
|
|
|
|
|
|
To make sure we can always update to the latest resolvable version for
each gem explicitly requested for update, we first run a full update,
and then add explicit exact requirements to the resolved versions. This
may lead into conflicts, but our resolver already automatically parses
those and unlocks additional gems to fix them.
https://github.com/rubygems/rubygems/commit/01c0bf34f0
|
|
https://github.com/rubygems/rubygems/commit/241d0aafcd
|
|
https://github.com/rubygems/rubygems/commit/924f87c8a9
|
|
An old platform related bug fix made some existing lockfiles no longer
work because they included invalid platforms. So to make it backwards
compatible, code was added to remove invalid platforms from the lockfile
before resolution. This is skipped though when Gemfile has changed
dependencies because in that case we will be re-resolving anyways.
However, in the `bundle update` case, the detection of "dependencies
have changed" was not actually working making Bundler remove all
platforms and not be able to resolve.
https://github.com/rubygems/rubygems/commit/6452adfd62
|
|
|
|
|
|
|
|
|
|
We have some places that already use `bundle config auto_install true`,
ie:
https://github.com/technicalpickles/rubygems/blob/7a144f3374f6a400cc9832f072dc1fc0bca8c724/bundler/lib/bundler/cli.rb#L11
This applies the same logic (copy and pasted) to happen when you
`require "bundler/setup"`.
https://github.com/rubygems/rubygems/commit/bb3c922341
|
|
|
|
I apparently did that to fix some issue with case insensitivity but I
didn't add a spec, and I think not upcasing should not cause issues.
https://github.com/rubygems/rubygems/commit/1b6f23275a
|
|
https://github.com/rubygems/rubygems/commit/5d9bf03c59
|
|
https://github.com/rubygems/rubygems/commit/e3d180620c
|
|
https://github.com/rubygems/rubygems/commit/b373b7ed0d
|
|
Signed-off-by: careworry <worrycare@outlook.com>
|
|
[Feature #18576]
Since outright renaming `ASCII-8BIT` is deemed to backward incompatible,
the next best thing would be to only change its `#inspect`, particularly
in exception messages.
|
|
https://github.com/rubygems/rubygems/commit/e8a363713e
|
|
musl vs gnu case
This case is for not locking things like `arm-darwin-23` when the
lockfile already includes `arm-darwin`, so that we don't infinitely keep
redundant versioned platforms in the lockfile when not necessary.
We detect this with `Gem::Platform#===`. For example,
`Gem::Platform.new("arm-darwin-23") === Gem::Platform.new("arm-darwin")`
but they're not `==`.
However, in the case of `-musl` vs `-gnu`, those act as the platform
"version", but `===` is not commutative for them. This is explained in
`===` docs.
We only want to exclude the local platform in situations when
`Gem::Platform#===` is actually commutative.
https://github.com/rubygems/rubygems/commit/8099c4face
|
|
* Improve consistency of `Fiber.current.raise`.
|
|
|
|
Accecpt the same arguments as `caller` and `caller_locations`.
|
|
|
|
|
|
invocation in specs, add banner text for CLI recommending single quotes
https://github.com/rubygems/rubygems/commit/6d2cf955f9
|
|
Bundler online documentation says that if the gem is located within a subdirectory of a git repository,
you can use the `:glob` option to specify the location of its .gemspec
`gem 'cf-copilot', git: 'https://github.com/cloudfoundry/copilot', glob: 'sdk/ruby/*.gemspec'`
This change allows for equivalent functionality from the bundler CLI
`bundle add cf-copilot --git=https://github.com/cloudfoundry/copilot --glob=sdk/ruby/*.gemspec`
https://github.com/rubygems/rubygems/commit/91052e5868
|
|
|
|
This affected both CLI and Gemfile installs
https://github.com/rubygems/rubygems/commit/a0d101a8df
|
|
|
|
The backtick method recieves a frozen string unless it is interpolated.
Otherwise the string held in the ISeq could be mutated by a custom
backtick method.
|
|
|
|
|
|
Fixes the following error:
````
$ ruby /home/deivid/code/rubygems/rubygems/bundler/spec/support/bundle.rb clean --force
--- ERROR REPORT TEMPLATE -------------------------------------------------------
```
TypeError: no implicit conversion of Pathname into String
/home/deivid/code/rubygems/rubygems/bundler/lib/bundler/runtime.rb:167:in `match'
/home/deivid/code/rubygems/rubygems/bundler/lib/bundler/runtime.rb:167:in `block in clean'
/home/deivid/code/rubygems/rubygems/bundler/lib/bundler/runtime.rb:164:in `each'
/home/deivid/code/rubygems/rubygems/bundler/lib/bundler/runtime.rb:164:in `clean'
/home/deivid/code/rubygems/rubygems/bundler/lib/bundler/cli/clean.rb:13:in `run'
/home/deivid/code/rubygems/rubygems/bundler/lib/bundler/cli.rb:590:in `clean'
/home/deivid/code/rubygems/rubygems/bundler/lib/bundler/vendor/thor/lib/thor/command.rb:28:in `run'
/home/deivid/code/rubygems/rubygems/bundler/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
/home/deivid/code/rubygems/rubygems/bundler/lib/bundler/vendor/thor/lib/thor.rb:527:in `dispatch'
/home/deivid/code/rubygems/rubygems/bundler/lib/bundler/cli.rb:34:in `dispatch'
/home/deivid/code/rubygems/rubygems/bundler/lib/bundler/vendor/thor/lib/thor/base.rb:584:in `start'
/home/deivid/code/rubygems/rubygems/bundler/lib/bundler/cli.rb:28:in `start'
/home/deivid/code/rubygems/rubygems/bundler/exe/bundle:28:in `block in <top (required)>'
/home/deivid/code/rubygems/rubygems/bundler/lib/bundler/friendly_errors.rb:117:in `with_friendly_errors'
/home/deivid/code/rubygems/rubygems/bundler/exe/bundle:20:in `<top (required)>'
/home/deivid/code/rubygems/rubygems/bundler/spec/support/bundle.rb:5:in `load'
/home/deivid/code/rubygems/rubygems/bundler/spec/support/bundle.rb:5:in `<main>'
```
(...)
````
https://github.com/rubygems/rubygems/commit/ff7ce7eb6d
|
|
This is a global variable and may happen to be set to 4 elsewhere.
http://ci.rvm.jp/logfiles/brlog.trunk.20240403-054356#L1707
```
The if expression with a boolean range ('flip-flop' operator) warns when Integer literals are used instead of predicates FAILED
Expected [0, 1, 2, 3, 4, 5, 6, 7, 8, 9] == []
to be truthy but was false
```
|
|
|
|
|
|
|
|
everything
https://github.com/rubygems/rubygems/commit/1ea44b3749
|
|
So that we don't need to reverse the Array.
https://github.com/rubygems/rubygems/commit/aeea5e2e00
|
|
We do that when first caching versions, and then it's no longer
necessary.
https://github.com/rubygems/rubygems/commit/ede15847db
|
|
caching maintains the right lockfile
https://github.com/rubygems/rubygems/commit/65839757e6
|
|
|