Arch Linux User Repository

The release 0.12.0 will change various configuration variables, e.g. ROOT_URL is changed to EXTERNAL_URL. Please read the official changelog before reporting any issues: https://github.com/gogs/gogs/releases/tag/v0.12.0

Further notes from myself:

• ROOT_URL did not work at all for me anymore. So it is apparently not just deprecated (as the changelog states).
• The changelog mentions no alternative to STATIC_ROOT_PATH. It looks like this directory is simply not required at all anymore because files are built into the executable. Overrides should be possible by placing files into the working directory (should be /var/lib/gogs/public with the default config provided by this package; haven't tested yet).

• All my packages are managed at GitHub where you can also contribute directly: https://github.com/Martchus/PKGBUILDs
• Patches are managed under: https://github.com/martchus/gogs
• There also exists a binary repository: https://martchus.no-ip.biz/repo/arch/ownstuff

Important note: You likely want to use the official Gitea package instead.

Gitea - a fork of Gogs - has been added to the official repositories: https://www.archlinux.org/packages/community/x86_64/gitea

That means for Arch Linux the decision has been made to support Gitea rather than Gogs. Hence I suggest everyone to use Gitea instead of Gogs for new installations. I've been testing Gitea for a while myself now and it works well. So I'm also going to switch fully to Gitea myself.

Nevertheless I'll continue maintaining this package for a while now to support old installations. However, I'm not doing any fine-tuning for this package anymore.

Further notes

• ~~~If anybody was using the Gitea package from my PKGBUILDs repository: It is easy to migrate the official Gitea package because the packages are structured more or less the same. The only significant difference between the packages is that mine was using the user gitea and the official package the user git. So that has to be changed in the config and for the ownership of /var/lib/gitea.~~~ The official package now uses the user gitea similar to my initial packaging was done.
• It is also possible to install this Gogs package provided here and Gitea at the same time (of course operating on different databases!). That makes it easy to try out Gitea without breaking the existing Gogs installation. Repos can be copied quite easily using my gogs2gitea script. (I'm afraid migrating isn't possible anymore without installing an old Gitea version first.)

Can you add the new go option '-modcacherw' so the build module cache folders and files are set with default permission instead of read-only. Currently, using yay, I get a lot of "permission denied" errors when doing a clean build on this package.

The release 0.12.0 will change various configuration variables, e.g. ROOT_URL is changed to EXTERNAL_URL. Please read the official changelog before reporting any issues: https://github.com/gogs/gogs/releases/tag/v0.12.0

Further notes from myself:

• ROOT_URL did not work at all for me anymore. So it is apparently not just deprecated (as the changelog states).
• The changelog mentions no alternative to STATIC_ROOT_PATH. It looks like this directory is simply not required at all anymore because files are built into the executable. Overrides should be possible by placing files into the working directory (should be /var/lib/gogs/public with the default config provided by this package; haven't tested yet).

One small thing I noticed is that the mode of /etc/gogs in this package does not match the mode specified in /usr/lib/tmpfiles.d/gogs.conf (/etc/gogs is 0755 in the package, but the gogs.conf file specifies 0775).

Not a huge deal, but would be nice if they were made to be consistent with each other.

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.

Had an issue where gogs would not write to the /etc/gogs/app.ini The installer kept on complaining that this was a "read only file system" despite changing the directory to various users, gog included. I also changed to mode 777 at one point. Still no luck. Gogs-git seems to work first time :)

@arshlinux I am aware of this warning. Not sure how to remove the reference from the binary, though. But it doesn't seem to cause any problems so I don't care much.

Just reporting this warning:

==> WARNING: Package contains reference to $srcdir
usr/bin/gogs

@Martchus: Thanks for the explanation, I guess that is annoying to deal with. The reason I add this is in an attempt to educate the people using the AUR about these kinds of things (which should absolutely be known by those users).

You won't hear me complain about your including the deps btw. Just about the people who asked you to include those deps ;-)

@runical I know that those dependencies are actually not required. See my comment on his PR. However, that's not the first complaint of that kind I'm receiving so I just thought let's finally add it. It can not hurt and might silence those complaints. If I now get more complaints about those makedepends being present, I maybe drop them again :-)

@Martchus, @k3a

It seems the comment has already been removed, so I hope k3a has found out that they were incorrect themselves. However, it seems Martchus has acted on it nevertheless.

GCC and patch do not have to be listed as makedepends as they are in the base-devel group. This group in assumed installed for anyone who builds packages, as can be seen on the wiki [0,1]. This does not mean that adding them is wrong per se, but they do not have to be added explicitly for any package on the AUR. Please refrain from asking anyone to add these as makedepends and just install base-devel.

[0] https://wiki.archlinux.org/index.php/Arch_User_Repository#Prerequisites

[1] https://wiki.archlinux.org/index.php/Makepkg