Rubygems dependency API issue affecting installs of Berkshelf


#1

Hi Chefs,

Starting yesterday, rubygems.org had an issue with their dependency API which bundler uses to determine which gems it should install. If you’ve tried to install Berkshelf 3 via bundler, you likely got an error when installing dep_selector due to dep-selector-libgecode not being installed as a prerequisite. We tracked this down to incorrect data being served by the rubygems dependency API and reported the issue to the rubygems.org team, who are currently working to resolve it.

You can track the progress on this ticket: http://help.rubygems.org/discussions/problems/18416-incorrect-dependencies-returned-by-dependency-api (please don’t spam with +1’s they are currently working on the issue and don’t need additional distraction).


Daniel DeLeo


#2

Seems fixed for me (at least the berkshelf install issue).

Thanks @LamontGranquist and @kallistec!

On Wed, Jul 16, 2014 at 8:41 PM, Daniel DeLeo dan@kallistec.com wrote:

Hi Chefs,

Starting yesterday, rubygems.org had an issue with their dependency API
which bundler uses to determine which gems it should install. If you’ve
tried to install Berkshelf 3 via bundler, you likely got an error when
installing dep_selector due to dep-selector-libgecode not being installed
as a prerequisite. We tracked this down to incorrect data being served by
the rubygems dependency API and reported the issue to the rubygems.org
team, who are currently working to resolve it.

You can track the progress on this ticket:
http://help.rubygems.org/discussions/problems/18416-incorrect-dependencies-returned-by-dependency-api
(please don’t spam with +1’s they are currently working on the issue and
don’t need additional distraction).


Daniel DeLeo