Bug #14799
closed
Installing Foreman
Description
Hi,
I'm trying to install foreman and appears the next error messages:
Setting up foreman-sqlite3 (1.11.1-1) ...
dpkg: error processing package foreman-sqlite3 (--configure):
subprocess installed post-installation script returned error exit status 7
Setting up ruby-foreman-deface (1.0.1) ...
dpkg: error processing package ruby-foreman-deface (--configure):
subprocess installed post-installation script returned error exit status 6
Can anyone help me?
Thanks!
Updated by Anonymous about 8 years ago
https://github.com/theforeman/foreman-packaging/pull/1109/files#diff-7a9a9dc0c7f7886fbfa10d05e4fb4933 - apply that change to /var/lib/dpkg/info/foreman-sqlite3.postinst and try again.
If that does not work, run "export DEBUG=1" and then "dpkg --configure foreman-sqlite3" and paste the output here.
Updated by Lukas Resch about 8 years ago
Using Ubuntu 14.04 i get the same error. Debugging the configuration shows
Could not find gem 'net-ssh (< 3) ruby' in the gems available on this machine.
Trying to install the gem results in
sudo gem install net-ssh
Fetching: net-ssh-3.1.1.gem (100%)
ERROR: Error installing net-ssh:
net-ssh requires Ruby version >= 2.0.
I think the problem is that by default ruby1.9.1 is used and not ruby2.0.
Updated by Dominic Cleal about 8 years ago
- Status changed from New to Feedback
- Pull request https://github.com/theforeman/foreman-packaging/pull/1109 added
I believe the issue with the foreman-sqlite3 package has been fixed for 1.11.2 and in current nightlies, via the linked PR.
Lukas, I don't know if your problem is related to this without more information - please start a thread on the foreman-users list or provide more information in a new bug report, on precisely what steps you're taking and where you're seeing the error. I don't recommend trying to install gems manually while using our packages, you will probably make the situation worse.
Updated by Lukas Resch about 8 years ago
I get the same errors as the OP when trying to install foreman-sqlite3 via apt-get from the trusty/stable repository. The package version I get from there is 1.11.1-1. So I think it is the same issue. Applying the linked patch fixes the installation though.
I just tried to locate the problem, I don't want to manage gems on my own. But it looks like the problem has been fixed already. The fix has just not made it to the stable repository yet.