| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
| |
On my system, the error was being hidden by the presence of a YARD
rubygems plugin that was providing the require and making things work.
|
|
|
|
|
|
| |
Sometimes "install_dir/cache" directory is not writable although "install_dir" is writable.
https://github.com/rubygems/rubygems/commit/665221cb69
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As far as I could see, `Gem::Resolver::APISpecification` objects are
supposed to be immutable. If my guessing is correct, then we can cache
and reuse its instances for performance.
At least, `rake` passes on my machine.
Before this change:
```
$ time ruby -I lib bin/gem install --no-doc aws-sdk
Successfully installed aws-sdk-3.0.1
1 gem installed
real 0m37.104s
user 0m36.952s
sys 0m0.333s
```
After this change:
```
$ time ruby -I lib bin/gem install --no-doc aws-sdk
Successfully installed aws-sdk-3.0.1
1 gem installed
real 0m23.905s
user 0m23.740s
sys 0m0.365s
```
https://github.com/rubygems/rubygems/commit/7e8fbba85c
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/d498ae3d62
|
|
|
|
|
|
| |
--system --silent`
https://github.com/rubygems/rubygems/commit/038203aaf8
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/c3fb0db930
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/5a1e56e892
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/dd87d70f51
|
|
|
|
|
| |
Consider the version original included with each ruby as the minimum
supported version.
|
|
|
|
|
|
| |
help message
https://github.com/rubygems/rubygems/commit/38230a77c1
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/087a1f9720
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/1715610648
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/addc644cad
|
| |
|
|
|
|
|
| |
31a6eaabc165d8a222e176f2c809d90622d88ec2 is obsoleted with
https://github.com/rubygems/rubygems/pull/3820
|
|
|
|
| |
Enable Style/EmptyLinesAroundClassBody rubocop cop.
|
|
|
|
|
| |
* They likely want to support older Ruby/tempfile versions
* Reverts part of e8c3872555fc85640505974e6b1c39d315572689
|
|
|
|
| |
automatically
|
|
|
|
|
|
| |
I believe this should fix a flaky test on Windows.
https://github.com/rubygems/rubygems/commit/a516b49a0a
|
|
|
|
|
|
|
|
| |
This restores 3.0 behavior and goes back to not formatting executables
by default on `gem update --system`. This is friendlier for jruby and
doesn't really affect OS packagers.
https://github.com/rubygems/rubygems/commit/1a504b651d
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/539fd9a39a
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 694e6afee769ffb3168a564ee7d315af2a934993.
It was failed on Windows and I'm unsure why. Also, the check seems
brittle since it could fail potentially fail because of warnings outside
of our control.
https://github.com/rubygems/rubygems/commit/908e9344dd
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/dca345441f
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/a54230093e
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If any error happens while verifying a package entry, it doesn't mean
that the package is corrupt. It could be a bug in rubygems, for example.
This in fact happened in CI and the current error doesn't make it easy
to troubleshoot the root cause, since it doesn't provide a backtrace.
See
https://github.com/rubygems/rubygems/pull/3807/checks?check_run_id=862526615.
So I propose to let the exception happens. There was something useful
about the previous message, which is the file entry where the error
happened, so I'm keeping that information in a warning message.
https://github.com/rubygems/rubygems/commit/ece87d858f
|
|
|
|
|
|
|
|
| |
Fixes the `Gem::FilePermissionError` without the privilege.
Initialize `@plugins_dir` to the user gem directory, when
installing with `--user` option.
https://github.com/rubygems/rubygems/commit/21a71ac769
|
|
|
|
|
|
| |
Since `rubygems/util` is autoloaded.
https://github.com/rubygems/rubygems/commit/52a9f88b99
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/41976ef3ec
|
|
|
|
|
|
|
|
|
| |
The `openssl` require when openssl not present was having the
side-effect the our custom require fallbacks would end up loading `Gem::Specification.stubs`.
Co-authored-by: Alyssa Ross <hi@alyssa.is>
https://github.com/rubygems/rubygems/commit/22c4ded4ad
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/054d57f74b
|
|
|
|
|
|
| |
So it can be reused.
https://github.com/rubygems/rubygems/commit/b9fc6e40db
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/babf943144
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/d92b94f3cf
|
|
|
|
|
|
| |
It will give more useful information.
https://github.com/rubygems/rubygems/commit/efcecb5af5
|
|
|
|
|
|
| |
The `rubygems/security` require already does this.
https://github.com/rubygems/rubygems/commit/bbb444b6f1
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/cbd4abf8cf
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/af3e5f7883
|
|
|
|
|
|
|
|
| |
`Gem::Installer`
Co-authored-by: MSP-Greg <MSP-Greg@users.noreply.github.com>
https://github.com/rubygems/rubygems/commit/710b969b60
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/d722b8b578
|
|
|
|
|
|
|
|
|
| |
It seems like the most common case since it requires no tricks on our
CI environment.
Co-authored-by: MSP-Greg <MSP-Greg@users.noreply.github.com>
https://github.com/rubygems/rubygems/commit/751c475574
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/2cca6714f3
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/9963d33cf2
|
|
|
|
|
|
|
|
|
|
|
| |
with nil path
It's very unlikely to hit this case, but it is possible, as
Thread::Backtrace::Location#path can return nil if the location is
a cfunc with no previous iseq. See location_path in vm_backtrace.c
in Ruby.
https://github.com/rubygems/rubygems/commit/511935645a
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* See https://github.com/oracle/truffleruby/issues/2046
* `<internal:` is a common prefix also used by core Ruby files in CRuby.
* test_no_kernel_require_in_*warn_with_uplevel already test this.
* Unfortunately just skipping `<internal:` in the Ruby implementation
is not enough, because RubyGems' #warn would not skip the
`<internal:` require (TruffleRuby defines #require in Ruby),
and the Ruby implementation's #warn would not skip
RubyGems's #require. The #caller_locations(0) look like this:
warnee.rb:1:in `<top (required)>' # where #warn is called
<internal:core> core/kernel.rb:234:in `gem_original_require' # not skipped by RubyGems' warn, skipped by the Ruby impl
rubygems/core_ext/kernel_require.rb:54:in `require' # not skipped by the Ruby impl's warn, what would be shown without this fix
warn.rb:1:in `<main>' # what would be correct
warn.rb is
require "warnee"
warnee.rb is
puts caller_locations(0), nil
warn "oops", uplevel: 1
https://github.com/rubygems/rubygems/commit/7c838f7419
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/694e6afee7
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/f4c4cddb68
|
|
|
|
|
|
|
| |
The `teardown` method doesn't call it either and I don't think it's
necessary.
https://github.com/rubygems/rubygems/commit/ca2a5d485d
|