| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
https://github.com/rubygems/rubygems/commit/43819b6973
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/5f20647ec1
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/7fbef2f0e3
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/75f672ff0e
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When installing in parallel, bundler creates several `Gem::Installer`
instances that run in parallel. These installers access the `@@all` class
variable of `Gem::Specification` concurrently.
If a concurrent thread calls `Gem::Specification.reset` (resetting
`@all` to `nil`) while another thread is running
`Gem::Specification._all` or another method that expects `@@all` to be
loaded and not `nil`, that can result in `Enumerable` methods being
called on `nil`, resulting in crashes.
I fix it by protecting the other concurrent access to the `@all`
variable.
https://github.com/rubygems/rubygems/commit/58b343c530
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/e9e25731d8
|
| |
|
| |
|
|
|
|
|
|
|
| |
* One should not compare RUBY_ENGINE and Gem::Platform.
* Introduced in https://github.com/rubygems/rubygems/pull/2672
https://github.com/rubygems/rubygems/commit/0e62c3be91
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/1a72c8796f
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/c07b9cf4f1
|
|
|
|
|
|
| |
move rubyforge_project= to removed methods
https://github.com/rubygems/rubygems/commit/223f7fd470
|
|
|
|
|
|
| |
time.
https://github.com/rubygems/rubygems/commit/c44eb21648
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/965eee1741
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/024267fa60
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/6afd914fda
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/db5bb65baf
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/4fe5bb5bf3
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/b679ab27af
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/3a14635cf5
|
|
|
|
|
|
| |
version instead of a date
https://github.com/rubygems/rubygems/commit/bf95b1de78
|
|
|
|
|
|
| |
instead of a date
https://github.com/rubygems/rubygems/commit/f0e098a1b7
|
|
|
|
|
|
|
|
| |
It was migrated on ruby core repository too.
https://github.com/ruby/ruby/commit/e5db3da9d34f0a7595208863301c044b612adbed
https://github.com/rubygems/rubygems/commit/848bbe3c76
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/afa01a29a3
|
|
|
|
|
|
| |
These changes completely broke the test suite on ruby core repository.
https://github.com/rubygems/rubygems/commit/84b0bea3e1
|
|
|
|
|
|
|
|
|
| |
Our tests are now guaranteed to not work on older versions of minitest,
so I don't think we should swallow this activation error because it will
make it very clear for the user what the problem is if she has a
minitest version not satisfying the requirement.
https://github.com/rubygems/rubygems/commit/a291b65369
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/24213b97d8
|
|
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/f2cc5d7033
https://github.com/rubygems/rubygems/commit/ae5b4e2043
|
|
|
|
|
|
|
| |
English.rb is extracted to the default gems at
https://github.com/ruby/ruby/commit/2c5764ec223d976e0d0da1494596a1519104be3e
https://github.com/rubygems/rubygems/commit/532f488c0b
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Support XDG_CONFIG_HOME for gemrc.
* Support XDG_DATA_HOME for .gem
* Added test for XDG_DATA_HOME
* Do not reuse environmental variable.
* Unify .rdoc path to RDoc.home.
* Support XDG_DATA_HOME for .rdoc
* Ignore exists?
* Extracted config_home path
* Use XDG_CONFIG_HOME for default credential path
* Fixed inconsistency location.
* Fixed the broken tests.
* Support XDG_CONFIG_HOME for irbrc
* Introduce Gem.cache_home as XDG_CACHE_HOME
* Use Gem.cache_home instead of Gem.config_home for the credential file of RubyGems.
* Initialized the old configurations
* Fixed test failure related the configuration initialization
* restore XDG_DATA_HOME
* Fixed the broken examples of bundler with XDG_*
* Do not modify environmental variable on test file
* Use XDG_DATA_HOME insted of XDG_CACHE_HOME for credential file
* stub out Gem.data_home
* Move dir accessor to defaults.rb file
* Use XDG_DATA_HOME for signed gem features
* Use XDG_DATA_HOME for spec cache
* Do not rely on Gem.user_home
* Gem.user_home is always exists. Don't need to use FileUitls.mkdir_p
* Bump support version to RubyGems 3.2.0+
* Removed the needless fallback configuration
* Fixed the inconsistency methods that are find_config_file and config_file
* Use Gem.configuration.credentials_path instead of hard-coded path
* gem_path is always provided
* Removed the duplicated code of find_home
* Also removed the duplicated code of user_home
* use Gem::UNTAINT instead of untaint for surpressing the warnings
* Use File.directory
* Restore XDG_DATA_HOME
* Use File.write
|
| |
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
|
|
|
|
|
| |
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
|
| |
|
| |
|