tag:help.rubygems.org,2010-01-19:/discussions/problems/28881-409-conflict-returned-for-non-existent-gemRubyGems.org: Discussion 2018-03-06T23:49:50Ztag:help.rubygems.org,2010-01-19:Comment/440890842017-11-21T15:31:54Z2017-11-21T15:31:54Z409 Conflict returned for non-existent gem<div><p>Some additional info:</p>
<p>When using the RubyGems API (<code>curl 'https://rubygems.org/api/v1/gems/calligraphy/owners.json'</code>), I was able to get a list of supposed owners for <code>calligraphy</code>, but when I look up the owner listed, using one of the API Owner methods (<code>curl 'https://rubygems.org/api/v1/owners/amckinnell/gems.json'</code>), the only gems that come back are <code>callgraphy</code> and <code>nutrella</code>. Neither of them have the same name as mine, <code>calligraphy</code>, although one is close (just missing one letter).</p>
<p>Without knowing too much about the implementation, it seems like there may be a issue with matching similarly named gems during operations like <code>gem push</code>.</p>
<p>Here are the gemspecs for the similarly named gems:</p>
<ul>
<li>
<p><a href="https://github.com/eanlain/calligraphy/blob/master/calligraphy.gemspec">https://github.com/eanlain/calligraphy/blob/master/calligraphy.gemspec</a></p>
</li>
<li>
<p><a href="https://github.com/amckinnell/callgraphy/blob/master/callgraphy.gemspec">https://github.com/amckinnell/callgraphy/blob/master/callgraphy.gem...</a></p>
</li>
</ul></div>Brandon Robinstag:help.rubygems.org,2010-01-19:Comment/440890842018-03-06T23:49:49Z2018-03-06T23:49:49Z409 Conflict returned for non-existent gem<div><p>It appears that we do indeed have a gem of that name in our system: <a href="https://rubygems.org/gems/calligraphy">https://rubygems.org/gems/calligraphy</a></p></div>kerrizor