tag:help.rubygems.org,2010-01-19:/discussions/problems/482-cant-list-older-gemsRubyGems.org: Discussion 2011-05-27T00:26:52Ztag:help.rubygems.org,2010-01-19:Comment/50656362011-02-01T21:46:02Z2011-02-01T21:46:02ZCan't list older gems<div><p>I can't reproduce, can you show any code?</p>
<pre>
<code>$ gem list -ra rake$
*** REMOTE GEMS ***
rake (0.8.7, 0.8.6, 0.8.5, 0.8.4, 0.8.3, 0.8.2, 0.8.1, 0.8.0, 0.7.3, 0.7.2, 0.7.1, 0.7.0, 0.6.2, 0.6.0, 0.5.4, 0.5.3, 0.5.0, 0.4.15, 0.4.14, 0.4.13, 0.4.12, 0.4.11, 0.4.10, 0.4.9, 0.4.8)</code>
</pre></div>Eric Hodeltag:help.rubygems.org,2010-01-19:Comment/50656362011-02-02T10:39:54Z2011-02-02T10:39:54ZCan't list older gems<div><p>No content.</p></div>Sylvain Joyeuxtag:help.rubygems.org,2010-01-19:Comment/50656362011-02-02T14:08:34Z2011-02-02T14:08:35ZCan't list older gems<div><p>Mm... replied by email but it did not end up there ...</p>
<p>From your answer, I could find what I was doing wrong.</p>
<p>The issue (and I don't know if it is a bug, a known limitation
or a feature) is that SpecFetcher#find_matching, when 'all' is set
to false, will return an empty set when given constraints that do
not match the newest gem, even though there are gems that match the
constraint.</p>
<p>I.e., in the general case, if you give constraints, also set
'all' to true.</p>
<p>I was not expecting that, but I guess it can be seen as an
acceptable limitation of #find_matching</p></div>Sylvain Joyeuxtag:help.rubygems.org,2010-01-19:Comment/50656362011-05-27T00:26:52Z2011-05-27T00:26:52ZCan't list older gems<div><p>Is this still happening? Not seeing this. Let us know and reopen
this ticket if so!</p></div>Nick Quaranto