| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Fix gem pristine not accounting for user installed gems. Pull request
#2914 by Luis Sagastume.
* Refactor keyword argument test for Ruby 2.7. Pull request #2947 by
SHIBATA Hiroshi.
* Fix errors at frozen Gem::Version. Pull request #2949 by Nobuyoshi
Nakada.
* Remove taint usage on Ruby 2.7+. Pull request #2951 by Jeremy Evans.
* Check Manifest.txt is up to date. Pull request #2953 by David Rodríguez.
* Clarify symlink conditionals in tests. Pull request #2962 by David
Rodríguez.
* Update command line parsing to work under ps. Pull request #2966 by
David Rodríguez.
* Properly test `Gem::Specifications.stub_for`. Pull request #2970 by
David Rodríguez.
* Fix Gem::LOADED_SPECS_MUTEX handling for recursive locking. Pull request
#2985 by MSP-Greg.
|
|
|
|
|
| |
And revert "Relaxed warning assertions",
6f9be8505d172b110ec449478a791d70b9b74afb.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some test cases in rubygems assume that /tmp/Gemfile does not exist.
If it does, they fail with very difficult-to-understand message:
```
[ 149/2108] TestGemBundlerVersionFinder#test_bundler_version_with_bundle_update_bundler = 0.00
1) Failure:
TestGemBundlerVersionFinder#test_bundler_version_with_bundle_update_bundler [/home/mame/work/ruby/test/rubygems/test_gem_bundler_version_finder.rb:38]:
Expected Gem::Version.new("2.0.2") to be nil.
```
I spent one hour to debug this issue. To prevent the same accident,
this change makes the test suite stop when /tmp/Gemfile explicitly.
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/97e9768612
|
|
|
|
|
|
| |
https://gist.github.com/ko1/a88834d744a0682711dab53fd9015a04#file-brlog-trunk-nopara-20191005-235153-L393-L472
https://github.com/rubygems/rubygems/commit/707408d8e7
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/1bd77f53df
|
|
|
|
|
|
|
|
|
|
| |
This reverts commits:
* 2a490d5660ac869f8f2bbcec4887b1dc2950643f
Suppress assert_match warnings.
* d4a86e407ec2057c2c7ad757aa76dad757f34c3a
Assert warnings message for the last argument is keyword parameter.
|
|
|
|
|
|
| |
https://bugs.ruby-lang.org/issues/16189
https://github.com/rubygems/rubygems/commit/e331222163
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/05146bb2fd
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/892bfc11fe
|
|
|
|
|
|
| |
For better messages at failures.
https://github.com/rubygems/rubygems/commit/971455b16e
|
|
|
|
|
|
| |
It is `assert_eqal(expected, actual)`.
https://github.com/rubygems/rubygems/commit/1d6197a090
|
| |
|
| |
|
|
|
|
|
|
| |
And test the fix we're adding.
https://github.com/rubygems/rubygems/commit/6f86637b98
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/8cdb2fd66f
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/7c5b66f9ef
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/8a7e27381c
|
|
|
|
|
|
| |
Previously it wouldn't play nice with the bundler version finder.
https://github.com/rubygems/rubygems/commit/d8bb81556d
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/2e65f7d4ae
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/b1d825ab3a
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes #2290.
1. `Gem::Specification.date` returns SOURCE_DATE_EPOCH when defined,
2. this commit makes RubyGems set it _persistently_ when not provided.
This combination means that you can build a gem, check the build time,
and use that value to generate a new build -- and then verify they're
the same.
https://github.com/rubygems/rubygems/commit/d830d53f59
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/5b81f364ae
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/d4fc383497
|
|
|
|
|
|
| |
surrounded by a single space.
https://github.com/rubygems/rubygems/commit/eaa38ebeb1
|
|
|
|
|
|
| |
is specified
https://github.com/rubygems/rubygems/commit/547947bbf0
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/c8913e37a7
|
|
|
|
|
|
| |
name specified
https://github.com/rubygems/rubygems/commit/38c72fd145
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/ab186266b7
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/dc70c5a192
|
|
|
|
|
|
|
| |
Instead, display an informative message saying that uninstallation of
specific versions is being skipped because of being default gems.
https://github.com/rubygems/rubygems/commit/b44845aa1d
|
|
|
|
|
|
|
| |
Otherwise it detects duplicate methods here, because it doesn't see that
we are reopening the class in two different places.
https://github.com/rubygems/rubygems/commit/ae3fb47f5f
|
| |
|
|
|
|
| |
This reverts commit 75d29db8f965893bb6ab38b9008abc80cdda246e.
|
|
|
|
| |
This reverts commit 00cd5d74cecb6aa4a184e57e2b8246ef6e45d458.
|
|
|
|
|
|
| |
https://github.com/rubygems/rubygems/pull/1868 changes the behavior
of require when it used with -I options. Therefore, the options of
ruby repository was different from rubygems/rubygems.
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/c0275ee537
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/bb02953a97
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/7964917bbc
|
|
|
|
|
|
| |
Gem::Command#show_lookup_failure with a parameter to suppress suggestions
https://github.com/rubygems/rubygems/commit/760b7d834f
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/6fbda98eb3
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/a6375920bf
|
|
|
|
|
|
| |
For consistency with the other specs.
https://github.com/rubygems/rubygems/commit/44b93aec4c
|
|
|
|
|
|
|
|
|
| |
JRUBY_VERSION
* RUBY_ENGINE and RUBY_ENGINE_VERSION are defined on every modern Ruby.
* There is no such constant as TRUFFLERUBY_VERSION or RBX_VERSION.
https://github.com/rubygems/rubygems/commit/431d0aefdd
|
|
|
|
|
|
|
| |
* If settings constants fail, show that exception instead of getting
another one due to variables being unset and hiding the real cause.
https://github.com/rubygems/rubygems/commit/f38cd67874
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Sometimes it happens to me that my local tests start failing because I
pull some file removals or renames into my local copy, and those are
still present on my last copy of pkg/. In those cases, the test about
`rake package` will fail with something like the following:
````
Failure:
TestRakePackage#test_builds_ok [/home/deivid/Code/rubygems/test/rubygems/test_rake_package.rb:13]:
Expected `rake package` to work, but got errors:
```
cd pkg/rubygems-update-3.1.0.pre1
WARNING: See http://guides.rubygems.org/specification-reference/ for help
rake aborted!
Gem::InvalidSpecificationException: ["test/rubygems/test_rake_package.rb"] are not files
Tasks: TOP => package => gem => pkg/rubygems-update-3.1.0.pre1.gem
(See full trace by running task with --trace)
```
If you have added or removed files, make sure you run `rake update_manifest` to update the `Manifest.txt` accordingly.
Expected: true
Actual: false
````
So, make sure, package is always built from scratch.
https://github.com/rubygems/rubygems/commit/4e2cc9eb26
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/5c3158d975
|
| |
|
| |
|