Backport recent security fixes to 2023.03 or to Elixir 1.13.4 #556
Labels
No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#556
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I've heard from multiple admins (Myself, @a1ba@suya.place and @rosey@neko.computer) that Elixir 1.14 is causing unneeded headaches because this version is still not available in the official Erlang Solutions repository.
A solution to this is to make sure Akkoma runs on 1.13.4, alternatively the security fix can be backported to release 2023.03, which is the last version that still runs on a Elixir version available in the official repository.
If this is not possible and we want to make the asdf version manager the only supported version manager for Akkoma the docs should reflect probably that.
The Soapbox installation guide explains how to use asdf quite well as an example: https://soapbox.pub/install/
no
Could you explain why this is getting completely dismissed without explanation?
I would personally be willing to add asdf instructions to the docs if backporting or lowering the version requirement is not an option.
the "backport" suggestion is mindbogglingly silly and should be embarrassing to even think of
we support the version as specified in the documentation, the tools to use the versions specified are listed in the docs
your issue suggests both lowering the requirement which would cause a regression, or doing something idiotic, neither of which are particularly good ideas
The docs do list asdf, but it doesn't give instructions on how to use it.
On the Debian or Ubuntu page for example the docs still suggest to install Elixir using the APT package manager, which is currently impossible. This will result in unnecessary hardship that could prevent some users from installing or updating Akkoma in the first place.
I personally think it is not a good idea to make the minimum required version a version that is not available in most repositories, but you're right it might be "idiotic" to reduce the minimum version at the current point in time and cause regression.
Then please consider this post a suggestion to least think about availability next time before moving the Akkoma to a new Elixir version maybe.
Documentation doesn't really tell anything about
asdf
, and if I didn't know about it beforehand, it would be a complex quest to understand how it works too.It's unfortunate that latest Elixir can't be installed from repositories, so
asdf
should be in the docs instead. And it's not like we use outdated operating systems, both Debian Stable and Ubuntu LTS doesn't package latest Elixir, and Elixir Solutions repository simply ignores these Debian/Ubuntu releases.For myself, I ended up installing
asdf
to a user Akkoma runs from, which is documented inasdf
docs. The only problem was modifying systemd service to directly callasdf
wrappers, but it's easy, just replaceEnvironment
andExecStart
: