summaryrefslogtreecommitdiff
path: root/lib/rubygems
AgeCommit message (Collapse)Author
2020-05-08[rubygems/rubygems] Rename version horizon deprecation methodsbronzdoc
https://github.com/rubygems/rubygems/commit/6afd914fda Notes: Merged: https://github.com/ruby/ruby/pull/3087
2020-05-08[rubygems/rubygems] Add next_rubygems_major_version methodbronzdoc
https://github.com/rubygems/rubygems/commit/db5bb65baf Notes: Merged: https://github.com/ruby/ruby/pull/3087
2020-05-08[rubygems/rubygems] Modify files to use new version horizon deprecationsbronzdoc
https://github.com/rubygems/rubygems/commit/4fe5bb5bf3 Notes: Merged: https://github.com/ruby/ruby/pull/3087
2020-05-08[rubygems/rubygems] Use the next major version as default for deprecationsbronzdoc
https://github.com/rubygems/rubygems/commit/b679ab27af Notes: Merged: https://github.com/ruby/ruby/pull/3087
2020-05-08[rubygems/rubygems] Remove deprecation methods by datebronzdoc
https://github.com/rubygems/rubygems/commit/3a14635cf5 Notes: Merged: https://github.com/ruby/ruby/pull/3087
2020-05-08[rubygems/rubygems] Make the deprecate_command method recieve a Rubygems ↵bronzdoc
version instead of a date https://github.com/rubygems/rubygems/commit/bf95b1de78 Notes: Merged: https://github.com/ruby/ruby/pull/3087
2020-05-08[rubygems/rubygems] Make the deprecate method recieve a Rubygems version ↵bronzdoc
instead of a date https://github.com/rubygems/rubygems/commit/f0e098a1b7 Notes: Merged: https://github.com/ruby/ruby/pull/3087
2020-05-08[rubygems/rubygems] Removed deprecated methods for Minitest5Hiroshi SHIBATA
It was migrated on ruby core repository too. https://github.com/ruby/ruby/commit/e5db3da9d34f0a7595208863301c044b612adbed https://github.com/rubygems/rubygems/commit/848bbe3c76 Notes: Merged: https://github.com/ruby/ruby/pull/3087
2020-05-08[rubygems/rubygems] Minitest::Test is works fine with the ruby core repositoryHiroshi SHIBATA
https://github.com/rubygems/rubygems/commit/afa01a29a3 Notes: Merged: https://github.com/ruby/ruby/pull/3087
2020-05-08[rubygems/rubygems] Revert https://github.com/rubygems/rubygems/pull/3445Hiroshi SHIBATA
These changes completely broke the test suite on ruby core repository. https://github.com/rubygems/rubygems/commit/84b0bea3e1 Notes: Merged: https://github.com/ruby/ruby/pull/3087
2020-05-08[rubygems/rubygems] Don't swallow gem activation exceptionDavid Rodríguez
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 Notes: Merged: https://github.com/ruby/ruby/pull/3087
2020-05-08[rubygems/rubygems] Remove minitest compatibility codeDavid Rodríguez
https://github.com/rubygems/rubygems/commit/24213b97d8 Notes: Merged: https://github.com/ruby/ruby/pull/3087
2020-05-08[rubygems/rubygems] [rubygems/rubygems] Require minitest `~> 5.13`David Rodríguez
https://github.com/rubygems/rubygems/commit/f2cc5d7033 https://github.com/rubygems/rubygems/commit/ae5b4e2043 Notes: Merged: https://github.com/ruby/ruby/pull/3087
2020-04-28[rubygems/rubygems] Removed the depdendency of English libraryHiroshi SHIBATA
English.rb is extracted to the default gems at https://github.com/ruby/ruby/commit/2c5764ec223d976e0d0da1494596a1519104be3e https://github.com/rubygems/rubygems/commit/532f488c0b
2020-04-25Clear cached XDG path namesNobuyoshi Nakada
2020-04-23Support XDG_* (#2174)Hiroshi SHIBATA
* 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 Notes: Merged-By: hsbt <hsbt@ruby-lang.org>
2020-03-30Migrate {assert,refute}_patch_exits for compatibility with Minitest5Hiroshi SHIBATA
2020-03-30[rubygems/rubygems] Remove deprecated + broken rubygems/source_local.Ellen Marie Dash
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
2020-03-30[rubygems/rubygems] Revert "Remove ↵David Rodríguez
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
2020-03-30[rubygems/rubygems] Remove misleading commentDavid Rodríguez
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
2020-03-30[rubygems/rubygems] Remove ruby 1.8 leftoversDavid Rodríguez
https://github.com/rubygems/rubygems/commit/84c89275b8
2020-03-30[rubygems/rubygems] Enable `Style/ExtraSpacing` and auto-correctDavid Rodríguez
https://github.com/rubygems/rubygems/commit/6fa0b1b679
2020-03-30[rubygems/rubygems] Enable Style/PercentLiteralDelimiters cop in rubygemsDavid Rodríguez
So it matches the style used by bundler. https://github.com/rubygems/rubygems/commit/ab0580fd65
2020-03-24Sync rubygems with current master (#2889)David Rodríguez
Notes: Merged-By: hsbt <hsbt@ruby-lang.org>
2020-03-08Specify explicit separator not to be affected by $;Nobuyoshi Nakada
2020-02-06Revert "[rubygems/rubygems] Fix require issue with file extension priority"Hiroshi SHIBATA
This reverts commit d767da428c28b7b9fec56b383bb32f6f76c6ad26. It fails with spec/ruby/core/kernel/require_spec.rb:5
2020-02-06Revert to remove the query command of rubygems.Hiroshi SHIBATA
The original commit was https://github.com/rubygems/rubygems/pull/3119
2020-02-06[rubygems/rubygems] Fix require issue with file extension priorityDavid Rodríguez
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
2020-02-06[rubygems/rubygems] Allow releasing with a rubygems pre versionDavid Rodríguez
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
2020-02-01Merge the current master branch of rubygems/rubygems.Hiroshi SHIBATA
Just started to develop RubyGems 3.2.0.
2019-12-20Merge RubyGems 3.1.2Hiroshi SHIBATA
2019-12-17[rubygems/rubygems] Move `require uri` to source_listmihaibuzgau
https://github.com/rubygems/rubygems/commit/c6b4df5bfc
2019-12-17[rubygems/rubygems] require `uri` in source.rbmihaibuzgau
https://github.com/rubygems/rubygems/commit/8de4d0272e
2019-12-13warn should be a global functionNobuyoshi Nakada
2019-12-13Prepare to release RubyGems 3.1.0 final version.Hiroshi SHIBATA
2019-11-13Fix a typoKazuhiro NISHIYAMA
2019-11-12Only enabled mon_owned condition with Ruby 2.5+Hiroshi SHIBATA
2019-11-12check more.Koichi Sasada
2019-11-12Monitor owner state check correctly.Koichi Sasada
Monitor can be owned at the beginning of this method.
2019-11-12Revert "Use untaint for File.symlink in kernel_require.rb"Yusuke Endoh
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.
2019-11-12Use untaint for File.symlink in kernel_require.rbHiroshi SHIBATA
Partly reverted 7d463e360b9c4718b17378eb52783116a01b884b
2019-11-12release RUBYGEMS_ACTIVATION_MONITOR correctly.Koichi Sasada
`File.symlink? safe_lp` can raise SecurityError and raising an exception can leave RUBYGEMS_ACTIVATION_MONITOR locking. This patch release it correctly.
2019-11-12more messagesKoichi Sasada
2019-11-12check monitor is owning for debugKoichi Sasada
2019-11-11Revert "Try to revert the test failure with Ruby CI"Hiroshi SHIBATA
This reverts commit 8b27c23b5d55bd707a89bb5d95d2bdba9e132c1a.
2019-11-11Try to revert the test failure with Ruby CIHiroshi SHIBATA
https://rubyci.org/logs/rubyci.s3.amazonaws.com/debian9/ruby-master/log/20191111T093005Z.fail.html.gz
2019-11-11Merge RubyGems 3.1.0.pre3Hiroshi SHIBATA
* 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
2019-11-09Remove unneeded exec bits from some filesDavid Rodríguez
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
2019-10-10[rubygems/rubygems] Optimize Gem::Package::TarReader#eachJean Boussier
https://github.com/rubygems/rubygems/commit/1de8f39ac4
2019-10-05[rubygems/rubygems] Use dependency.identity in available_specsbronzdoc
https://github.com/rubygems/rubygems/commit/bde88f00a1
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-21 06:59:13 +0000