Skip to content

Instantly share code, notes, and snippets.

@jendiamond
Last active December 21, 2015 21:39
Show Gist options
  • Save jendiamond/6369821 to your computer and use it in GitHub Desktop.
Save jendiamond/6369821 to your computer and use it in GitHub Desktop.
Week 7 Day 32 (Wednesday August 28th)

Week 7 Day 32

##(Wednesday August 28th)

Jen's Wednesday

I was looking at the issue again and I noticed a link at the bottom of the page. It went to and [older issue.}(rubygems/bundler#1915)

'bundle outdated' gives success incorrectly

No milestone No one is assigned With bundler-1.2.0.pre installed, I run "bundle outdated gemname-with-typo" — misleadingly it reports success, I think because my bundle is technically up-to-date, since is not actually a gem.

Fetching gem metadata from http://rubygems.org/........
Fetching gem metadata from http://rubygems.org/..

Outdated gems included in the bundle:
Your bundle is up to date
An error message like "gemname-with-typo not found" instead would be greatly clarifying.

Re-creating the Error

adelcambre's suggested that I make a directory with a Gemfile and run bundle outdated and see what happens when you specify a gem in the Gemfile, vs one that isn't.

Andy's test looked like this:

$ mkdir test_outdated  
$ cd test_outdated  
$ vi Gemfile  
$ bundle  
  Fetching gem metadata from https://rubygems.org/..  
  Resolving dependencies...  
  Using rake (10.1.0)   
  Using bundler (1.3.5)   
  Your bundle is complete!  
  Use `bundle show [gemname]` to see where a bundled gem is installed.  
$ bundle outdated rake  
  Fetching gem metadata from https://rubygems.org/..  
  Resolving dependencies...  

  Your bundle is up to date!  
  ...

He notes: One gem in the gemfile (rake), bundle outdated rake and bundle outdated rails look exactly the same even though rake is there and rails isn't

My test looked like this:

I ran $ bundle outdated serv to check the error because there is no serv gem listed in the Gemfile.

$ bundle outdated serv
  Fetching gem metadata from https://rubygems.org/..........
  Fetching gem metadata from https://rubygems.org/..
  Resolving dependencies...

  Your bundle is up to date!

$ bundle outdated rake
  You have requested:
  rake = 10.0.4

  The bundle currently has rake locked at 10.1.0.
  Try running `bundle update rake`

So yes it worked, I re-created the error or in this case the lack there of.

I took a break to deal with my land-lord and my broken sink and leaking toilet. I returned to find that Jessica had made comments on all my pull requests so I started doing 8 corrections then squashed them all. I am feeling pretty comfortable with squashing and rebasing now. This time when everything went awry on one of the squashings I was able to figure out how to fix it on my own.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment