Package Details: gogs 1:0.11.91-1

Git Clone URL: https://aur.archlinux.org/gogs.git (read-only, click to copy)
Package Base: gogs
Description: Self Hosted Git Service written in Go
Upstream URL: https://gogs.io
Keywords: git go gogs
Licenses: MIT
Conflicts: gogs-bin, gogs-dev-git, gogs-git
Submitter: kureikain
Maintainer: Martchus
Last Packager: Martchus
Votes: 54
Popularity: 0.000501
First Submitted: 2014-05-12 08:56
Last Updated: 2020-01-21 14:09

Pinned Comments

Martchus commented on 2017-06-12 22:24

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.
  • 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.)
Previous "sticky" note

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 ... Next › Last »

Martchus commented on 2017-07-25 18:08

@geekinthesticks Hard to tell without the actual error message.

geekinthesticks commented on 2017-07-23 17:45

I am getting an error when trying to build. Error seems to be ner the top of the following extract:

/text/encoding/charmap=github.com/gogits/gogs/vendor/golang.org/x/text/encoding/charmap -importmap golang.org/x/text/encoding/htmlindex=github.com/gogits/gogs/vendor/golang.org/x/text/encoding/htmlindex -importmap golang.org/x/text/transform=github.com/gogits/gogs/vendor/golang.org/x/text/transform -D _/home/ian/AUR/gogs/src/build/src/github.com/gogits/gogs/vendor/golang.org/x/net/html/charset -I $WORK -I /home/ian/AUR/gogs/src/build/pkg/linux_amd64 -pack ./charset.go
mkdir -p $WORK/github.com/gogits/gogs/vendor/github.com/Unknwon/paginater/_obj/
cd /home/ian/AUR/gogs/src/build/src/github.com/gogits/gogs/vendor/github.com/Unknwon/paginater
/home/ian/AUR/gogs/src/build/go/pkg/tool/linux_amd64/compile -o $WORK/github.com/gogits/gogs/vendor/github.com/Unknwon/paginater.a -trimpath $WORK -p github.com/gogits/gogs/vendor/github.com/Unknwon/paginater -complete -buildid 129795f9401284b6370ddf00284a8072eab56a02 -D _/home/ian/AUR/gogs/src/build/src/github.com/gogits/gogs/vendor/github.com/Unknwon/paginater -I $WORK -pack ./paginater.go
mkdir -p $WORK/github.com/gogits/gogs/vendor/gopkg.in/editorconfig/editorconfig-core-go.v1/_obj/
mkdir -p $WORK/github.com/gogits/gogs/vendor/gopkg.in/editorconfig/
cd /home/ian/AUR/gogs/src/build/src/github.com/gogits/gogs/vendor/gopkg.in/editorconfig/editorconfig-core-go.v1
/home/ian/AUR/gogs/src/build/go/pkg/tool/linux_amd64/compile -o $WORK/github.com/gogits/gogs/vendor/gopkg.in/editorconfig/editorconfig-core-go.v1.a -trimpath $WORK -p github.com/gogits/gogs/vendor/gopkg.in/editorconfig/editorconfig-core-go.v1 -complete -buildid 7d4e644a3a9877e3061a4ad98e7f1039e3fb2236 -importmap gopkg.in/ini.v1=github.com/gogits/gogs/vendor/gopkg.in/ini.v1 -D _/home/ian/AUR/gogs/src/build/src/github.com/gogits/gogs/vendor/gopkg.in/editorconfig/editorconfig-core-go.v1 -I $WORK -I /home/ian/AUR/gogs/src/build/pkg/linux_amd64 -pack ./editorconfig.go
mkdir -p $WORK/github.com/gogits/gogs/vendor/github.com/gogits/cron/_obj/
cd /home/ian/AUR/gogs/src/build/src/github.com/gogits/gogs/vendor/github.com/gogits/cron
/home/ian/AUR/gogs/src/build/go/pkg/tool/linux_amd64/compile -o $WORK/github.com/gogits/gogs/vendor/github.com/gogits/cron.a -trimpath $WORK -p github.com/gogits/gogs/vendor/github.com/gogits/cron -complete -buildid a8b187f01712f4544fb37dd71e6746b085ac7800 -D _/home/ian/AUR/gogs/src/build/src/github.com/gogits/gogs/vendor/github.com/gogits/cron -I $WORK -pack ./constantdelay.go ./cron.go ./doc.go ./parser.go ./spec.go
mkdir -p $WORK/github.com/gogits/gogs/vendor/github.com/urfave/cli/_obj/
mkdir -p $WORK/github.com/gogits/gogs/vendor/github.com/urfave/
cd /home/ian/AUR/gogs/src/build/src/github.com/gogits/gogs/vendor/github.com/urfave/cli
/home/ian/AUR/gogs/src/build/go/pkg/tool/linux_amd64/compile -o $WORK/github.com/gogits/gogs/vendor/github.com/urfave/cli.a -trimpath $WORK -p github.com/gogits/gogs/vendor/github.com/urfave/cli -complete -buildid 0090ed328af0fe71d365ca1c02e15703c5517340 -D _/home/ian/AUR/gogs/src/build/src/github.com/gogits/gogs/vendor/github.com/urfave/cli -I $WORK -pack ./app.go ./category.go ./cli.go ./command.go ./context.go ./errors.go ./flag.go ./flag_generated.go ./funcs.go ./help.go
==> ERROR: A failure occurred in build().

julian commented on 2017-06-29 12:08

@Martchus Yes, creating the directory allowed gogs to start. Apart of this I had to fix paths to app.ini and gogs binary in the /home/gogs/.ssh/authorized_keys, to make pushing work again.

Martchus commented on 2017-06-27 11:57

@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`.

julian commented on 2017-06-27 09:33

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

Martchus commented on 2017-06-23 21:32

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.

datawolf commented on 2017-06-23 21:00

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.

colinc904 commented on 2017-06-17 07:33

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

Martchus commented on 2017-06-12 22:24

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.
  • 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.)
Previous "sticky" note

Martchus commented on 2017-05-15 12:39

@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`.