| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
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
|
| |
|
| |
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/ca8afc01a3
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/be962ca0c4
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/be962ca0c4
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/006cdd4084
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/1ea674d8f7
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/70c5c17a5f
|
|
|
|
|
|
|
|
|
|
|
|
| |
BasicSpecification.
This was never the right place. The method got there just by evolution,
not by design. Move it within default methods, where it suits better.
Since this method is presumably used just internally, it should be safe
to deprecate it and remove later.
https://github.com/rubygems/rubygems/commit/0c0dd9458a
|
|
|
|
|
|
| |
supported nor functional.
https://github.com/rubygems/rubygems/commit/cadb66037d
|
|
|
|
|
|
|
|
|
|
| |
Separate #add_runtime_dependency and #add_development_dependency
availability condition from #specification_version availability,
which is not related to directly.
Also check if the former method is available, instead of comparing
the version.
https://github.com/rubygems/rubygems/commit/5cccc2b836
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/79b62c233a
|
|
|
|
|
|
| |
methods
https://github.com/rubygems/rubygems/commit/2a96494d91
|
|
|
|
|
|
| |
S3URISigner class
https://github.com/rubygems/rubygems/commit/c30d21ec7a
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/fb62d3043c
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/a76f25dff0
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/f289788ca5
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/2c9cfcb666
|
|
|
|
|
|
| |
Add some basic specs for the package attr_reader.
https://github.com/rubygems/rubygems/commit/68af2a0ee3
|
|
|
|
|
|
| |
in Rubygems 3
https://github.com/rubygems/rubygems/commit/6d5f743a89
|
|
|
|
|
|
|
| |
Because we can't control 3rd party gems using deprecated rubygems
behavior, and thus outputting warnings to the screen.
https://github.com/rubygems/rubygems/commit/6912ebf20a
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/1b9ab33083
|
|
|
|
|
|
| |
available
https://github.com/rubygems/rubygems/commit/471239f1fa
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/955174658f
|
|
|
|
|
|
|
| |
`Dir.pwd` may differ from the source path. Test directories and
files should be resolved from test file paths.
https://github.com/rubygems/rubygems/commit/e18e7c81b4
|
| |
|
|
|
|
| |
I picked the commit from 3c469e0da538428a0ddd94f99aa73c32da22e8ba
|
|
|
|
|
|
| |
for Solaris.
https://rubyci.org/logs/rubyci.s3.amazonaws.com/unstable10s/ruby-master/log/20190528T191908Z.fail.html.gz
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The old certificate files (for example, test/rubygems/ca_cert.pem) were
signed by SHA1. This message digest is considered too weak and rejected
by OpenSSL 1.1.1 or later. Because of this, the test suite does not
pass on Debian 10.
https://rubyci.org/logs/rubyci.s3.amazonaws.com/debian/ruby-master/log/20190527T123003Z.fail.html.gz#test%2Frubygems
This change regenerates the files.
A shell script for the regeneration (util/create_certs.sh) is also
added.
|
|
|
|
|
|
| |
for Solaris.
https://rubyci.org/logs/rubyci.s3.amazonaws.com/unstable10s/ruby-master/log/20190525T211908Z.fail.html.gz
|
|
|
|
| |
merged https://github.com/rubygems/rubygems/pull/2765
|
|
|
|
| |
Closes: https://github.com/ruby/ruby/pull/2154
|
|
|
|
|
|
|
| |
The current master branch is
https://github.com/rubygems/rubygems/commit/97b264f0fa248c864b6ee9a23d3ff1cdd217dddb
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67415 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
|
|
|
|
| |
to make CI stable. See the PR for details.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67293 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
|
|
|
|
| |
Import rubygems/rubygems#2678
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67205 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
|
|
|
|
|
| |
When `GEM_HOME` was shared with CRuby and JRuby. RubyGems try to
handle both platforms. It should be ignored the different platform.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67190 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
|
|
| |
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67171 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
|
|
|
|
|
| |
It fixed the multiple vulnerabilities.
https://blog.rubygems.org/2019/03/05/security-advisories-2019-03.html
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67168 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|