Package Details: gitea-git v1.19.0_dev_286_g477a1cc40e-1

Git Clone URL: https://aur.archlinux.org/gitea-git.git (read-only, click to copy)
Package Base: gitea-git
Description: Painless self-hosted Git service. Community managed fork of Gogs.
Upstream URL: https://gitea.io/
Keywords: git
Licenses: MIT
Conflicts: gitea
Provides: gitea
Submitter: francoism90
Maintainer: kageru
Last Packager: kageru
Votes: 7
Popularity: 0.000000
First Submitted: 2016-11-15 09:57 (UTC)
Last Updated: 2023-01-11 19:12 (UTC)

Dependencies (10)

Required by (2)

Sources (5)

Pinned Comments

Latest Comments

1 2 3 4 5 6 7 Next › Last »

hopeseekr commented on 2025-01-21 23:43 (UTC)

The only way I got this to work with a separate repository path was:

  1. edit /usr/lib/systemd/system/gitea.service
  2. edit and change to ReadWritePaths=/etc/gitea/app.ini /storage/gitea
  3. sudo systemctl reload-daemon; sudo systemctl restart gitea
  4. sudo chattr +i /usr/lib/systemd/system/gitea.service

Then it would work normally.

I tried the systemctl edit gitea, but it did no good.

I set the immutable flag on the systemd file so while it explodes during gitea upgrades, at least it won't silently change the file and silently break gitea.

kageru commented on 2023-01-11 19:13 (UTC)

Disabled lto, thanks for the hint.

HLFH commented on 2023-01-02 12:00 (UTC) (edited on 2023-01-02 12:02 (UTC) by HLFH)

Hi @kageru.

Could you disable LTO in the PKGBUILD as go does not support it ?

backup=('etc/gitea/app.ini')
options=(!lto)
conflicts=('gitea')

The package breaks when LTO is enabled within /etc/makepkg.conf. So, the options=(!lto) must be added to disable it for the package until go supports it.

Thaodan commented on 2022-09-01 20:21 (UTC)

Shouldn't the optdepends also be makedepends so they are found during build?

tip commented on 2022-05-08 15:23 (UTC)

First step after install gitea:

cp /etc/gitea/app.example.ini /etc/gitea/app.ini
chown gitea:gitea /etc/gitea/app.ini
systemctl restart gitea

After this steps I am success save configuration in /etc/gitea/app.ini

kageru commented on 2021-10-21 21:03 (UTC)

Both this package and gitea from the repositories include a systemd unit file in /usr/lib/systemd/system/gitea.service which specifies ProtectSystem=strict. You can make changes via systemctl edit gitea (editing the .service file directly will also work, but it will be overwritten on each package update).

malibu commented on 2021-10-10 20:21 (UTC)

I am trying to install both gogs-git and gitea-git but they are giving the same issue. Upon pressing the install button, the console reports the following error: Failed to save configuration: open /etc/gogs/app.ini: read-only file system

I have been unable to find any solution. There seems to be a comment from someone trying to help in gogs: "Being unable to write to /etc/gogs/app.ini during the installer even though permissions are correct is caused by ProtectSystem=full in gogs.service. Changing this setting to ProtectSystem=true mounts /etc rw fixing this issue." But I have no idea where I need to change that, since there is no gitea or gogs service file on my system. Can anyone help? thanks.

ZFSuss commented on 2021-07-02 02:31 (UTC)

The community package is way out of date, so I decided to make the transition to docker. As this package shares the same paths I hope someone else finds the following helpful if they're migrating away from these packages:

$ find "data/git/repositories/" -name "gitea" -exec sed -i "s/\/usr\/bin\/gitea/\/app\/gitea\/gitea/g" '{}' \;
$ find "data/git/repositories/" -name "gitea" -exec sed -i "s/\/etc\/gitea\/app.ini/\/data\/gitea\/conf\/app.ini/g" '{}' \;

kageru commented on 2020-12-22 15:43 (UTC)

Got it. I reenabled bindata and also changed most other things that have diverged from the repo package. The only meaningful difference now is this package setting GOCACHE for users with read-only home directories.

Thanks again.

Archange commented on 2020-12-22 15:06 (UTC)

Yes indeed, because the parallel compilation implied that at some point it tried to embed (which is the point of bindata) assets that were not yet fully built. So we ended with partially built assets in the binary, and hence an half-working website.

Forcing serial builds avoid this issue, because assets are built before being embedded.

1 2 3 4 5 6 7 Next › Last »