bundler 1.16.0 → 1.16.1

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" "September 2017" "" ""
+.TH "BUNDLE\-PLATFORM" "1" "February 2017" "" ""
 .
 .SH "NAME"
 \fBbundle\-platform\fR \- Displays platform compatibility information

data/man/bundle-platform.1.txt

@@ -2,14 +2,14 @@ BUNDLE-PLATFORM(1)					    BUNDLE-PLATFORM(1)
 
 
 
-1mNAME0m
-       1mbundle-platform 22m- Displays platform compatibility information
+NAME
+       bundle-platform - Displays platform compatibility information
 
-1mSYNOPSIS0m
-       1mbundle platform 22m[--ruby]
+SYNOPSIS
+       bundle platform [--ruby]
 
-1mDESCRIPTION0m
-       1mplatform  22mwill display information from your Gemfile, Gemfile.lock, and
+DESCRIPTION
+       platform  will display information from your Gemfile, Gemfile.lock, and
        Ruby VM about your platform.
 
        For instance, using this Gemfile(5):
@@ -24,7 +24,7 @@ BUNDLE-PLATFORM(1)					    BUNDLE-PLATFORM(1)
 
 
 
-       If you run 1mbundle platform 22mon Ruby 1.9.3, it will display the following
+       If you run bundle platform on Ruby 1.9.3, it will display the following
        output:
 
 
@@ -41,17 +41,17 @@ BUNDLE-PLATFORM(1)					    BUNDLE-PLATFORM(1)
 
 
 
-       1mplatform  22mwill  list  all the platforms in your 1mGemfile.lock 22mas well as
-       the 1mruby 22mdirective if applicable from your Gemfile(5). It will also let
-       you know if the 1mruby 22mdirective requirement has been met. If 1mruby 22mdirec-
+       platform  will  list  all the platforms in your Gemfile.lock as well as
+       the ruby directive if applicable from your Gemfile(5). It will also let
+       you know if the ruby directive requirement has been met. If ruby direc-
        tive doesn't match the running Ruby VM, it will tell you what part does
        not.
 
-1mOPTIONS0m
-       1m--ruby 22mIt  will  display  the  ruby directive information, so you don't
+OPTIONS
+       --ruby It  will	display  the  ruby directive information, so you don't
 	      have to parse it from the Gemfile(5).
 
 
 
 
-				September 2017		    BUNDLE-PLATFORM(1)
+				 February 2017		    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" "October 2017" "" ""
+.TH "BUNDLE\-PRISTINE" "1" "August 2017" "" ""
 .
 .SH "NAME"
 \fBbundle\-pristine\fR \- Restores installed gems to their pristine condition

data/man/bundle-pristine.1.txt

@@ -2,43 +2,43 @@ BUNDLE-PRISTINE(1)					    BUNDLE-PRISTINE(1)
 
 
 
-1mNAME0m
-       1mbundle-pristine 22m- Restores installed gems to their pristine condition
+NAME
+       bundle-pristine - Restores installed gems to their pristine condition
 
-1mSYNOPSIS0m
-       1mbundle pristine0m
+SYNOPSIS
+       bundle pristine
 
-1mDESCRIPTION0m
-       1mpristine  22mrestores	the  installed gems in the bundle to their pristine
+DESCRIPTION
+       pristine  restores  the	installed gems in the bundle to their pristine
        condition using the local gem cache from  RubyGems.  For  git  gems,  a
        forced checkout will be performed.
 
-       For  further  explanation,  1mbundle  pristine  22mignores unpacked files on
-       disk. In other words, this command utilizes the local 1m.gem 22mcache or the
+       For  further  explanation,  bundle  pristine  ignores unpacked files on
+       disk. In other words, this command utilizes the local .gem cache or the
        gem's git repository as if one were installing from scratch.
 
        Note:  the  Bundler  gem  cannot be restored to its original state with
-       1mpristine22m. One also cannot use 1mbundle pristine 22mon  gems  with  a  'path'
+       pristine. One also cannot use bundle pristine on  gems  with  a	'path'
        option  in  the	Gemfile,  because  bundler has no original copy it can
        restore from.
 
-       When is it practical to use 1mbundle pristine22m?
+       When is it practical to use bundle pristine?
 
-       It comes in handy when a developer is debugging a gem. 1mbundle	pristine0m
+       It comes in handy when a developer is debugging a gem. bundle  pristine
        is a great way to get rid of experimental changes to a gem that one may
        not want.
 
-       Why use 1mbundle pristine 22mover 1mgem pristine --all22m?
+       Why use bundle pristine over gem pristine --all?
 
-       Both commands are very similar. For context: 1mbundle  pristine22m,  without
-       arguments,  cleans  all gems from the lockfile. Meanwhile, 1mgem pristine0m
-       1m--all 22mcleans all installed gems for that Ruby version.
+       Both commands are very similar. For context: bundle  pristine,  without
+       arguments,  cleans  all gems from the lockfile. Meanwhile, gem pristine
+       --all cleans all installed gems for that Ruby version.
 
        If a developer forgets which gems in their project they might have been
-       debugging,  the Rubygems 1mgem pristine [GEMNAME] 22mcommand may be inconve-
-       nient. One can avoid waiting for 1mgem pristine --all22m,  and  instead	run
-       1mbundle pristine22m.
+       debugging,  the Rubygems gem pristine [GEMNAME] command may be inconve-
+       nient. One can avoid waiting for gem pristine --all,  and  instead  run
+       bundle pristine.
 
 
 
-				 October 2017		    BUNDLE-PRISTINE(1)
+				  August 2017		    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" "September 2017" "" ""
+.TH "BUNDLE\-SHOW" "1" "February 2017" "" ""
 .
 .SH "NAME"
 \fBbundle\-show\fR \- Shows all the gems in your bundle, or the path to a gem

data/man/bundle-show.1.txt

@@ -2,24 +2,24 @@ BUNDLE-SHOW(1)							BUNDLE-SHOW(1)
 
 
 
-1mNAME0m
-       1mbundle-show 22m- Shows all the gems in your bundle, or the path to a gem
+NAME
+       bundle-show - Shows all the gems in your bundle, or the path to a gem
 
-1mSYNOPSIS0m
-       1mbundle show 22m[GEM] [--paths]
+SYNOPSIS
+       bundle show [GEM] [--paths]
 
-1mDESCRIPTION0m
-       Without	the [GEM] option, 1mshow 22mwill print a list of the names and ver-
-       sions of all gems that are required by your 1mGemfile(5)22m.
+DESCRIPTION
+       Without	the [GEM] option, show will print a list of the names and ver-
+       sions of all gems that are required by your Gemfile(5).
 
        Calling show with [GEM] will list the exact location  of  that  gem  on
        your machine.
 
-1mOPTIONS0m
-       1m--paths0m
-	      List the paths of all gems that are required by your 1mGemfile(5)22m.
+OPTIONS
+       --paths
+	      List the paths of all gems that are required by your Gemfile(5).
 
 
 
 
-				September 2017			BUNDLE-SHOW(1)
+				 February 2017			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" "October 2017" "" ""
+.TH "BUNDLE\-UPDATE" "1" "July 2017" "" ""
 .
 .SH "NAME"
 \fBbundle\-update\fR \- Update your gems to the latest available versions

data/man/bundle-update.1.txt

@@ -2,81 +2,81 @@ BUNDLE-UPDATE(1)					      BUNDLE-UPDATE(1)
 
 
 
-1mNAME0m
-       1mbundle-update 22m- Update your gems to the latest available versions
+NAME
+       bundle-update - Update your gems to the latest available versions
 
-1mSYNOPSIS0m
-       1mbundle  update  4m22m*gems24m [--group=NAME] [--source=NAME] [--local] [--ruby]
+SYNOPSIS
+       bundle  update  *gems [--group=NAME] [--source=NAME] [--local] [--ruby]
        [--bundler[=VERSION]] [--full-index] [--jobs=JOBS] [--quiet]  [--force]
        [--patch|--minor|--major] [--strict] [--conservative]
 
-1mDESCRIPTION0m
+DESCRIPTION
        Update  the  gems specified (all gems, if none are specified), ignoring
-       the previously installed gems specified in the  1mGemfile.lock22m.  In  gen-
+       the previously installed gems specified in the  Gemfile.lock.  In  gen-
        eral, you should use [bundle install(1)][bundle-install] to install the
        same exact gems and versions across machines.
 
-       You would use 1mbundle update 22mto explicitly update the version of a gem.
+       You would use bundle update to explicitly update the version of a  gem.
 
-1mOPTIONS0m
-       1m--group=<name>22m, 1m-g=[<name>]0m
-	      Only update the gems in the specified group. For	instance,  you
-	      can  update all gems in the development group with 1mbundle update0m
-	      1m--group development22m. You  can  also	call  1mbundle	update	rails0m
-	      1m--group  test  22mto  update the rails gem and all gems in the test
+OPTIONS
+       --group=<name>, -g=[<name>]
+	      Only  update  the gems in the specified group. For instance, you
+	      can update all gems in the development group with bundle	update
+	      --group  development.  You  can  also  call  bundle update rails
+	      --group test to update the rails gem and all gems  in  the  test
 	      group, for example.
 
-       1m--source=<name>0m
-	      The name of a 1m:git 22mor 1m:path 22msource used in the	Gemfile(5).  For
-	      instance,        with	   a	    1m:git	 22msource	 of
-	      1mhttp://github.com/rails/rails.git22m, you would call 1mbundle  update0m
-	      1m--source rails0m
+       --source=<name>
+	      The  name  of a :git or :path source used in the Gemfile(5). For
+	      instance,       with	 a	  :git	      source	    of
+	      http://github.com/rails/rails.git,  you would call bundle update
+	      --source rails
 
-       1m--local0m
-	      Do  not  attempt	to  fetch  gems remotely and use the gem cache
+       --local
+	      Do not attempt to fetch gems remotely  and  use  the  gem  cache
 	      instead.
 
-       1m--ruby 22mUpdate the locked version of Ruby  to  the  current	version  of
+       --ruby Update  the  locked  version  of	Ruby to the current version of
 	      Ruby.
 
-       1m--bundler0m
+       --bundler
 	      Update the locked version of bundler to the invoked bundler ver-
 	      sion.
 
-       1m--full-index0m
+       --full-index
 	      Fall back to using the single-file index of all gems.
 
-       1m--jobs=[<number>]22m, 1m-j[<number>]0m
-	      Specify the number of jobs to run in parallel. The default is 1m122m.
+       --jobs=[<number>], -j[<number>]
+	      Specify the number of jobs to run in parallel. The default is 1.
 
-       1m--retry=[<number>]0m
-	      Retry failed network or git requests for 4mnumber24m times.
+       --retry=[<number>]
+	      Retry failed network or git requests for number times.
 
-       1m--quiet0m
+       --quiet
 	      Only output warnings and errors.
 
-       1m--force0m
+       --force
 	      Force downloading every gem.
 
-       1m--patch0m
+       --patch
 	      Prefer updating only to next patch version.
 
-       1m--minor0m
+       --minor
 	      Prefer updating only to next minor version.
 
-       1m--major0m
+       --major
 	      Prefer updating to next major version (default).
 
-       1m--strict0m
-	      Do not allow any gem to be updated past latest 1m--patch 22m| 1m--minor0m
-	      | 1m--major22m.
+       --strict
+	      Do not allow any gem to be updated past latest --patch | --minor
+	      | --major.
 
-       1m--conservative0m
+       --conservative
 	      Use bundle install conservative update behavior and do not allow
 	      shared dependencies to be updated.
 
-1mUPDATING ALL GEMS0m
-       If you run 1mbundle update 22mwith no parameters, bundler  will	ignore	any
+UPDATING ALL GEMS
+       If you run bundle update with no parameters, bundler  will  ignore  any
        previously  installed  gems and resolve all dependencies again based on
        the latest versions of all gems available in the sources.
 
@@ -133,41 +133,41 @@ BUNDLE-UPDATE(1)					      BUNDLE-UPDATE(1)
 
        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 1mGemfile.lock22m. The next time you	run
+       the exact versions it installed in Gemfile.lock. The next time you  run
        [bundle install(1)][bundle-install], bundler skips the dependency reso-
        lution and installs the same gems as it installed last time.
 
-       After checking in the 1mGemfile.lock 22minto version control and cloning  it
+       After checking in the Gemfile.lock into version control and cloning  it
        on  another  machine,  running [bundle install(1)][bundle-install] will
-       4mstill24m install the gems that you installed last time. You don't need  to
-       worry that a new release of 1merubis 22mor 1mmail 22mchanges the gems you use.
+       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.
 
        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  Gem-
        file(5).
 
-       To  do this, run 1mbundle update22m, which will ignore the 1mGemfile.lock22m, and
+       To  do this, run bundle update, which will ignore the Gemfile.lock, and
        resolve all the dependencies again. Keep in mind that this process  can
        result  in  a  significantly different set of the 25 gems, based on the
        requirements of new gems that the gem authors released since  the  last
-       time you ran 1mbundle update22m.
+       time you ran bundle update.
 
-1mUPDATING A LIST OF GEMS0m
+UPDATING A LIST OF GEMS
        Sometimes, you want to update a single gem in the Gemfile(5), and leave
        the rest of the gems that you specified locked to the versions  in  the
-       1mGemfile.lock22m.
+       Gemfile.lock.
 
-       For  instance,  in  the	scenario above, imagine that 1mnokogiri 22mreleases
-       version 1m1.4.422m, and you want to update it 4mwithout24m updating Rails and all
-       of its dependencies. To do this, run 1mbundle update nokogiri22m.
+       For  instance,  in  the	scenario above, imagine that nokogiri releases
+       version 1.4.4, and you want to update it without updating Rails and all
+       of its dependencies. To do this, run bundle update nokogiri.
 
-       Bundler	will  update  1mnokogiri  22mand any of its dependencies, but leave
+       Bundler	will  update  nokogiri	and any of its dependencies, but leave
        alone Rails and its dependencies.
 
-1mOVERLAPPING DEPENDENCIES0m
+OVERLAPPING DEPENDENCIES
        Sometimes, multiple gems declared in your Gemfile(5) are  satisfied  by
        the  same  second-level	dependency. For instance, consider the case of
-       1mthin 22mand 1mrack-perftools-profiler22m.
+       thin and rack-perftools-profiler.
 
 
 
@@ -178,8 +178,8 @@ BUNDLE-UPDATE(1)					      BUNDLE-UPDATE(1)
 
 
 
-       The 1mthin 22mgem depends on  1mrack  >=  1.022m,  while  1mrack-perftools-profiler0m
-       depends on 1mrack ~> 1.022m. If you run bundle install, you get:
+       The thin gem depends on	rack  >=  1.0,	while  rack-perftools-profiler
+       depends on rack ~> 1.0. If you run bundle install, you get:
 
 
 
@@ -196,46 +196,46 @@ BUNDLE-UPDATE(1)					      BUNDLE-UPDATE(1)
 
 
        In this case, the two gems have their own set of dependencies, but they
-       share 1mrack 22min common. If you  run  1mbundle  update  thin22m,  bundler  will
-       update  1mdaemons22m, 1meventmachine 22mand 1mrack22m, which are dependencies of 1mthin22m,
-       but  not   1mopen4   22mor   1mperftools.rb22m,	 which	 are   dependencies   of
-       1mrack-perftools_profiler22m.  Note that 1mbundle update thin 22mwill update 1mrack0m
-       even though it's 4malso24m a dependency of 1mrack-perftools_profiler22m.
+       share rack in common. If you  run  bundle  update  thin,  bundler  will
+       update  daemons, eventmachine and rack, which are dependencies of thin,
+       but  not   open4   or   perftools.rb,   which   are   dependencies   of
+       rack-perftools_profiler.  Note that bundle update thin will update rack
+       even though it's also a dependency of rack-perftools_profiler.
 
-       In short, by default, when  you	update	a  gem	using  1mbundle  update22m,
+       In short, by default, when  you	update	a  gem	using  bundle  update,
        bundler	will 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   1mCONSERVATIVE   UPDATING	 22mbehavior   in   [bundle
+       option	 was   the   CONSERVATIVE   UPDATING   behavior   in   [bundle
        install(1)][bundle-install]:
 
-       In this scenario, updating the 1mthin 22mversion manually in the Gemfile(5),
+       In this scenario, updating the thin version manually in the Gemfile(5),
        and  then  running [bundle install(1)][bundle-install] will only update
-       1mdaemons 22mand 1meventmachine22m, but not 1mrack22m. For more information,  see  the
-       1mCONSERVATIVE UPDATING 22msection of [bundle install(1)][bundle-install].
+       daemons and eventmachine, but not rack. For more information,  see  the
+       CONSERVATIVE UPDATING section of [bundle install(1)][bundle-install].
 
-       Starting with 1.14, specifying the 1m--conservative 22moption will also pre-
+       Starting with 1.14, specifying the --conservative option will also pre-
        vent shared dependencies from being updated.
 
-1mPATCH LEVEL OPTIONS0m
+PATCH LEVEL OPTIONS
        Version 1.14 introduced 4 patch-level options that will	influence  how
        gem  versions  are  resolved. One of the following options can be used:
-       1m--patch22m, 1m--minor 22mor 1m--major22m. 1m--strict 22mcan be added to further influence
+       --patch, --minor or --major. --strict can be added to further influence
        resolution.
 
-       1m--patch0m
+       --patch
 	      Prefer updating only to next patch version.
 
-       1m--minor0m
+       --minor
 	      Prefer updating only to next minor version.
 
-       1m--major0m
+       --major
 	      Prefer updating to next major version (default).
 
-       1m--strict0m
-	      Do not allow any gem to be updated past latest 1m--patch 22m| 1m--minor0m
-	      | 1m--major22m.
+       --strict
+	      Do not allow any gem to be updated past latest --patch | --minor
+	      | --major.
 
        When Bundler is resolving what versions	to  use  to  satisfy  declared
        requirements  in  the Gemfile or in parent gems, it looks up all avail-
@@ -243,38 +243,38 @@ BUNDLE-UPDATE(1)					      BUNDLE-UPDATE(1)
        ment, and then, by default, sorts them from newest to oldest, consider-
        ing them in that order.
 
-       Providing one of the patch level options  (e.g.	1m--patch22m)  changes	the
+       Providing one of the patch level options  (e.g.	--patch)  changes  the
        sort  order of the satisfying versions, causing Bundler to consider the
-       latest 1m--patch 22mor 1m--minor 22mversion available before other versions. Note
+       latest --patch or --minor version available before other versions. Note
        that versions outside the stated patch level could still be resolved to
        if necessary to find a suitable dependency graph.
 
        For example, if gem 'foo' is locked at 1.0.2, with no  gem  requirement
        defined	in the Gemfile, and versions 1.0.3, 1.0.4, 1.1.0, 1.1.1, 2.0.0
-       all exist, the default order of preference by default (1m--major22m) will be
+       all exist, the default order of preference by default (--major) will be
        "2.0.0, 1.1.1, 1.1.0, 1.0.4, 1.0.3, 1.0.2".
 
-       If  the	1m--patch 22moption is used, the order of preference will change to
+       If  the	--patch option is used, the order of preference will change to
        "1.0.4, 1.0.3, 1.0.2, 1.1.1, 1.1.0, 2.0.0".
 
-       If the 1m--minor 22moption is used, the order of preference will  change  to
+       If the --minor option is used, the order of preference will  change  to
        "1.1.1, 1.1.0, 1.0.4, 1.0.3, 1.0.2, 2.0.0".
 
-       Combining  the 1m--strict 22moption with any of the patch level options will
+       Combining  the --strict option with any of the patch level options will
        remove any versions beyond the scope of	the  patch  level  option,  to
        ensure that no gem is updated that far.
 
-       To  continue the previous example, if both 1m--patch 22mand 1m--strict 22moptions
+       To  continue the previous example, if both --patch and --strict options
        are used, the available versions for resolution would be "1.0.4, 1.0.3,
-       1.0.2".	If  1m--minor  22mand 1m--strict 22mare used, it would be "1.1.1, 1.1.0,
+       1.0.2".	If  --minor  and --strict are used, it would be "1.1.1, 1.1.0,
        1.0.4, 1.0.3, 1.0.2".
 
        Gem requirements as defined in the Gemfile  will  still	be  the  first
        determining factor for what versions are available. If the gem require-
-       ment for 1mfoo 22min the Gemfile is '~> 1.0', that will accomplish the  same
-       thing as providing the 1m--minor 22mand 1m--strict 22moptions.
+       ment for foo in the Gemfile is '~> 1.0', that will accomplish the  same
+       thing as providing the --minor and --strict options.
 
-1mPATCH LEVEL EXAMPLES0m
+PATCH LEVEL EXAMPLES
        Given the following gem specifications:
 
 
@@ -324,33 +324,33 @@ BUNDLE-UPDATE(1)					      BUNDLE-UPDATE(1)
        the dependency from foo 1.4.5 required it.
 
        In case 2, only foo is requested  to  be  unlocked,  but  bar  is  also
-       allowed to move because it's not a declared dependency in the Gemfile.
+       allowed	to move because it's not a declared dependency in the Gemfile.
 
-       In  case 3, bar goes up a whole major release, because a minor increase
-       is preferred now for foo, and when it goes to 1.5.1, it requires  3.0.0
+       In case 3, bar goes up a whole major release, because a minor  increase
+       is  preferred now for foo, and when it goes to 1.5.1, it requires 3.0.0
        of bar.
 
        In case 4, foo is preferred up to a minor version, but 1.5.1 won't work
-       because the --strict flag removes bar 3.0.0  from  consideration  since
+       because	the  --strict  flag removes bar 3.0.0 from consideration since
        it's a major increment.
 
-       In  case 5, both foo and bar have any minor or major increments removed
-       from consideration because of the --strict flag, so the most  they  can
+       In case 5, both foo and bar have any minor or major increments  removed
+       from  consideration  because of the --strict flag, so the most they can
        move is up to 1.4.4 and 2.0.4.
 
-1mRECOMMENDED WORKFLOW0m
-       In  general, when working with an application managed with bundler, you
+RECOMMENDED WORKFLOW
+       In general, when working with an application managed with bundler,  you
        should use the following workflow:
 
        o   After you create your Gemfile(5) for the first time, run
 
 	   $ bundle install
 
-       o   Check the resulting 1mGemfile.lock 22minto version control
+       o   Check the resulting Gemfile.lock into version control
 
 	   $ git add Gemfile.lock
 
-       o   When checking out this repository on another  development  machine,
+       o   When  checking  out this repository on another development machine,
 	   run
 
 	   $ bundle install
@@ -359,12 +359,12 @@ BUNDLE-UPDATE(1)					      BUNDLE-UPDATE(1)
 
 	   $ bundle install --deployment
 
-       o   After  changing  the  Gemfile(5)  to reflect a new or update depen-
+       o   After changing the Gemfile(5) to reflect a  new  or	update	depen-
 	   dency, run
 
 	   $ bundle install
 
-       o   Make sure to check the updated 1mGemfile.lock 22minto version control
+       o   Make sure to check the updated Gemfile.lock into version control
 
 	   $ git add Gemfile.lock
 
@@ -373,7 +373,7 @@ BUNDLE-UPDATE(1)					      BUNDLE-UPDATE(1)
 
 	   $ bundle update rails thin
 
-       o   If  you want to update all the gems to the latest possible versions
+       o   If you want to update all the gems to the latest possible  versions
 	   that still match the gems listed in the Gemfile(5), run
 
 	   $ bundle update
@@ -383,4 +383,4 @@ BUNDLE-UPDATE(1)					      BUNDLE-UPDATE(1)
 
 
 
-				 October 2017		      BUNDLE-UPDATE(1)
+				   July 2017		      BUNDLE-UPDATE(1)