Age | Commit message (Collapse) | Author |
|
|
|
It has been deprecated for 3 years, and has been broken for that entire
period. (It required itself, instead of `rubygems/source/local`.)
Closes #3158.
https://github.com/rubygems/rubygems/commit/2f01a272d0
|
|
Gem::DependencyInstaller#find_gems_with_sources"
This reverts commit 04c79d3eb9d9803d9fae78575b125b325b97206e.
Final removal is postponed until next year until we find a better way to
manage deprecations.
https://github.com/rubygems/rubygems/commit/3e1cf918a5
|
|
That line means that the class supports both `URI`'s and `String`'s
being passed to `initialize`. I don't see how that's related to 1.8.
https://github.com/rubygems/rubygems/commit/77aeff4515
|
|
https://github.com/rubygems/rubygems/commit/84c89275b8
|
|
https://github.com/rubygems/rubygems/commit/6fa0b1b679
|
|
So it matches the style used by bundler.
https://github.com/rubygems/rubygems/commit/ab0580fd65
|
|
Notes:
Merged-By: hsbt <hsbt@ruby-lang.org>
|
|
|
|
This reverts commit d767da428c28b7b9fec56b383bb32f6f76c6ad26.
It fails with spec/ruby/core/kernel/require_spec.rb:5
|
|
The original commit was https://github.com/rubygems/rubygems/pull/3119
|
|
If `require "a"` is run when two folders have been specified in the -I
option including a "a.rb" file and a "a.so" file respectively, the ruby
spec says that the ".rb" file should always be preferred. However, the
logic we added in https://github.com/rubygems/rubygems/commit/6b81076d9
to make the -I option always beat default gems does not respect this
spec, creating a difference from the original ruby-core's require.
[the ruby spec says]: https://github.com/ruby/spec/blob/d80a6e2b221d4f17a8cadcac75ef950c59cba901/core/kernel/shared/require.rb#L234-L246
https://github.com/rubygems/rubygems/commit/b3944384f4
|
|
This condition is too restrictive in my opinion. If a user has a pre
version of rubygems installed, she should be fully responsible for it,
and we shouldn't restrict any functionality.
Also, why is a new prerelease disallowed but an old prelease allowed, or
why is 2.0.0.rc2 explictly whitelisted? I believe this kind of
exceptions are one more reason to actually permit this.
https://github.com/rubygems/rubygems/commit/7f77a77620
|
|
Just started to develop RubyGems 3.2.0.
|
|
|
|
https://github.com/rubygems/rubygems/commit/c6b4df5bfc
|
|
https://github.com/rubygems/rubygems/commit/8de4d0272e
|
|
|
|
|
|
|
|
|
|
|
|
Monitor can be owned at the beginning of this method.
|
|
This reverts commit d9978ce5d397866afae536db2aa708af3b7a4b2f.
Untaint was tentatively restored due to test failures. But now, the
failed tests have been removed, so we can revert the tentative fix.
|
|
Partly reverted 7d463e360b9c4718b17378eb52783116a01b884b
|
|
`File.symlink? safe_lp` can raise SecurityError and raising an
exception can leave RUBYGEMS_ACTIVATION_MONITOR locking. This
patch release it correctly.
|
|
|
|
|
|
This reverts commit 8b27c23b5d55bd707a89bb5d95d2bdba9e132c1a.
|
|
https://rubyci.org/logs/rubyci.s3.amazonaws.com/debian9/ruby-master/log/20191111T093005Z.fail.html.gz
|
|
* 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.
Notes:
Merged: https://github.com/ruby/ruby/pull/2666
|
|
I noticed that some files in rubygems were executable, and I could think
of no reason why they should be.
In general, I think ruby files should never have the executable bit set
unless they include a shebang, so I run the following command over the
whole repo:
```bash
find . -name '*.rb' -type f -executable -exec bash -c 'grep -L "^#!" $1 || chmod -x $1' _ {} \;
```
Notes:
Merged: https://github.com/ruby/ruby/pull/2662
|
|
https://github.com/rubygems/rubygems/commit/1de8f39ac4
|
|
https://github.com/rubygems/rubygems/commit/bde88f00a1
|
|
https://github.com/rubygems/rubygems/commit/05146bb2fd
|
|
The arity of this method has been -1 since the import, so the
option has been passed always, even if Zlib::GzipReader#initialize
does not take the option. Actually it takes the option since 1.9.
https://github.com/rubygems/rubygems/commit/2fcde0f4e0
|
|
|
|
And test the fix we're adding.
https://github.com/rubygems/rubygems/commit/6f86637b98
|
|
https://github.com/rubygems/rubygems/commit/cc255b774a
|
|
Co-authored-by: Yusuke Endoh <mame@ruby-lang.org>
https://github.com/rubygems/rubygems/commit/92892bbc3a
|
|
https://github.com/rubygems/rubygems/commit/506c5bce49
|
|
https://github.com/rubygems/rubygems/commit/b3b5c2d379
|
|
https://github.com/rubygems/rubygems/commit/8a7e27381c
|
|
https://github.com/rubygems/rubygems/commit/1d18b12a26
|
|
Previously it wouldn't play nice with the bundler version finder.
https://github.com/rubygems/rubygems/commit/d8bb81556d
|
|
https://github.com/rubygems/rubygems/commit/ba021fb4be
|
|
https://github.com/rubygems/rubygems/commit/8ac0647659
|
|
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
|