Upgrading to Gitea 1.13.4 didn’t go as planned and it failed to compile the go-sqlite3 module with my previous setup. While crossbuilding, the CGO parameter is automatically disabled (i.e. compiling is done with CGO_ENABLED=0) but the go-sqlite3 module won’t build anymore if this option is not set (probably require some optimisation in C and a pure Go implementation won’t fit anymore).
I use Docker quite a lot as it allows me to install, test, remove libraries or components without any risk to break my main system. VM is another option but even if a linux install is now just a few clicks in virt-manager GUI, it takes time and I don’t need the full isolation provided for this use-case.
The Nvidia driver currently available in buster-backport (450.80) seems to have issues with the 5.9 kernel, resulting in an unavailable uvm module.
[ 8883.526038] nvidia_uvm: module uses symbols from proprietary module nvidia, inheriting taint.
A bit early for christmas presents, but I got myself a new machine (AMD Ryzen 3900X / 32G / RTX2060 Super, by the way Ryzen CPUs are real monsters). Now, let’s try to make use of this.
Instead of building the Gitea binary on a Raspberry PI, we can speed up things a bit by crossbuilding from some other computer with more punch. Recent version of Gitea will need nodejs/npm to be available at build time, so we’ll install this too.
I’m hosting my projects code on a Gitea instance running on a Raspberry PI. Thing is, the last Raspbian update broke the gitea binary: probably some change in the kernel or libc.