Bug 247381
| Summary: | www/gitea: fails to start due to missing locale files | ||
|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Vincent Bentley <vince> |
| Component: | Individual Port(s) | Assignee: | Adam Weinberger <adamw> |
| Status: | Closed Feedback Timeout | ||
| Severity: | Affects Some People | CC: | adamw, fernape, stb |
| Priority: | --- | Keywords: | needs-patch |
| Version: | Latest | Flags: | fernape:
maintainer-feedback?
(stb) koobs: merge-quarterly? |
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
Vincent Bentley
2020-06-18 14:03:20 UTC
^Triage: notifying MAINTAINER Thanks for such detailed report! I have successfully built the gitea 1.11.6_1 port with the BINDATA option set using Poudriere. Building with BINDATA on fixes the missing locale problem. The gitea package in the FreeBSD repo is not built with BINDATA on as default. Unfortunately, after installing the freshly built package (with BINDATA) and setting gitea_enable="YES" in /etc/rc.conf it will not start as a service. However, when gitea is started from the command line it appears that gitea will create config in /usr/local/sbin. I must have started it as root at least once to do this. When su'd as git, the /usr/local/etc/gitea/conf directory and app.ini need to be writable for the git user for gitea to start. I am currently working through combinations of command line arguments and app.ini config to try to get gitea to start properly. Changing ownership of the following directory trees to git:git fixed the problem starting the gitea service: chown -R git:git /usr/local/etc/gitea chown -R git:git /var/db/gitea chown -R git:git /var/log/gitea The startup script /usr/local/etc/rc.d/gitea sets GITEA_WORK_DIR to /usr/local/share/gitea but this directory does not exist. I assume that it does not get created if BINDATA is set. It does not appear to cause any problems. Please take alook at the startup script in /usr/local/etc/rc.d/gitea. WThe way the Gitea project builds the binary, it is not possible to just run `gitea web`; you will need to set some command line options and environment variables to point gitea to where things live in FreeBSD (as opposed to the Docker-centric model Gitea seems to be preferring). If you're having trouble starting service, please check the syslog output for hints. If all else fails, running the start script like so might give an indication why it might be failing: sh -vx /usr/local/etc/rc.d/gitea start I would love to have a default configuration of the gitea binary that points at the right locations by default, but so far I haven't been successful in supplying the right options to the build. I'd be very happy to have somebody else figure that out! I've just built and tested the gitea port with the bindata option enabled, and it seems to be working just fine for me (12.1-RELEASE-p3). I'm not getting error messages, and the permissions for the directories all seem to be correct out of the box. Is this still an issue? I was not able to reproduce your observations. If you're still having a problem, please let me know. It's been a month since you asked for more feedback. Would you like me to close out this PR? Closing as submitter has disappeared, and maintainer cannot reproduce. |
