Chef 0.10.0 and dep_selector build issue


#1

Hello all,

Because of some awful trouble I have with chef-solr on my current 0.9
setup (which I’ll probably say some words in another message here), I
was ready to rush the move to 0.10. I installed the gecode package on
my box:
ii libgecode-dev 3.1.0-1
generic constraint development environment
ii libgecode17 3.1.0-1
generic constraint development environment

I’m using ruby 1.8.7 (2011-02-18 patchlevel 334) [x86_64-linux], MBARI
0x6770, Ruby Enterprise Edition 2011.03

I started installing chef 0.10 from scratch and it crashes while
building dep_selector (see attached). Am I the only one concerned by this
issue ? Is there any easy workaround ?

Thanks for your feedback !

Pierre Baillet oct@fotopedia.com
Server Shepherd @ http://www.fotopedia.com/


#2

Hi Pierre,

On Wed, May 11, 2011 at 7:37 AM, Pierre oct@fotonauts.com wrote:

I installed the gecode package on
my box:
ii libgecode-dev 3.1.0-1
generic constraint development environment
ii libgecode17 3.1.0-1
generic constraint development environment

I’m using ruby 1.8.7 (2011-02-18 patchlevel 334) [x86_64-linux], MBARI
0x6770, Ruby Enterprise Edition 2011.03

This is an older version of gecode than what we have built against. I
have libgecode-dev 3.5.0 with libgecode27. I suspect that upgrading
that package will solve your issues. You will also want to have a
recent gcc installed.

Hope that helps.

  • seth


Seth Falcon | Senior Software Design Engineer | Opscode | @sfalcon


#3

Seth,

Thanks for your swift reply ! After further investigation, it seems
that the APT repository you maintain has not been updated for all
flavours:

http://apt.opscode.com/dists/ shows that the Karmic indices do not
contains any reference to the gecode library whereas Maverick’s do.
( http://apt.opscode.com/dists/karmic/main/binary-amd64/Packages
http://apt.opscode.com/dists/maverick/main/binary-amd64/Packages ).

I’m pretty sure the Karmic indices were containing the library at one
point because I followed your indication to add the Opscode repo to
all the server using the lsb-release trick you describe in the Wiki
and everything went ok…

Is this just a simple oversight or have you given up supporting this version ?
Cheers,

Pierre.

On Wed, May 11, 2011 at 4:48 PM, Seth Falcon seth@opscode.com wrote:

Hi Pierre,

On Wed, May 11, 2011 at 7:37 AM, Pierre oct@fotonauts.com wrote:

I installed the gecode package on
my box:
ii libgecode-dev 3.1.0-1
generic constraint development environment
ii libgecode17 3.1.0-1
generic constraint development environment

I’m using ruby 1.8.7 (2011-02-18 patchlevel 334) [x86_64-linux], MBARI
0x6770, Ruby Enterprise Edition 2011.03

This is an older version of gecode than what we have built against. I
have libgecode-dev 3.5.0 with libgecode27. I suspect that upgrading
that package will solve your issues. You will also want to have a
recent gcc installed.

Hope that helps.

  • seth


Seth Falcon | Senior Software Design Engineer | Opscode | @sfalcon


Pierre Baillet oct@fotopedia.com
Server Shepherd @ http://www.fotopedia.com/


#4

On Wed, May 11, 2011 at 8:08 AM, Pierre oct@fotonauts.com wrote:

Is this just a simple oversight or have you given up supporting this version ?

We aren’t supporting the Chef server packaging on Karmic. Basically we
plan to support packaging for the Chef server on LTS and up. This is
due to the sheer number of packages that must be backported, including
old decaying versions of ruby and rubygems.

http://wiki.opscode.com/display/chef/Package+Installation+on+Debian+and+Ubuntu

The table at the top of that page covers what we’re supporting right
now. We’ve been putting together a document internally that I’ll post
to the public wiki and mailing list when done.

Bryan