'bundle outdated' gives success incorrectly

[cbfrance]

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.

[indirect]

Yeah, I think an error message if you pass a gemname that doesn't exist would be good. If you feel strongly enough about it to write a pull request, awesome. If not, we'll get to it when we can. Thanks!

[rohitarondekar]

Two issues here:

• It does output as success if you give any gem name not included in your bundle, as reported by OP.
• The output of bundle outdated gem_name or bundle outdated gem1 gem2 gem3 isn't very friendly. It just tells Your bundle is up to date! for either case, assuming the list of gems are up to date of course, but my bundle is not up to date. Only the list of gems I've provided are up to date. My bundle could still be outdated. I think the output should reflect that by saying, gem1, gem2, gem3 are up to date..

[indirect]

The first issue is fixed in master, and will be part of 1.3. The second sounds like its probably a good idea to implement.

On Nov 30, 2012, at 3:27 AM, Rohit Arondekar notifications@github.com wrote:

Two issues here:

It does output as success if you give any gem name not included in your bundle, as reported by OP.
The output of bundle outdated gem_name or bundle outdated gem1 gem2 gem3 isn't very friendly. It just tells Your bundle is up to date! for either case, assuming the list of gems are up to date of course, but my bundle is not up to date. Only the list of gems I've provided are up to date. My bundle could still be outdated. I think the output should reflect that by saying, gem1, gem2, gem3 are up to date..
�
Reply to this email directly or view it on GitHub.

[rohitarondekar]

I don't think so. Just tried with bundler built with latest master and issue 1 still exists. Can you try? If not I might have found a variation of the issue.

[xaviershay]

Still an issue:

> bundle outdated blurgh
Fetching gem metadata from https://rubygems.org/...........
Fetching gem metadata from https://rubygems.org/..
Resolving dependencies...

Your bundle is up to date!
> echo $?
0

Moving to bundler features.