New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't start Gitea if it's not built with the "bindata" flag #11756
Comments
There is a downstream issue with the arch package where the built files are not put in a location that Gitea expects. You'll need to open a ticket with the package maintainer to have package updated so that the expected paths are used. As this is out of our control I will close this issue now, however if the arch package maintainers have questions we are available to answer any questions in our chat discord.gg/gitea |
If anyone is facing the same problem, this is the maintainer answer:
|
Interesting how bindata is broken? |
@lafriks I don't know, but you can reach him out at |
It's really recommended to use Gitea in release mode with bindata. Without is meant for development purposes |
@lafriks So I’m trying to upgrade Arch package to 1.12.2, but In previous versions (starting from 1.11.3 IIRC)
What we do (from a clone of git tag 1.12.2):
The failure is in the last step. |
P.S.: Tell me if you prefer that I open a new issue. ;) |
|
|
What’s up here then? Should I open a new issue for better visibility? |
@ArchangeGabriel this is very odd. What happens if you change your script to use |
Exactly the same thing, sorry if I wasn’t clear that by “Adding |
OK sorry about that. How about switching the order of the TAGS ... etc around to after the make? |
I’ve tried this:
But same issue. I’m currently having a look at the Makefile, seems the handling of bindata changed at least once recently (11f7fc5). |
It's really weird and I don't quite understand what the problem is. Is it possible the EXTRA_GOFLAGS are conflicting with the bindata - in particular I wonder if there is an issue with modcacherw or mod=readonly? |
OK, found it. It’s a concurrency issue: bindata needs the frontend to be already built, but make is building the frontend and backend on parallel. Using |
I suspect it's not that the frontend needs to be built but that generate has been run first. |
Indeed, running |
If we add I think adding:
makes this work. |
OK, so we fixed the first issue, but there is another one remaining, which was the initial reason this ticket was opened. Here is a gitea 1.12.3 deployed with the Arch package, built with bindata: https://code.astrophysics.eu/ This is why bindata was disabled in the first place… I will revert to that for now, so that the update can be published while we sort that out. |
Oh damn I think you're right we do need the frontend built before bindata can run! |
Indeed, so this:
got it working finally! |
See go-gitea/gitea#11756 for changes git-svn-id: file:///srv/repos/svn-community/svn@665847 9fca08f4-af9d-4005-b8df-a31f2cc04f65
See go-gitea/gitea#11756 for changes git-svn-id: file:///srv/repos/svn-community/svn@665847 9fca08f4-af9d-4005-b8df-a31f2cc04f65
Still have that problem on latest v1.12 branch (1.12.4), with FreeBSD 12.1/amd64, Go 1.14.7, Node 14.4.0, npm 6.12.1。
No problem on master branch(1.13.0) |
don't use make -jx - our build is not parallelisable. have you tried:
|
Gitea version (or commit ref):
Gitea version 1.11.4 built with GNU Make 4.3, go1.13.8 : sqlite, pam
Git version:
git 2.27.0-1
Operating system:
Linux 5.4.42-1-ARCH #1 SMP PREEMPT Thu May 26 01:48:56 UTC 2020 armv7l GNU/Linux
Database (use [x]):
Can you reproduce the bug at https://try.gitea.io:
Description
I install
gitea
from the community repo of Arch Linux ARM, which is built with the same PKGBUILD used in Arch Linux.Starting from version 1.11.4-1 they removed
bindata
from the build flags, and if I startgitea
after an update I encounter the following error:journalctl -u gitea
If I downgrade using the latest version built with
bindata
everything works as expected.Is there a way to solve this issue without that flag? Or I need to ask the package maintainer to re-add it?
The text was updated successfully, but these errors were encountered: