aboutsummaryrefslogtreecommitdiffstats
path: root/lib/rubygems
Commit message (Collapse)AuthorAgeFilesLines
* Merge prepare version of RubyGems 3.2.0Hiroshi SHIBATA2020-12-0883-511/+1124
|
* RubyGems certs - remove AddTrust, add GlobalSign Root R3MSP-Greg2020-12-062-25/+21
|
* Merge rubygems-3.2.0.rc.2Hiroshi SHIBATA2020-10-153-14/+15
|
* Add missing fileutils requireDavid Rodríguez2020-10-061-1/+4
| | | | | 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.
* [rubygems/rubygems] Add writable check for cache dirxndcn2020-09-281-2/+3
| | | | | | Sometimes "install_dir/cache" directory is not writable although "install_dir" is writable. https://github.com/rubygems/rubygems/commit/665221cb69
* [rubygems/rubygems] Avoid duplicated generation of APISpecification objectsYusuke Endoh2020-09-281-5/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* [rubygems/rubygems] Eval defaults with frozen_string_literal: trueJean Boussier2020-09-281-0/+2
| | | | https://github.com/rubygems/rubygems/commit/d498ae3d62
* [rubygems/rubygems] Remove last remaining line of output from `gem update ↵Ellen Marie Dash2020-09-281-1/+1
| | | | | | --system --silent` https://github.com/rubygems/rubygems/commit/038203aaf8
* [rubygems/rubygems] Add test for "gem update --system --silent"Ellen Marie Dash2020-09-281-2/+2
| | | | https://github.com/rubygems/rubygems/commit/c3fb0db930
* [rubygems/rubygems] Have "gem update --system" pass through the --silent flag.Ellen Marie Dash2020-09-281-0/+1
| | | | https://github.com/rubygems/rubygems/commit/5a1e56e892
* [rubygems/rubygems] Added Ruby version for oldest supported version of rubygemsHiroshi SHIBATA2020-09-281-0/+1
| | | | https://github.com/rubygems/rubygems/commit/dd87d70f51
* Disallow downgrades to too old versionsDavid Rodríguez2020-09-281-1/+16
| | | | | Consider the version original included with each ruby as the minimum supported version.
* [rubygems/rubygems] Add --dryrun to the deprecated options when showing the ↵bronzdoc2020-09-281-1/+1
| | | | | | help message https://github.com/rubygems/rubygems/commit/38230a77c1
* [rubygems/rubygems] We don't need shortucts for a deprecated flagbronzdoc2020-09-281-1/+1
| | | | https://github.com/rubygems/rubygems/commit/087a1f9720
* [rubygems/rubygems] Deprecate --dryrunbronzdoc2020-09-281-1/+7
| | | | https://github.com/rubygems/rubygems/commit/1715610648
* [rubygems/rubygems] Make --dry-run flag consistent across rubygems commandsbronzdoc2020-09-281-1/+1
| | | | https://github.com/rubygems/rubygems/commit/addc644cad
* Added `--platform` option to `build` commandNobuyoshi Nakada2020-09-282-0/+9
|
* Revert "Manually merged from https://github.com/rubygems/rubygems/pull/2636"Hiroshi SHIBATA2020-09-23138-364/+0
| | | | | 31a6eaabc165d8a222e176f2c809d90622d88ec2 is obsoleted with https://github.com/rubygems/rubygems/pull/3820
* Manually merged from https://github.com/rubygems/rubygems/pull/2636Hiroshi SHIBATA2020-09-23138-0/+364
| | | | Enable Style/EmptyLinesAroundClassBody rubocop cop.
* Revert changes to rdoc & rubygems regarding Tempfile.open(&block)Benoit Daloze2020-08-291-0/+2
| | | | | * They likely want to support older Ruby/tempfile versions * Reverts part of e8c3872555fc85640505974e6b1c39d315572689
* Simplify Tempfile.open calls with a block as they now unlink the file ↵Benoit Daloze2020-08-291-2/+0
| | | | automatically
* [rubygems/rubygems] Read path binarilyDavid Rodríguez2020-07-311-1/+1
| | | | | | I believe this should fix a flaky test on Windows. https://github.com/rubygems/rubygems/commit/a516b49a0a
* [rubygems/rubygems] Don't format executables on `gem update --system`David Rodríguez2020-07-311-1/+1
| | | | | | | | 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
* [rubygems/rubygems] unset XDG_* environmental variables for testing of rubygems.Hiroshi SHIBATA2020-07-311-0/+3
| | | | https://github.com/rubygems/rubygems/commit/539fd9a39a
* [rubygems/rubygems] Revert "Disallow warnings to creep into the test suite"David Rodríguez2020-07-311-14/+0
| | | | | | | | | | 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
* [rubygems/rubygems] Remove fileutils autoloadDavid Rodríguez2020-07-312-1/+1
| | | | https://github.com/rubygems/rubygems/commit/dca345441f
* [rubygems/rubygems] Remove explicit require for autoloaded constantDavid Rodríguez2020-07-312-2/+0
| | | | https://github.com/rubygems/rubygems/commit/a54230093e
* [rubygems/rubygems] Let more exceptions flowDavid Rodríguez2020-07-311-4/+3
| | | | | | | | | | | | | | | | 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
* [rubygems/rubygems] Install plugins to user directoryNobuyoshi Nakada2020-07-311-0/+1
| | | | | | | | 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
* [rubygems/rubygems] Remove more unnecessary requiresDavid Rodríguez2020-07-315-6/+0
| | | | | | Since `rubygems/util` is autoloaded. https://github.com/rubygems/rubygems/commit/52a9f88b99
* [rubygems/rubygems] The file is only ever required when openssl is availableDavid Rodríguez2020-07-311-2/+0
| | | | https://github.com/rubygems/rubygems/commit/41976ef3ec
* [rubygems/rubygems] Gem::Specification#to_ruby doesn't need `openssl`David Rodríguez2020-07-311-2/+2
| | | | | | | | | 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
* [rubygems/rubygems] Make sure tests at least load without opensslDavid Rodríguez2020-07-311-1/+1
| | | | https://github.com/rubygems/rubygems/commit/054d57f74b
* [rubygems/rubygems] Move openssl require to a separate fileDavid Rodríguez2020-07-312-6/+8
| | | | | | So it can be reused. https://github.com/rubygems/rubygems/commit/b9fc6e40db
* [rubygems/rubygems] In the rubies we support `Exception#path` is always thereDavid Rodríguez2020-07-311-2/+1
| | | | https://github.com/rubygems/rubygems/commit/babf943144
* [rubygems/rubygems] Only require what we are usingDavid Rodríguez2020-07-311-1/+1
| | | | https://github.com/rubygems/rubygems/commit/d92b94f3cf
* [rubygems/rubygems] Let the original error happenDavid Rodríguez2020-07-311-6/+0
| | | | | | It will give more useful information. https://github.com/rubygems/rubygems/commit/efcecb5af5
* [rubygems/rubygems] Remove unnecessary stuffDavid Rodríguez2020-07-311-6/+0
| | | | | | The `rubygems/security` require already does this. https://github.com/rubygems/rubygems/commit/bbb444b6f1
* [rubygems/rubygems] Reword warningbronzdoc2020-07-311-1/+1
| | | | https://github.com/rubygems/rubygems/commit/cbd4abf8cf
* [rubygems/rubygems] Warn on duplicate dependency in a specificationbronzdoc2020-07-311-0/+4
| | | | https://github.com/rubygems/rubygems/commit/af3e5f7883
* [rubygems/rubygems] Support PATH's using `File::ALT_SEPARATOR` in ↵David Rodríguez2020-07-311-0/+2
| | | | | | | | `Gem::Installer` Co-authored-by: MSP-Greg <MSP-Greg@users.noreply.github.com> https://github.com/rubygems/rubygems/commit/710b969b60
* [rubygems/rubygems] Move traling `if` to the same line for readablityDavid Rodríguez2020-07-311-2/+1
| | | | https://github.com/rubygems/rubygems/commit/d722b8b578
* [rubygems/rubygems] Prefer the standard separator on WindowsDavid Rodríguez2020-07-311-1/+1
| | | | | | | | | 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
* [rubygems/rubygems] fix missing identationColby Swandale2020-07-311-1/+1
| | | | https://github.com/rubygems/rubygems/commit/2cca6714f3
* [rubygems/rubygems] Deduplicate the requirement operators in memoryJean Boussier2020-07-311-1/+1
| | | | https://github.com/rubygems/rubygems/commit/9963d33cf2
* [rubygems/rubygems] Fix Kernel#warn override to handle backtrace location ↵Jeremy Evans2020-07-311-4/+5
| | | | | | | | | | | 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
* [rubygems/rubygems] Ignore internal frames in RubyGems' Kernel#warnBenoit Daloze2020-07-311-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | * 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
* [rubygems/rubygems] Disallow warnings to creep into the test suiteDavid Rodríguez2020-07-311-0/+14
| | | | https://github.com/rubygems/rubygems/commit/694e6afee7
* [rubygems/rubygems] Fix test warningDavid Rodríguez2020-07-311-1/+1
| | | | https://github.com/rubygems/rubygems/commit/f4c4cddb68
* [rubygems/rubygems] Don't `super` on main test setupDavid Rodríguez2020-07-311-2/+0
| | | | | | | The `teardown` method doesn't call it either and I don't think it's necessary. https://github.com/rubygems/rubygems/commit/ca2a5d485d
generated by cgit v1.2.3 (git 2.39.1) at 2024-08-17 14:13:59 +0000