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.)

@julian Yes, `/var/lib/gogs` is the working directory. So adding this directory fixed the issue? I guess the package should contain the (empty) directory `/var/lib/gogs` like mariadb contains `/var/lib/mysql`.

After updating from 0.10.18 to 0.11.19 the systemd service does not start any more: gogs.service: Failed at step CHROOT spawning /usr/bin/gogs: No such file or directory /usr/bin/gogs clearly exists and is runnable as user gogs. Any thoughts on this? EDIT: /var/lib/gogs needs to be existant for recent versions of this packages, as it is used as working directory

You can work around this issue by executing `chown gogs:gogs -R /etc/gogs`. Maybe I should fix this in the package. And yes, you have to modify `/etc/gogs/app.ini` directly. The other file is just to be able to restore the defaults more easily. Hence `/etc/gogs/app.ini` is in the backup array of the PKGBUILD. I guess upstream prefers having a custom config file containing only settings to be modified and hence include the 'DO NOT MODIFY' warning. I decided against that because I like to see all available options in the file, even if I mostly stick to the default value. Additionally, this approach prevents changed behavior in case the default changes. Instead, such changes are detected by pacman creating .pacnew/.pacsave file and it is easy to get a diff.

On the first run of a fresh install, it brings me to the Install page, but I cannot leave this page. When I click the install button at the bottom, it gives me the error, "Fail to save configuration: open /etc/gogs/app.ini.855127131.tmp: permission denied". I just installed and started using the provided gogs.service. How can I get past this? Also, do I just modify /etc/gogs/app.ini directly, or do I need to make a copy? I see that the pkgbuild also puts an app.ini file at /usr/share/gogs/conf/app.ini. The top of both of them says not to modify. I'm not sure which one I should be using.

I could not build this package as it stands, because the variable $GOPATH was not defined in the build() section, so the cd command failed. Copying the export commands for GOROOT and GOPATH from the prepare() section into the build() section fixes the problem for me. (this is using the 'pacaur' command, I don't know if that is relevant...)

• 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.)

@xsmile: Thanks, I'll add the flags when updating anyways. The Wiki pages should be updated, too: https://wiki.archlinux.org/index.php/Gogs But maybe it doesn't make much sense to put absolute paths there anymore because other Gogs packages (eg. gogs-git, variants of this, ...) might use other locations. It should be easy to find out the absolute paths by just using `pacman -Ql gogs`.

@Martchus: That is fore sure :-) The change is in line 62. Using these ldflags strips debugging information from the binary.

@xsmile How did you achieve the smaller binary size (not sure which modification of your PKGBUILD is relevant)? I think it is better not change the paths here again because these changes are likely very annoying for the users.

I have been playing around with different gogs configurations recently and would like to share my package that includes some (in my opinion) useful changes I gathered from the other packages or found out myself: - working directory is set using an environment variable - symlinks instead of static paths in app.ini - thus no default app.ini, gogs generates it during the setup routine - binary should be ~10MB smaller https://www.sendspace.com/file/zxe93v