bundler 1.16.2 → 1.16.3

data/man/bundle-exec.1.txt

@@ -14,8 +14,8 @@ DESCRIPTION
 
        Essentially, if you  would  normally  have  run	something  like  rspec
        spec/my_spec.rb,  and  you  want to use the gems specified in the [Gem-
-       file(5)][Gemfile(5)]  and  installed   via   [bundle   install(1)][bun-
-       dle-install(1)], you should run bundle exec rspec spec/my_spec.rb.
+       file(5)][Gemfile(5)]  and  installed   via   bundle   install(1)   bun-
+       dle-install.1.html, you should run bundle exec rspec spec/my_spec.rb.
 
        Note  that bundle exec does not require that an executable is available
        on your shell's $PATH.
@@ -27,10 +27,10 @@ OPTIONS
 	      of passing all file descriptors to the new process.
 
 BUNDLE INSTALL --BINSTUBS
-       If  you	use  the   --binstubs	flag   in   [bundle   install(1)][bun-
-       dle-install(1)],  Bundler  will automatically create a directory (which
-       defaults to app_root/bin) containing all of the	executables  available
-       from gems in the bundle.
+       If  you	use  the   --binstubs	flag   in   bundle   install(1)   bun-
+       dle-install.1.html,  Bundler  will  automatically  create  a  directory
+       (which defaults to app_root/bin)  containing  all  of  the  executables
+       available from gems in the bundle.
 
        After  using --binstubs, bin/rspec spec/my_spec.rb is identical to bun-
        dle exec rspec spec/my_spec.rb.
@@ -175,4 +175,4 @@ RUBYGEMS PLUGINS
 
 
 
-				 February 2018			BUNDLE-EXEC(1)
+				   July 2018			BUNDLE-EXEC(1)

data/man/bundle-exec.ronn

@@ -12,7 +12,7 @@ This command executes the command, making all gems specified in the
 
 Essentially, if you would normally have run something like
 `rspec spec/my_spec.rb`, and you want to use the gems specified
-in the [`Gemfile(5)`][Gemfile(5)] and installed via [bundle install(1)][bundle-install(1)], you
+in the [`Gemfile(5)`][Gemfile(5)] and installed via [bundle install(1)](bundle-install.1.html), you
 should run `bundle exec rspec spec/my_spec.rb`.
 
 Note that `bundle exec` does not require that an executable is
@@ -27,7 +27,7 @@ available on your shell's `$PATH`.
 
 ## BUNDLE INSTALL --BINSTUBS
 
-If you use the `--binstubs` flag in [bundle install(1)][bundle-install(1)], Bundler will
+If you use the `--binstubs` flag in [bundle install(1)](bundle-install.1.html), Bundler will
 automatically create a directory (which defaults to `app_root/bin`)
 containing all of the executables available from gems in the bundle.
 

data/man/bundle-gem.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-GEM" "1" "February 2018" "" ""
+.TH "BUNDLE\-GEM" "1" "July 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-gem\fR \- Generate a project skeleton for creating a rubygem
@@ -74,7 +74,7 @@ Open the resulting GEM_NAME\.gemspec in EDITOR, or the default editor if not spe
 .SH "SEE ALSO"
 .
 .IP "\(bu" 4
-[bundle config(1)][bundle\-config(1)]
+bundle config(1) \fIbundle\-config\.1\.html\fR
 .
 .IP "" 0
 

data/man/bundle-gem.1.txt

@@ -81,11 +81,11 @@ OPTIONS
 	      $VISUAL, or $EDITOR.
 
 SEE ALSO
-       o   [bundle config(1)][bundle-config(1)]
+       o   bundle config(1) bundle-config.1.html
 
 
 
 
 
 
-				 February 2018			 BUNDLE-GEM(1)
+				   July 2018			 BUNDLE-GEM(1)

data/man/bundle-gem.ronn

@@ -75,4 +75,4 @@ configuration file using the following names:
 
 ## SEE ALSO
 
-* [bundle config(1)][bundle-config(1)]
+* [bundle config(1)](bundle-config.1.html)

data/man/bundle-info.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-INFO" "1" "January 2018" "" ""
+.TH "BUNDLE\-INFO" "1" "July 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-info\fR \- Show information for the given gem in your bundle

data/man/bundle-info.1.txt

@@ -18,4 +18,4 @@ OPTIONS
 
 
 
-				 January 2018			BUNDLE-INFO(1)
+				   July 2018			BUNDLE-INFO(1)

data/man/bundle-init.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-INIT" "1" "May 2018" "" ""
+.TH "BUNDLE\-INIT" "1" "July 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-init\fR \- Generates a Gemfile into the current working directory

data/man/bundle-init.1.txt

@@ -31,4 +31,4 @@ SEE ALSO
 
 
 
-				   May 2018			BUNDLE-INIT(1)
+				   July 2018			BUNDLE-INIT(1)

data/man/bundle-inject.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-INJECT" "1" "February 2018" "" ""
+.TH "BUNDLE\-INJECT" "1" "July 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-inject\fR \- Add named gem(s) with version requirements to Gemfile

data/man/bundle-inject.1.txt

@@ -29,4 +29,4 @@ DESCRIPTION
 
 
 
-				 February 2018		      BUNDLE-INJECT(1)
+				   July 2018		      BUNDLE-INJECT(1)

data/man/bundle-install.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-INSTALL" "1" "May 2018" "" ""
+.TH "BUNDLE\-INSTALL" "1" "July 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-install\fR \- Install the dependencies specified in your Gemfile
@@ -291,7 +291,7 @@ Even though \fBactivemerchant\fR declares a very loose dependency that theoretic
 To explicitly update \fBactionpack\fR, including its dependencies which other gems in the Gemfile(5) still depend on, run \fBbundle update actionpack\fR (see \fBbundle update(1)\fR)\.
 .
 .P
-\fBSummary\fR: In general, after making a change to the Gemfile(5) , you should first try to run \fBbundle install\fR, 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(1)]\.
+\fBSummary\fR: In general, after making a change to the Gemfile(5) , you should first try to run \fBbundle install\fR, 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) \fIbundle\-update\.1\.html\fR\.
 .
 .SH "SEE ALSO"
 .

data/man/bundle-install.1.txt

@@ -369,7 +369,7 @@ CONSERVATIVE UPDATING
        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(1)].
+       work, run bundle update(1) bundle-update.1.html.
 
 SEE ALSO
        o   Gem				install 			  docs
@@ -382,4 +382,4 @@ SEE ALSO
 
 
 
-				   May 2018		     BUNDLE-INSTALL(1)
+				   July 2018		     BUNDLE-INSTALL(1)

data/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(1)].
+does not work, run [bundle update(1)](bundle-update.1.html).
 
 ## SEE ALSO
 

data/man/bundle-list.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-LIST" "1" "May 2018" "" ""
+.TH "BUNDLE\-LIST" "1" "July 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-list\fR \- List all the gems in the bundle

data/man/bundle-list.1.txt

@@ -18,4 +18,4 @@ OPTIONS
 
 
 
-				   May 2018			BUNDLE-LIST(1)
+				   July 2018			BUNDLE-LIST(1)

data/man/bundle-lock.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-LOCK" "1" "February 2018" "" ""
+.TH "BUNDLE\-LOCK" "1" "July 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-lock\fR \- Creates / Updates a lockfile without installing
@@ -81,4 +81,4 @@ If you want your bundle to support platforms other than the one you\'re running
 For a full explanation of gem platforms, see \fBgem help platform\fR\.
 .
 .SH "PATCH LEVEL OPTIONS"
-See [bundle update(1)][bundle\-update(1)] for details\.
+See bundle update(1) \fIbundle\-update\.1\.html\fR for details\.

data/man/bundle-lock.1.txt

@@ -86,8 +86,8 @@ SUPPORTING OTHER PLATFORMS
        For a full explanation of gem platforms, see gem help platform.
 
 PATCH LEVEL OPTIONS
-       See [bundle update(1)][bundle-update(1)] for details.
+       See bundle update(1) bundle-update.1.html for details.
 
 
 
-				 February 2018			BUNDLE-LOCK(1)
+				   July 2018			BUNDLE-LOCK(1)

data/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(1)] for details.
+See [bundle update(1)](bundle-update.1.html) for details.

data/man/bundle-open.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-OPEN" "1" "February 2017" "" ""
+.TH "BUNDLE\-OPEN" "1" "July 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-open\fR \- Opens the source directory for a gem in your bundle

data/man/bundle-open.1.txt

@@ -26,4 +26,4 @@ DESCRIPTION
 
 
 
-				 February 2017			BUNDLE-OPEN(1)
+				   July 2018			BUNDLE-OPEN(1)

data/man/bundle-outdated.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-OUTDATED" "1" "February 2018" "" ""
+.TH "BUNDLE\-OUTDATED" "1" "July 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-outdated\fR \- List installed gems with newer versions available
@@ -71,7 +71,7 @@ Only list minor newer versions\.
 Only list patch newer versions\.
 .
 .SH "PATCH LEVEL OPTIONS"
-See [bundle update(1)][bundle\-update(1)] for details\.
+See bundle update(1) \fIbundle\-update\.1\.html\fR for details\.
 .
 .P
 One difference between the patch level options in \fBbundle update\fR and here is the \fB\-\-strict\fR option\. \fB\-\-strict\fR was already an option on outdated before the patch level options were added\. \fB\-\-strict\fR wasn\'t altered, and the \fB\-\-update\-strict\fR option on \fBoutdated\fR reflects what \fB\-\-strict\fR does on \fBbundle update\fR\.

data/man/bundle-outdated.1.txt

@@ -63,7 +63,7 @@ OPTIONS
 	      Only list patch newer versions.
 
 PATCH LEVEL OPTIONS
-       See [bundle update(1)][bundle-update(1)] for details.
+       See bundle update(1) bundle-update.1.html 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
@@ -124,4 +124,4 @@ FILTERING OUTPUT
 
 
 
-				 February 2018		    BUNDLE-OUTDATED(1)
+				   July 2018		    BUNDLE-OUTDATED(1)

data/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(1)] for details.
+See [bundle update(1)](bundle-update.1.html) 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/man/bundle-package.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-PACKAGE" "1" "February 2018" "" ""
+.TH "BUNDLE\-PACKAGE" "1" "July 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-package\fR \- Package your needed \fB\.gem\fR files into your application
@@ -19,7 +19,7 @@ Since Bundler 1\.2, the \fBbundle package\fR command can also package \fB:git\fR
 When using gems that have different packages for different platforms, Bundler 1\.8 and newer support caching of gems for other platforms where the Gemfile has been resolved (i\.e\. present in the lockfile) in \fBvendor/cache\fR\. This needs to be enabled via the \fB\-\-all\-platforms\fR option\. This setting will be remembered in your local bundler configuration\.
 .
 .SH "REMOTE FETCHING"
-By default, if you run \fBbundle install(1)\fR][bundle\-install(1)] after running bundle package(1) \fIbundle\-package\.html\fR, bundler will still connect to \fBrubygems\.org\fR to check whether a platform\-specific gem exists for any of the gems in \fBvendor/cache\fR\.
+By default, if you run \fBbundle install(1)\fR](bundle\-install\.1\.html) after running bundle package(1) \fIbundle\-package\.1\.html\fR, bundler will still connect to \fBrubygems\.org\fR to check whether a platform\-specific gem exists for any of the gems in \fBvendor/cache\fR\.
 .
 .P
 For instance, consider this Gemfile(5):
@@ -52,4 +52,4 @@ If you know for sure that the gems packaged in \fBvendor/cache\fR are appropriat
 One way to be sure that you have the right platformed versions of all your gems is to run \fBbundle package\fR on an identical machine and check in the gems\. For instance, you can run \fBbundle package\fR on an identical staging box during your staging process, and check in the \fBvendor/cache\fR before deploying to production\.
 .
 .P
-By default, bundle package(1) \fIbundle\-package\.html\fR fetches and also installs the gems to the default location\. To package the dependencies to \fBvendor/cache\fR without installing them to the local install location, you can run \fBbundle package \-\-no\-install\fR\.
+By default, bundle package(1) \fIbundle\-package\.1\.html\fR fetches and also installs the gems to the default location\. To package the dependencies to \fBvendor/cache\fR without installing them to the local install location, you can run \fBbundle package \-\-no\-install\fR\.

data/man/bundle-package.1.txt

@@ -28,10 +28,10 @@ SUPPORT FOR MULTIPLE PLATFORMS
        This setting will be remembered in your local bundler configuration.
 
 REMOTE FETCHING
-       By default, if you run bundle install(1)][bundle-install(1)] after run-
-       ning bundle package(1) bundle-package.html, bundler will still  connect
-       to rubygems.org to check whether a platform-specific gem exists for any
-       of the gems in vendor/cache.
+       By  default, if you run bundle install(1)](bundle-install.1.html) after
+       running bundle package(1)  bundle-package.1.html,  bundler  will  still
+       connect to rubygems.org to check whether a platform-specific gem exists
+       for any of the gems in vendor/cache.
 
        For instance, consider this Gemfile(5):
 
@@ -69,11 +69,11 @@ REMOTE FETCHING
        staging	box during your staging process, and check in the vendor/cache
        before deploying to production.
 
-       By default, bundle  package(1)  bundle-package.html  fetches  and  also
+       By default, bundle package(1) bundle-package.1.html  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.
 
 
 
-				 February 2018		     BUNDLE-PACKAGE(1)
+				   July 2018		     BUNDLE-PACKAGE(1)

data/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(1)] after running
-[bundle package(1)][bundle-package(1)], bundler will still connect to `rubygems.org`
+By default, if you run `bundle install(1)`](bundle-install.1.html) after running
+[bundle package(1)](bundle-package.1.html), 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(1)] fetches and also
+By default, [bundle package(1)](bundle-package.1.html) 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/man/bundle-platform.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-PLATFORM" "1" "February 2017" "" ""
+.TH "BUNDLE\-PLATFORM" "1" "July 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-platform\fR \- Displays platform compatibility information

data/man/bundle-platform.1.txt

@@ -54,4 +54,4 @@ OPTIONS
 
 
 
-				 February 2017		    BUNDLE-PLATFORM(1)
+				   July 2018		    BUNDLE-PLATFORM(1)

data/man/bundle-pristine.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-PRISTINE" "1" "January 2018" "" ""
+.TH "BUNDLE\-PRISTINE" "1" "July 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-pristine\fR \- Restores installed gems to their pristine condition

data/man/bundle-pristine.1.txt

@@ -41,4 +41,4 @@ DESCRIPTION
 
 
 
-				 January 2018		    BUNDLE-PRISTINE(1)
+				   July 2018		    BUNDLE-PRISTINE(1)

data/man/bundle-show.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-SHOW" "1" "February 2018" "" ""
+.TH "BUNDLE\-SHOW" "1" "July 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-show\fR \- Shows all the gems in your bundle, or the path to a gem

data/man/bundle-show.1.txt

@@ -23,4 +23,4 @@ OPTIONS
 
 
 
-				 February 2018			BUNDLE-SHOW(1)
+				   July 2018			BUNDLE-SHOW(1)

data/man/bundle-update.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-UPDATE" "1" "May 2018" "" ""
+.TH "BUNDLE\-UPDATE" "1" "July 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-update\fR \- Update your gems to the latest available versions
@@ -10,7 +10,7 @@
 \fBbundle update\fR \fI*gems\fR [\-\-group=NAME] [\-\-source=NAME] [\-\-local] [\-\-ruby] [\-\-bundler[=VERSION]] [\-\-full\-index] [\-\-jobs=JOBS] [\-\-quiet] [\-\-force] [\-\-patch|\-\-minor|\-\-major] [\-\-strict] [\-\-conservative]
 .
 .SH "DESCRIPTION"
-Update the gems specified (all gems, if none are specified), ignoring the previously installed gems specified in the \fBGemfile\.lock\fR\. In general, you should use [bundle install(1)][bundle\-install(1)] to install the same exact gems and versions across machines\.
+Update the gems specified (all gems, if none are specified), ignoring the previously installed gems specified in the \fBGemfile\.lock\fR\. In general, you should use bundle install(1) \fIbundle\-install\.1\.html\fR to install the same exact gems and versions across machines\.
 .
 .P
 You would use \fBbundle update\fR to explicitly update the version of a gem\.
@@ -97,7 +97,7 @@ gem "nokogiri"
 .IP "" 0
 .
 .P
-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:
+When you run bundle install(1) \fIbundle\-install\.1\.html\fR the first time, bundler will resolve all of the dependencies, all the way down, and install what you need:
 .
 .IP "" 4
 .
@@ -140,10 +140,10 @@ Use `bundle show [gemname]` to see where a bundled gem is installed\.
 .IP "" 0
 .
 .P
-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 \fBGemfile\.lock\fR\. 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\.
+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 \fBGemfile\.lock\fR\. The next time you run bundle install(1) \fIbundle\-install\.1\.html\fR, bundler skips the dependency resolution and installs the same gems as it installed last time\.
 .
 .P
-After checking in the \fBGemfile\.lock\fR into version control and cloning it on another machine, running [bundle install(1)][bundle\-install(1)] will \fIstill\fR install the gems that you installed last time\. You don\'t need to worry that a new release of \fBerubis\fR or \fBmail\fR changes the gems you use\.
+After checking in the \fBGemfile\.lock\fR into version control and cloning it on another machine, running bundle install(1) \fIbundle\-install\.1\.html\fR will \fIstill\fR install the gems that you installed last time\. You don\'t need to worry that a new release of \fBerubis\fR or \fBmail\fR changes the gems you use\.
 .
 .P
 However, from time to time, you might want to update the gems you are using to the newest versions that still match the gems in your Gemfile(5)\.
@@ -204,10 +204,10 @@ In this case, the two gems have their own set of dependencies, but they share \f
 In short, by default, when you update a gem using \fBbundle update\fR, bundler will update all dependencies of that gem, including those that are also dependencies of another gem\.
 .
 .P
-To prevent updating shared dependencies, prior to version 1\.14 the only option was the \fBCONSERVATIVE UPDATING\fR behavior in [bundle install(1)][bundle\-install(1)]:
+To prevent updating shared dependencies, prior to version 1\.14 the only option was the \fBCONSERVATIVE UPDATING\fR behavior in bundle install(1) \fIbundle\-install\.1\.html\fR:
 .
 .P
-In this scenario, updating the \fBthin\fR version manually in the Gemfile(5), and then running [bundle install(1)][bundle\-install(1)] will only update \fBdaemons\fR and \fBeventmachine\fR, but not \fBrack\fR\. For more information, see the \fBCONSERVATIVE UPDATING\fR section of [bundle install(1)][bundle\-install(1)]\.
+In this scenario, updating the \fBthin\fR version manually in the Gemfile(5), and then running bundle install(1) \fIbundle\-install\.1\.html\fR will only update \fBdaemons\fR and \fBeventmachine\fR, but not \fBrack\fR\. For more information, see the \fBCONSERVATIVE UPDATING\fR section of bundle install(1) \fIbundle\-install\.1\.html\fR\.
 .
 .P
 Starting with 1\.14, specifying the \fB\-\-conservative\fR option will also prevent shared dependencies from being updated\.
@@ -375,7 +375,7 @@ Make sure to check the updated \fBGemfile\.lock\fR into version control
 $ git add Gemfile\.lock
 .
 .IP "\(bu" 4
-If [bundle install(1)][bundle\-install(1)] reports a conflict, manually update the specific gems that you changed in the Gemfile(5)
+If bundle install(1) \fIbundle\-install\.1\.html\fR reports a conflict, manually update the specific gems that you changed in the Gemfile(5)
 .
 .IP
 $ bundle update rails thin