We now got the first arm64 Debian users that are asking for a repo. The pip(x)-solution does work for them at the moment but a repo solution is obviously better :).
Can we help with anything to pull this rabbit out of the hat?
We now got the first arm64 Debian users that are asking for a repo. The pip(x)-solution does work for them at the moment but a repo solution is obviously better :).
Can we help with anything to pull this rabbit out of the hat?
Hi, I can try to support this. I will leave this open as a reminder, as I might not get to it immediately. Possibly on the next release
I did some work recently on our Debian/Ubuntu package builder so that it can now also build backports of the Go compiler for arm64 and put those packages in the same repository as the amd64 packages. This makes things a lot easier, both for the server and client.
The Go arm64 "backports" are there now and can be used by the targets in nbuilder.deb
See: https://codeberg.org/eduVPN/nbuilder.deb/src/branch/main/GO.md
No due date set.
No dependencies set.
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?