A painless self-hosted Git service.

Edit Package gitea
https://gitea.io/

Gitea is a community managed fork of Gogs, lightweight code hosting solution written in Go and published under the MIT license.

Refresh
Refresh
Source Files
Comments 6

Sauer's avatar

I spotted two problems with this package:

  • Templates do not work. 'journalctl -eu gitea' says 'permission denied' Solution: The apparmor profile needs to be updated to allow read access to /etc/gitea/templates/**.

  • The commit search functionality in /[owner]/[repo]/[commits]/branch/[branch] does not work

The user sees a 500 Server error

'journalctl -eu gitea' reports "Couldn't JIT the PCRE2 pattern x got -48"

The underlying problem is this:

  - gitea uses the command 'git log --grep=keyword'

  - git uses the PCRE2 library to grep

  - PCRE2 needs memory with write and execute permission

  - systemd denies that because of the setting MemoryDenyWriteExecute=yes in gitea.service

Solution1:

Now i know that it is not great to allow that for such a wide open application like gitea,
but i don't know any better way right now than to set MemoryDenyWriteExecute=no in gitea.service.

    If anyone has a better way to do this (allow w+x memory for git only) please reply.

Solution2:

Git has a compile time flag to disable LibPCRE2. One could use a differently compiled git and it should work, albeit slow(er).

Eric Schirra's avatar

For apparmor please contact michael@stroeder.com


Eric Schirra's avatar

Yes. Appamor or systemd hardening is broken since some weeks. Can you test point C: in README.SUSE? Are your errors gone now?


Dirk Mueller's avatar

thanks for the reports, I will take a look


Georg Pfuetzenreuter's avatar

Hi,

I am trying to build this package with the "bindata" tag which is recommended by Gitea https://docs.gitea.com/next/installation/install-from-source#build and will allow assets to be bundled instead of being fetched remotely. However I think to be facing an issue with the vendored modules:

[  134s] # code.gitea.io/gitea/modules/migration
[  134s] modules/migration/schemas_static.go:14:9: undefined: Assets

Do you happen to know about this?

There is an issue on GitHub but it seems we already use the suggested build process according to the linked sample spec file: https://github.com/go-gitea/gitea/issues/7997


Eric Schirra's avatar

The ticket was from me

Upstream doesn't really understand some things about epm and buiilserver. At least that's my impression. Help does not come either. Besides, they are changing things. Sometimes all dependencies are in there. Sometimes a few are missing.

And why do you want to change my build process?

It works without errors.

Among other things, because I do it the way I do it.

openSUSE Build Service is sponsored by