Today, I was going to install a new production bench on a fresh Ubuntu 16 Virtual Server image.
After updating my system and downloading install.py, I created frappe user and gave him sudo permissions, as per tutorial. Starting installation with this command (As root):
python3 install.py --production --user frappe
Results in:
OK:1 http://ch.archive.ubuntu.com/ubuntu xenial InRelease
OK:2 http://ch.archive.ubuntu.com/ubuntu xenial-updates InRelease
OK:3 http://ch.archive.ubuntu.com/ubuntu xenial-backports InRelease
OK:4 http://security.ubuntu.com/ubuntu xenial-security InRelease
Paketlisten werden gelesen... Fertig
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
E: Paket libssl1.0-dev kann nicht gefunden werden. //This translates into: Package libssl1.0-dev could not be found.
E: Mittels des Musters »libssl1.0-dev« konnte kein Paket gefunden werden. // By pattern libssl1.0-dev was no package found.
E: Mittels regulärem Ausdruck »libssl1.0-dev« konnte kein Paket gefunden werden. // By regular expression libssl1.0-dev was no package found
Traceback (most recent call last):
File "install.py", line 413, in <module>
install_bench(args)
File "install.py", line 21, in install_bench
'sudo yum install -y epel-release redhat-lsb-core git python-setuptools python-devel openssl-devel libffi-devel'
File "install.py", line 226, in run_os_command
returncode = subprocess.check_call(command, shell=True)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command 'sudo apt-get install -y git build-essential python3-setuptools python3-dev libffi-dev libssl1.0-dev' returned non-zero exit status 100
My guess is, that the installation script is currently broken and leads to a package that no longer exists.
Right now, I’m trying to replace the package “libssl1.0-dev” with “libssl-dev” and I’ll let you know how and if it works.
Edit: This missing package is still listed as a dependency in site.yaml. This is a temporary file that deletes itself once the installation fails, so I currently have no way of accessing it and replacing the broken package.
Regards,
Val