I installed core4 both with and without the appliance on fresh Debian9 VMs. This issue only comes up on machines which do NOT have the appliance:
The command used to install core4 pip install --edit . (https://github.com/plan-net/core4#core4os-installation-backend-only) is failing right now. This stems from the package rpy2 listing a specific version of the cffi package as one of its requirements. I don't know why this issue does not arise if you have the appliance installed. Need to look into this, but my guess is that the appliance already installs an rpy2-compatible version of cffi before it tries to install rpy2.
i.e., Install cffi before we try to install core4 (and with it, rpy2). I tested this already and pip install --edit . gets executed smoothly after this.
I didn't make a pull request with this change yet because I had issues with making multiple pull requests at the same time the last time I tried it.
I installed core4 both with and without the appliance on fresh Debian9 VMs. This issue only comes up on machines which do NOT have the appliance:
The command used to install core4
pip install --edit .
(https://github.com/plan-net/core4#core4os-installation-backend-only) is failing right now. This stems from the package rpy2 listing a specific version of the cffi package as one of its requirements. I don't know why this issue does not arise if you have the appliance installed. Need to look into this, but my guess is that the appliance already installs an rpy2-compatible version of cffi before it tries to install rpy2.I found a workaround for now: Change this code block in the README as follows:
i.e., Install cffi before we try to install core4 (and with it, rpy2). I tested this already and
pip install --edit .
gets executed smoothly after this.I didn't make a pull request with this change yet because I had issues with making multiple pull requests at the same time the last time I tried it.