| Age | Commit message (Collapse) | Author |
|
It's only related to the `bundle cache` command, so it should be checked
there.
https://github.com/rubygems/rubygems/commit/cf749f8ffa
|
|
https://github.com/rubygems/rubygems/commit/285ccbc07e
|
|
https://github.com/rubygems/rubygems/commit/d86fb2c316
|
|
https://github.com/rubygems/rubygems/commit/04e6a5ae31
|
|
These days all these errors are raised as `Gem::Security::Exception` so
there's no need to do any matching on the exception message.
https://github.com/rubygems/rubygems/commit/bd3403da57
|
|
The `security_policies` method already requires it.
https://github.com/rubygems/rubygems/commit/d19b088f2f
|
|
It's checked before calling the method already.
https://github.com/rubygems/rubygems/commit/4eb00e9586
|
|
https://github.com/rubygems/rubygems/commit/a00c79a4da
|
|
Treats ::chmod_R and ::chown.
https://github.com/ruby/fileutils/commit/df4ac84bef
|
|
Treats ::chmod; adds Pathname usage to ::install.
https://github.com/ruby/fileutils/commit/9db4cb129c
|
|
`timeout 0.3.0` broke our test suite because we have some
tests that stubs `Process.clock_gettime` making it return
a value in the past, causing `Timeout` to trigger almost immediately.
I beleive it wasn't a problem before because it was relying on `Process.sleep`.
https://github.com/ruby/timeout/commit/e5911a303e
|
|
https://github.com/ruby/fileutils/commit/b9d5a79e38
|
|
Adds a note about file tree examples.
https://github.com/ruby/fileutils/commit/65ac65067a
|
|
https://github.com/rubygems/rubygems/commit/81ccb3ab89
|
|
#message (https://github.com/ruby/error_highlight/pull/24)
See https://bugs.ruby-lang.org/issues/18564.
Ref: https://github.com/ruby/did_you_mean/pull/177
https://github.com/ruby/error_highlight/commit/671b7c61b2
|
|
|
|
https://github.com/ruby/rdoc/commit/6d7bf24bb8
|
|
Currently only literal `0` and `1` are accepted as `read`/`write`
flags.
This patch allows other boolean arguments, C macros (`FALSE`/`TRUE`),
Ruby `VALUE`s (`Qfalse`/`Qtrue`), and C99 `bool`s (`false`/`true`), as
well.
https://github.com/ruby/rdoc/commit/169dc02e3c
|
|
(https://github.com/ruby/fileutils/pull/78)
Treats:
::rm
::rm_f
::rm_r
::rm_rf
::remove_entry_secure
https://github.com/ruby/fileutils/commit/ce2a438d75
|
|
* Add missing slash.
https://github.com/ruby/open-uri/commit/40023e63da
|
|
It was being explicitly required from `Gem::Specification` but also a
strange autoload was set for it at `Gem::Version`. The autoload was non
standard because it should've been done in the `Gem` module, not in
`Gem::Specification`, since that's where the constant is expected to get
defined. Doing this might get deprecated in the future, and it was not
being effective anyways due to the explicit require.
Unify everything with an `autoload` at the right place.
https://github.com/rubygems/rubygems/commit/174ea3e24c
|
|
https://github.com/ruby/cgi/commit/93326fb622
|
|
So that an exception raises by non-existent command, not via shell.
https://github.com/ruby/rdoc/commit/fd94dce69d
|
|
https://github.com/ruby/rdoc/commit/6b1a011243
|
|
https://github.com/ruby/rdoc/commit/83051403d6
|
|
`IO.popen` does that job.
https://github.com/ruby/rdoc/commit/3bbbc5ac84
|
|
https://github.com/ruby/rdoc/commit/47a1aef447
|
|
https://github.com/rubygems/rubygems/commit/a20bac7924
|
|
`Bundle.defintion`.
Prior to this commit, `bundle add GEM_NAME` updated the lockfile,
but `bundle remove GEM_NAME` left GEM_NAME in the lockfile.
By invalidating the cached `Bundle.definition`, the existing code
handles that without a problem.
https://github.com/rubygems/rubygems/commit/aa0794d6a9
|
|
The installer is actually rewriting the spec's full gem path to be the
one of the newly installed gem, however the accessor was not properly
working for `StubSpecification` instances, and default gems are always
of this type, because they are always present locally.
Fix the accessor to properly update the underlying full specification.
https://github.com/rubygems/rubygems/commit/efa41babfa
|
|
This change was never covered with a spec, and we have recently covered
the case of partially deleted gems with specs and it works fine
(installation is "auto-healed").
https://github.com/rubygems/rubygems/commit/6e66ee4235
|
|
`YAML::PrivateType`
This issue was not detected because when all traces of old YAML parser
and emitter `Syck` were removed, this null-type.gemspec.rz marshalled
gemspec was updated to no longer load `YAML::Syck::PrivateType` but load
`Psych::PrivateType` instead.
However, realworld old marshalled gemspecs still use the
`YAML::PrivateType` constant, so this commit replaces the gemspec to be
the real pry-0.4.7 marshalled gemspec, so that it catches this issue.
https://github.com/rubygems/rubygems/commit/51b330b8d2
|
|
This old bug used to affect the `rubyforge_project` field in serialized
gemspecs. However, this field has been removed and it's no longer
present in marshaled loaded gemspecs.
So, while the constant is still present in these marshalled gemspecs and
we still need to make sure it exists, we no longer need to clean it up
from the loaded data.
https://github.com/rubygems/rubygems/commit/09df18e522
|
|
Generally this warning is skipped for gemspec development dependencies.
I think because it's common to override them in the Gemfile to change
the source, for example.
But the order of conditions was not correct and the warning was still
being printed in one case.
https://github.com/rubygems/rubygems/commit/da9d1d6a3f
|
|
This alternative really uses only the Gemfile, and can never end up
being absurd, because it will never be suggested when there's no
lockfile, and it suggests deleting the lockfile.
https://github.com/rubygems/rubygems/commit/5d154dd50e
|
|
Treats:
::copy_entry
::copy_file
::copy_stream
::mv
https://github.com/ruby/fileutils/commit/d6d7e5330d
|
|
https://github.com/rubygems/rubygems/commit/2d99277328
|
|
If BUNDLE_PATH is configured to a symlinked path, installing gems with
symlinks would crash with an error like this:
```
Gem::Package::SymlinkError: installing symlink 'man/man0/README.markdown' pointing to parent path /usr/home/stevewi/srv/mail/lib/tools/.vendor/ruby/3.1.0/gems/binman-5.1.0/README.markdown of /srv/mail/lib/tools/.vendor/ruby/3.1.0/gems/binman-5.1.0 is not allowed
```
This commit fixes the problem by changing the bundle path to be the
realpath of the configured value, right after we're sure the path has
been created.
https://github.com/rubygems/rubygems/commit/3cd3dd142a
|
|
https://github.com/rubygems/rubygems/commit/f5dd5204ca
|
|
Apparently old versions of MacOS would set `GEM_HOME` to a `/System`
folder, and trying to create a file there raises `Errno::EROFS`.
We ignore the error. Any permission issues should be better handled
further down the line.
https://github.com/rubygems/rubygems/commit/ef90c071d0
|
|
This kind of error can happen when setting `GEM_HOME` to a path
under MacOS System Integrity Protection.
We ignore the error. Any permission issues should be better handled
further down the line.
https://github.com/rubygems/rubygems/commit/174cb66863
|
|
https://github.com/rubygems/rubygems/commit/a7f81cc7ee
|
|
It's already done before.
https://github.com/rubygems/rubygems/commit/49d28cfde5
|
|
configured
https://github.com/rubygems/rubygems/commit/9f3b21192d
|
|
removed
Instead of guessing on the culprit.
We actually have a helper, `Bundler.rm_rf`, with exactly the behavior
that we want:
* Allow the passed folder to not exist.
* No exception swallowing other than that.
https://github.com/rubygems/rubygems/commit/5fa3e6f04a
|
|
(https://github.com/ruby/fileutils/pull/76)
https://github.com/ruby/fileutils/commit/27a3c376c7
|
|
https://github.com/ruby/timeout/commit/f3a31abdfb
|
|
https://github.com/ruby/timeout/commit/5153ae9cad
|
|
https://github.com/ruby/timeout/commit/01c44b591f
|
|
https://github.com/ruby/timeout/commit/9a9b03b44c
|