rubygems-update 2.7.6 → 2.7.7

data/bundler/man/bundle-inject.ronn

@@ -8,9 +8,9 @@ bundle-inject(1) -- Add named gem(s) with version requirements to Gemfile
 ## DESCRIPTION
 
 Adds the named gem(s) with their version requirements to the resolved
-`Gemfile(5)`.
+[`Gemfile(5)`][Gemfile(5)].
 
-This command will add the gem to both your `Gemfile(5)` and Gemfile.lock if it
+This command will add the gem to both your [`Gemfile(5)`][Gemfile(5)] and Gemfile.lock if it
 isn't listed yet.
 
 Example:
@@ -19,4 +19,4 @@ Example:
     bundle inject 'rack' '> 0'
 
 This will inject the 'rack' gem with a version greater than 0 in your
-`Gemfile(5)` and Gemfile.lock
+[`Gemfile(5)`][Gemfile(5)] and Gemfile.lock

data/bundler/man/bundle-install.ronn

@@ -361,7 +361,7 @@ which other gems in the Gemfile(5) still depend on, run
 `Summary`: In general, after making a change to the Gemfile(5) , you
 should first try to run `bundle install`, which will guarantee that no
 other gem in the Gemfile(5) is impacted by the change. If that
-does not work, run [bundle update(1)][bundle-update].
+does not work, run [bundle update(1)][bundle-update(1)].
 
 ## SEE ALSO
 

data/bundler/man/bundle-lock.ronn

@@ -91,4 +91,4 @@ For a full explanation of gem platforms, see `gem help platform`.
 
 ## PATCH LEVEL OPTIONS
 
-See [bundle update(1)][bundle-update] for details.
+See [bundle update(1)][bundle-update(1)] for details.

data/bundler/man/bundle-outdated.ronn

@@ -69,7 +69,7 @@ are up to date, Bundler will exit with a status of 0. Otherwise, it will exit 1.
 
 ## PATCH LEVEL OPTIONS
 
-See [bundle update(1)][bundle-update] for details.
+See [bundle update(1)][bundle-update(1)] for details.
 
 One difference between the patch level options in `bundle update` and here is the `--strict` option.
 `--strict` was already an option on outdated before the patch level options were added. `--strict`

data/bundler/man/bundle-package.ronn

@@ -27,8 +27,8 @@ in your local bundler configuration.
 
 ## REMOTE FETCHING
 
-By default, if you run [bundle install(1)][bundle-install] after running
-[bundle package(1)][bundle-package], bundler will still connect to `rubygems.org`
+By default, if you run `bundle install(1)`][bundle-install(1)] after running
+[bundle package(1)][bundle-package(1)], bundler will still connect to `rubygems.org`
 to check whether a platform-specific gem exists for any of the gems
 in `vendor/cache`.
 
@@ -66,7 +66,7 @@ machine and check in the gems. For instance, you can run
 staging process, and check in the `vendor/cache` before
 deploying to production.
 
-By default, [bundle package(1)][bundle-package] fetches and also
+By default, [bundle package(1)][bundle-package(1)] fetches and also
 installs the gems to the default location. To package the
 dependencies to `vendor/cache` without installing them to the
 local install location, you can run `bundle package --no-install`.

data/bundler/man/bundle-show.ronn

@@ -9,7 +9,7 @@ bundle-show(1) -- Shows all the gems in your bundle, or the path to a gem
 ## DESCRIPTION
 
 Without the [GEM] option, `show` will print a list of the names and versions of
-all gems that are required by your `Gemfile(5)`.
+all gems that are required by your [`Gemfile(5)`][Gemfile(5)].
 
 Calling show with [GEM] will list the exact location of that gem on your
 machine.
@@ -17,4 +17,4 @@ machine.
 ## OPTIONS
 
 * `--paths`:
-  List the paths of all gems that are required by your `Gemfile(5)`.
+  List the paths of all gems that are required by your [`Gemfile(5)`][Gemfile(5)].

data/bundler/man/bundle-update.ronn

@@ -20,7 +20,7 @@ bundle-update(1) -- Update your gems to the latest available versions
 
 Update the gems specified (all gems, if none are specified), ignoring
 the previously installed gems specified in the `Gemfile.lock`. In
-general, you should use [bundle install(1)][bundle-install] to install the same exact
+general, you should use [bundle install(1)][bundle-install(1)] to install the same exact
 gems and versions across machines.
 
 You would use `bundle update` to explicitly update the version of a
@@ -91,7 +91,7 @@ Consider the following Gemfile(5):
     gem "rails", "3.0.0.rc"
     gem "nokogiri"
 
-When you run [bundle install(1)][bundle-install] the first time, bundler will resolve
+When you run [bundle install(1)][bundle-install(1)] the first time, bundler will resolve
 all of the dependencies, all the way down, and install what you need:
 
     Fetching gem metadata from https://rubygems.org/.........
@@ -128,11 +128,11 @@ all of the dependencies, all the way down, and install what you need:
 
 As you can see, even though you have two gems in the Gemfile(5), your application
 needs 26 different gems in order to run. Bundler remembers the exact versions
-it installed in `Gemfile.lock`. The next time you run [bundle install(1)][bundle-install], bundler skips
+it installed in `Gemfile.lock`. The next time you run [bundle install(1)][bundle-install(1)], bundler skips
 the dependency resolution and installs the same gems as it installed last time.
 
 After checking in the `Gemfile.lock` into version control and cloning it on another
-machine, running [bundle install(1)][bundle-install] will _still_ install the gems that you installed
+machine, running [bundle install(1)][bundle-install(1)] will _still_ install the gems that you installed
 last time. You don't need to worry that a new release of `erubis` or `mail` changes
 the gems you use.
 
@@ -192,12 +192,12 @@ update all dependencies of that gem, including those that are also dependencies
 of another gem.
 
 To prevent updating shared dependencies, prior to version 1.14 the only option
-was the `CONSERVATIVE UPDATING` behavior in [bundle install(1)][bundle-install]:
+was the `CONSERVATIVE UPDATING` behavior in [bundle install(1)][bundle-install(1)]:
 
 In this scenario, updating the `thin` version manually in the Gemfile(5),
-and then running [bundle install(1)][bundle-install] will only update `daemons` and `eventmachine`,
+and then running [bundle install(1)][bundle-install(1)] will only update `daemons` and `eventmachine`,
 but not `rack`. For more information, see the `CONSERVATIVE UPDATING` section
-of [bundle install(1)][bundle-install].
+of [bundle install(1)][bundle-install(1)].
 
 Starting with 1.14, specifying the `--conservative` option will also prevent shared
 dependencies from being updated.
@@ -335,7 +335,7 @@ use the following workflow:
 
     $ git add Gemfile.lock
 
-* If [bundle install(1)][bundle-install] reports a conflict, manually update the specific
+* If [bundle install(1)][bundle-install(1)] reports a conflict, manually update the specific
   gems that you changed in the Gemfile(5)
 
     $ bundle update rails thin

data/bundler/man/bundle-viz.ronn

@@ -14,7 +14,7 @@ bundle-viz(1) -- Generates a visual dependency graph for your Gemfile
 `viz` generates a PNG file of the current `Gemfile(5)` as a dependency graph.
 `viz` requires the ruby-graphviz gem (and its dependencies).
 
-The associated gems must also be installed via `bundle install(1)`.
+The associated gems must also be installed via [`bundle install(1)`][bundle-install(1)].
 
 ## OPTIONS
 

data/bundler/man/bundle.ronn

@@ -26,73 +26,73 @@ started, and Gemfile(5) for more information on the `Gemfile` format.
 
 ## BUNDLE COMMANDS
 
-We divide `bundle` subcommands into primary commands and utilities.
+We divide `bundle` subcommands into primary commands and utilities:
 
 ## PRIMARY COMMANDS
 
-* [`bundle install(1)`][bundle-install]:
+* [`bundle install(1)`][bundle-install(1)]:
   Install the gems specified by the `Gemfile` or `Gemfile.lock`
 
-* [`bundle update(1)`][bundle-update]:
+* [`bundle update(1)`][bundle-update(1)]:
   Update dependencies to their latest versions
 
-* [`bundle package(1)`][bundle-package]:
+* [`bundle package(1)`][bundle-package(1)]:
   Package the .gem files required by your application into the
   `vendor/cache` directory
 
-* [`bundle exec(1)`][bundle-exec]:
-  Execute a script in the context of the current bundle
+* [`bundle exec(1)`][bundle-exec(1)]:
+  Execute a script in the current bundle
 
-* [`bundle config(1)`][bundle-config]:
-  Specify and read configuration options for bundler
+* [`bundle config(1)`][bundle-config(1)]:
+  Specify and read configuration options for Bundler
 
 * `bundle help(1)`:
   Display detailed help for each subcommand
 
 ## UTILITIES
 
-* `bundle add(1)`:
+* [`bundle add(1)`][bundle-add(1)]:
   Add the named gem to the Gemfile and run `bundle install`
 
-* `bundle binstubs(1)`:
+* [`bundle binstubs(1)`][bundle-binstubs(1)]:
   Generate binstubs for executables in a gem
 
-* `bundle check(1)`:
+* [`bundle check(1)`][bundle-check(1)]:
   Determine whether the requirements for your application are installed
-  and available to bundler
+  and available to Bundler
 
-* `bundle show(1)`:
+* [`bundle show(1)`][bundle-show(1)]:
   Show the source location of a particular gem in the bundle
 
-* [`bundle outdated(1)`][bundle-outdated]:
+* [`bundle outdated(1)`][bundle-outdated(1)]:
   Show all of the outdated gems in the current bundle
 
 * `bundle console(1)`:
-  Start an IRB session in the context of the current bundle
+  Start an IRB session in the current bundle
 
-* `bundle open(1)`:
+* [`bundle open(1)`][bundle-open(1)]:
   Open an installed gem in the editor
 
 * [`bundle lock(1)`][bundle-lock]:
   Generate a lockfile for your dependencies
 
-* `bundle viz(1)`:
+* [`bundle viz(1)`][bundle-viz(1)]:
   Generate a visual representation of your dependencies
 
-* `bundle init(1)`:
+* [`bundle init(1)`][bundle-init(1)]:
   Generate a simple `Gemfile`, placed in the current directory
 
-* [`bundle gem(1)`][bundle-gem]:
-  Create a simple gem, suitable for development with bundler
+* [`bundle gem(1)`][bundle-gem(1)]:
+  Create a simple gem, suitable for development with Bundler
 
-* [`bundle platform(1)`][bundle-platform]:
+* [`bundle platform(1)`][bundle-platform(1)]:
   Display platform compatibility information
 
-* `bundle clean(1)`:
-  Clean up unused gems in your bundler directory
+* [`bundle clean(1)`][bundle-clean(1)]:
+  Clean up unused gems in your Bundler directory
 
 * `bundle doctor(1)`:
-  Display warnings about common potential problems
+  Display warnings about common problems
 
 ## PLUGINS
 
@@ -102,7 +102,7 @@ and execute it, passing down any extra arguments to it.
 
 ## OBSOLETE
 
-These commands are obsolete and should no longer be used
+These commands are obsolete and should no longer be used:
 
 * `bundle cache(1)`
 * `bundle show(1)`

data/bundler/man/gemfile.5.ronn

@@ -35,7 +35,7 @@ this warning, by using the [`:source` option](#SOURCE) or a
 
 ### CREDENTIALS
 
-Some gem sources require a username and password. Use [bundle config(1)][bundle-config] to set
+Some gem sources require a username and password. Use [bundle config(1)][bundle-config(1)] to set
 the username and password for any of the sources that need it. The command must
 be run once on each computer that will install the Gemfile, but this keeps the
 credentials from being stored in plain text in version control.
@@ -228,7 +228,7 @@ As with groups, you can specify one or more platforms:
     gem "ruby-debug", :platforms => :mri_18
     gem "nokogiri",   :platforms => [:mri_18, :jruby]
 
-All operations involving groups (`bundle install`, `Bundler.setup`,
+All operations involving groups ([`bundle install`][bundle-install(1)], `Bundler.setup`,
 `Bundler.require`) behave exactly the same as if any groups not
 matching the current platform were explicitly excluded.
 
@@ -465,7 +465,7 @@ software is installed or some other conditions are met.
 
 ## GEMSPEC
 
-The [.gemspec](http://guides.rubygems.org/specification-reference/) file is where
+The [`.gemspec`](http://guides.rubygems.org/specification-reference/) file is where
  you provide metadata about your gem to Rubygems. Some required Gemspec
  attributes include the name, description, and homepage of your gem. This is
  also where you specify the dependencies your gem needs to run.

data/lib/rubygems.rb

@@ -10,7 +10,7 @@ require 'rbconfig'
 require 'thread'
 
 module Gem
-  VERSION = "2.7.6"
+  VERSION = "2.7.7"
 end
 
 # Must be first since it unloads the prelude from 1.9.2
@@ -604,7 +604,7 @@ An Array (#{env.inspect}) was passed in from #{caller[3]}
 
   private_class_method :find_home
 
-  # FIXME deprecate these in 3.0
+  # TODO:  remove in RubyGems 4.0
 
   ##
   # Zlib::GzipReader wrapper that unzips +data+.
@@ -613,6 +613,11 @@ An Array (#{env.inspect}) was passed in from #{caller[3]}
     Gem::Util.gunzip data
   end
 
+  class << self
+    extend Gem::Deprecate
+    deprecate :gunzip, "Gem::Util.gunzip", 2018, 12
+  end
+
   ##
   # Zlib::GzipWriter wrapper that zips +data+.
 
@@ -620,6 +625,11 @@ An Array (#{env.inspect}) was passed in from #{caller[3]}
     Gem::Util.gzip data
   end
 
+  class << self
+    extend Gem::Deprecate
+    deprecate :gzip, "Gem::Util.gzip", 2018, 12
+  end
+
   ##
   # A Zlib::Inflate#inflate wrapper
 
@@ -627,6 +637,11 @@ An Array (#{env.inspect}) was passed in from #{caller[3]}
     Gem::Util.inflate data
   end
 
+  class << self
+    extend Gem::Deprecate
+    deprecate :inflate, "Gem::Util.inflate", 2018, 12
+  end
+
   ##
   # Top level install helper method. Allows you to install gems interactively:
   #
@@ -1225,9 +1240,12 @@ An Array (#{env.inspect}) was passed in from #{caller[3]}
 
   class << self
     ##
-    # TODO remove with RubyGems 3.0
+    # TODO remove with RubyGems 4.0
 
     alias detect_gemdeps use_gemdeps # :nodoc:
+
+    extend Gem::Deprecate
+    deprecate :detect_gemdeps, "Gem.use_gemdeps", 2018, 12
   end
 
   # FIX: Almost everywhere else we use the `def self.` way of defining class

data/lib/rubygems/bundler_version_finder.rb

@@ -1,3 +1,7 @@
+# frozen_string_literal: true
+
+require "rubygems/util"
+
 module Gem::BundlerVersionFinder
   @without_filtering = false
 
@@ -102,7 +106,7 @@ To install the missing version, run `gem install bundler:#{vr.first}`
     lockfile = case gemfile
     when "gems.rb" then "gems.locked"
     else "#{gemfile}.lock"
-    end.untaint
+    end.dup.untaint
 
     return unless File.file?(lockfile)
 

data/lib/rubygems/commands/push_command.rb

@@ -13,7 +13,7 @@ class Gem::Commands::PushCommand < Gem::Command
 The push command uploads a gem to the push server (the default is
 https://rubygems.org) and adds it to the index.
 
-The gem can be removed from the index (but only the index) using the yank
+The gem can be removed from the index and deleted from the server using the yank
 command.  For further discussion see the help for the yank command.
     EOF
   end

data/lib/rubygems/commands/setup_command.rb

@@ -351,7 +351,7 @@ By default, this RubyGems will install gem as:
     return unless Gem::USE_BUNDLER_FOR_GEMDEPS
 
     specs_dir = Gem::Specification.default_specifications_dir
-    File.join(options[:destdir], specs_dir) unless Gem.win_platform?
+    specs_dir = File.join(options[:destdir], specs_dir) unless Gem.win_platform?
     mkdir_p specs_dir
 
     # Workaround for non-git environment.
@@ -385,8 +385,8 @@ By default, this RubyGems will install gem as:
         each {|default_gem| rm_r File.join(bundler_spec.gems_dir, default_gem) }
     end
 
-    bundler_bin_dir = File.join(Gem.default_dir, 'gems', bundler_spec.full_name, bundler_spec.bindir)
-    File.join(options[:destdir], bundler_bin_dir) unless Gem.win_platform?
+    bundler_bin_dir = bundler_spec.bin_dir
+    bundler_bin_dir = File.join(options[:destdir], bundler_bin_dir) unless Gem.win_platform?
     mkdir_p bundler_bin_dir
     bundler_spec.executables.each do |e|
       cp File.join("bundler", bundler_spec.bindir, e), File.join(bundler_bin_dir, e)

data/lib/rubygems/commands/unpack_command.rb

@@ -183,7 +183,7 @@ command help for an example.
         when 'metadata' then
           metadata = entry.read
         when 'metadata.gz' then
-          metadata = Gem.gunzip entry.read
+          metadata = Gem::Util.gunzip entry.read
         end
       end
     end

data/lib/rubygems/dependency.rb

@@ -2,6 +2,7 @@
 ##
 # The Dependency class holds a Gem name and a Gem::Requirement.
 
+require "rubygems/bundler_version_finder"
 require "rubygems/requirement"
 
 class Gem::Dependency

data/lib/rubygems/dependency_installer.rb

@@ -113,7 +113,7 @@ class Gem::DependencyInstaller
 
   ##
   #--
-  # TODO remove, no longer used
+  # TODO remove at RubyGems 4, no longer used
 
   def add_found_dependencies to_do, dependency_list # :nodoc:
     seen = {}
@@ -163,6 +163,7 @@ class Gem::DependencyInstaller
 
     dependency_list.remove_specs_unsatisfied_by dependencies
   end
+  deprecate :add_found_dependencies, :none, 2018, 12
 
   ##
   # Creates an AvailableSet to install from based on +dep_or_name+ and
@@ -321,7 +322,7 @@ class Gem::DependencyInstaller
   # Gathers all dependencies necessary for the installation from local and
   # remote sources unless the ignore_dependencies was given.
   #--
-  # TODO remove at RubyGems 3
+  # TODO remove at RubyGems 4
 
   def gather_dependencies # :nodoc:
     specs = @available.all_specs
@@ -354,6 +355,7 @@ class Gem::DependencyInstaller
 
     @gems_to_install = dependency_list.dependency_order.reverse
   end
+  deprecate :gather_dependencies, :none, 2018, 12
 
   def in_background what # :nodoc:
     fork_happened = false

data/lib/rubygems/exceptions.rb

@@ -4,6 +4,8 @@
 # Each exception needs a brief description and the scenarios where it is
 # likely to be raised
 
+require 'rubygems/deprecate'
+
 ##
 # Base exception class for RubyGems.  All exception raised by RubyGems are a
 # subclass of this one.
@@ -11,10 +13,12 @@ class Gem::Exception < RuntimeError
 
   ##
   #--
-  # TODO: remove in RubyGems 3, nobody sets this
+  # TODO: remove in RubyGems 4, nobody sets this
 
   attr_accessor :source_exception # :nodoc:
 
+  extend Gem::Deprecate
+  deprecate :source_exception, :none, 2018, 12
 end
 
 class Gem::CommandLineError < Gem::Exception; end