Closed KibaFox closed 6 years ago
Here is a snippet from official.json at the time of the issue.
"synapse": {
"git": {
"branch": "master",
"revision": "3e91f1c31620d68d5d1f5007ef690c7404aa3f7c",
"url": "https://github.com/YunoHost-Apps/synapse_ynh"
},
"lastUpdate": 1523908838
}
Indeed, the list points to an old commit which does not include the recent fixes ... we need to update https://github.com/YunoHost/apps/blob/master/official.json (and ideally really think about using 'HEAD' as a long-term solution to avoid all these headaches of forgetting to update the list ...)
In the meantime, installing from the explicit URL "https://github.com/YunoHost-Apps/synapse_ynh" should work
Thank you, @alexAubin!
@alexAubin - do you mean putting using 'HEAD' as the revision
in the official.json
list? Seeing that would make me a little nervous, since it relies on the master
branch to always be stable.
You could possibly adopt something like Docker tags, where the default is to pull the latest
tag. When you want to release a version of master, you move the latest
tag. This is still something to remember to do, but it shifts the responsibility to this project rather than updating the official.json
.
Just a thought. I'm not familiar with your release process.
Yes, this was something we started discussing a while ago now. Thing is, we already do (as far as (at least) official apps are concerned) all development in a testing
branch and merge it in master
once it's dimmed stable. So updating the commit in official.json is just another step that can be automated - hence the use of HEAD
.
We could indeed have other strategies, using proper tags and release, but that also implies some more knowledge of git/github in general and would need to change existing processes.
On the "security aspect" side, using master/HEAD
as stable means that any people with push-permissions to the repo can trigger an upgrade on people's instance, but those people are actually the same people with push-permissions to YunoHost/Apps so :wink:
That makes sense and I think that'll simplify the process a lot. :)
Installation succeeds. Since it's not an issue with this project, I'm going to go ahead and close the ticket.
I'm currently evaluating migrating my self hosting solutions over to Yunohost and after a fresh install on Digital Ocean, I cannot install the Synapse application.
I'm using Digital Ocean's Debian 8.10 x64 image as a base and I followed the instructions to install manually.
I've repeated this a couple of times and found the same result.
Here is the output from attempting to install from the command line.
It fails to start the
matrix-synapse.service
via Systemd and aborts the install. When I check the logs viajournalctl
I see this:The key error here appears to be:
cannot import name _OpenSSLECCurve