Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ruby-build plugin fails on ubuntu 18.04 - libgdbm3 not available #207

Closed
kpmueller opened this issue Mar 8, 2018 · 6 comments
Closed

ruby-build plugin fails on ubuntu 18.04 - libgdbm3 not available #207

kpmueller opened this issue Mar 8, 2018 · 6 comments

Comments

@kpmueller
Copy link
Contributor

Obviously, this is still beta, but 18.04 is coming out soon!

Cookbook version

1.1.0

Chef-client version

12.21

Platform Details

Ubuntu 18.04 beta, upgraded from 17.04 EC2 AMI

Scenario:

I'm using the LWRP to install the ruby-build rbenv plugin

Steps to Reproduce:

Nothing special - install any ruby using ruby-build plugin on ubuntu 18.04

My LWRP is simply something like

rbenv_system_install 'ruby_system'

rbenv_plugin 'ruby-build' do
  git_url 'git://github.com/rbenv/ruby-build.git'
end

... and then install rubies

Expected Result:

That it works

Actual Result:

No candidate version available for libgdbm3

ub18
ub18       * No candidate version available for libgdbm3
ub18       ================================================================================
ub18       Error executing action `install` on resource 'apt_package[gcc, autoconf, bison, build-essential, libssl-dev, libyaml-dev, libreadline6-dev, zlib1g-dev, libncurses5-dev, libffi-dev, libgdbm3, libgdbm-dev, make]'
ub18       ================================================================================
ub18
ub18       Chef::Exceptions::Package
ub18       -------------------------
ub18       No candidate version available for libgdbm3
ub18
ub18       Resource Declaration:
ub18       ---------------------
ub18       # In /var/chef/cache/cookbooks/ruby_rbenv/resources/ruby.rb
ub18
ub18        89:       package package_deps
ub18        90:     end
ub18
ub18       Compiled Resource:
ub18       ------------------
ub18       # Declared in /var/chef/cache/cookbooks/ruby_rbenv/resources/ruby.rb:89:in `install_ruby_dependencies'
ub18
ub18       apt_package("gcc, autoconf, bison, build-essential, libssl-dev, libyaml-dev, libreadline6-dev, zlib1g-dev, libncurses5-dev, libffi-dev, libgdbm3, libgdbm-dev, make") do
ub18         package_name ["gcc", "autoconf", "bison", "build-essential", "libssl-dev", "libyaml-dev", "libreadline6-dev", "zlib1g-dev", "libncurses5-dev", "libffi-dev", "libgdbm3", "libgdbm-dev", "make"]
ub18         action [:install]
ub18         retries 0
ub18         retry_delay 2
ub18         default_guard_interpreter :default
ub18         declared_type :package
ub18         cookbook_name "piazza_ruby"
ub18       end
ub18
ub18       System Info:
ub18       ------------
ub18       chef_version=12.22.1
ub18       platform=ubuntu
ub18       platform_version=18.04
ub18       ruby=ruby 2.3.6p384 (2017-12-14 revision 61254) [x86_64-linux]
ub18       program_name=chef-client worker: ppid=1419;start=03:17:19;
ub18       executable=/opt/chef/bin/chef-client
@kpmueller
Copy link
Contributor Author

Like it just needs to be changed to libgdbm4, I would guess? Assuming ruby-build supports that

@damacus
Copy link
Member

damacus commented Mar 8, 2018

Hi @kpmueller

Would you mind submitting a PR for this? Looks reasonably simple.

Shout if you get stuck or want talking through the code!

@kpmueller
Copy link
Contributor Author

good idea - let me do that

@kpmueller
Copy link
Contributor Author

done: #208

not sure what the preferred way to distinguish platform version differences are. I put in a case statement with a default under the platform family.

@damacus
Copy link
Member

damacus commented Mar 9, 2018

Resolve by #208

@damacus damacus closed this as completed Mar 9, 2018
@lock
Copy link

lock bot commented Mar 9, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Mar 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants