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

I've adopted this package and updated to 0.13.0

Before updating, see the release notes here and pay attention to the Removed section.

I won't be maintaining this long term, so I'm orphaning it right back.

@Martchus gitea is only a fork of gogs, although it got a lot more popularity as it was a lot more heavily developed.

But due to recent criticisms, gitea might not be peoples first choice considering they did some shady stuff. Although releasing a statement apologising people still dislike gitea, and might hop back to gogs.

The package should still remain up to date, I am just wondering if anyone here actually still uses it, or would like to see it updated.

Most people I would have thought would be moving to forgejo, which is a fork of gitea, which attempts to address the privacy and lack of trust which gitea has dug themselves into.

I personally have orphaned it as I'm not interested anymore. Gitea has won :-)

Considering Gogs is technically still maintained we can keep this package here for anybody who wants to follow-up where I left off. The pinned comment should be enough of a warning for newcomers to see that they likely want Gitea instead. If someone takes over I will remove references to my GitHub repositories.

Are people still interested in this package being updated?

On a side note: I really hope that this repo keeps being maintained because IMHO the scope is quite different from Gitea. More features, contributors and updates does not always mean better, and a slower growing, more minimal project has its own place.

@Martchus Thanks for the reply. I am not interested in switching to Gitea, but I also don't have any Go experience (or any experience with AUR package authoring). If I can figure this out with my limited capacities, I'll be glad to send over a patch.

Not sure when I'll have time to implement any changes. If you have a patch, I'll apply it (or disown the package so you can continue on your own). Also read the pinned comments; likely you want to use Gitea anyways.

It seems like the "custom" directory (where e.g. custom themes are kept) is set to /usr/bin/custom, which seems strange.

See https://github.com/gogs/gogs/discussions/7059

Is it possible to set the custom directory to one in /usr/share/gogs, or similar, and add it to the install package? Thanks.

All the conflicts are not needed, are the variations that need to provide and conflicts gogs

@respiranto No surprise as I've already noted a 2nd GitHub notification for the new release. It looks like the author changed the release afterwards. I haven't applied the change yet because I wanted to wait whether the 2nd release will actually be the last amendment.

I've also noticed that the new release broke my setup. There's no error message logged but stracing shows that it cannot connect to my MariaDB instance (and then silently exists). So I guess I'll have to figure out that as well.

Maybe it is time to abandon this one completely (in favor of Gitea). (See further notes in pinned comment.)