Package Details: gogs 1:0.13.0-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
Submitter: kureikain
Maintainer: None
Last Packager: dcelasun
Votes: 50
Popularity: 0.000000
First Submitted: 2014-05-12 08:56 (UTC)
Last Updated: 2023-08-10 14:22 (UTC)

Dependencies (9)

Required by (0)

Sources (3)

Pinned Comments

Martchus commented on 2020-08-24 14:06 (UTC)

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

Martchus commented on 2017-06-12 22:24 (UTC) (edited on 2020-08-24 14:22 (UTC) by Martchus)

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

Latest Comments

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 .. 18 Next › Last »

Mic92 commented on 2016-08-03 15:24 (UTC) (edited on 2016-08-03 15:26 (UTC) by Mic92)

Usually I like arch's default to not automatically restart services after upgrade. But in this case Gogs will not find it's old assets, so I added this pacman hook: #/etc/pacman.d/hooks/gogs.hook [Trigger] Type = File Operation = Upgrade Target = usr/share/gogs/gogs [Action] Description = Restart gogs... When = PostTransaction Exec = /usr/bin/systemctl try-restart gogs.service Maybe this could be part of the wiki or part of the package (maybe optionally enabled via symlink). I find it quite convenient.

CountMurphy commented on 2016-07-22 18:50 (UTC)

checksums fail: ==> Validating source files with sha512sums... gogs.service.patch ... Passed app.ini.patch ... Passed gogs ... FAILED ==> ERROR: One or more files did not pass the validity check!

fanningert commented on 2016-07-21 08:50 (UTC)

@jakschu Currently the install process with apacman or yaourt, is working on my laptop. Looks like it is a github or glide problem. My created issue is open and I will search for the problem. But currently I don't found a good log-option in glide with the install parameter.

jakschu commented on 2016-07-20 14:51 (UTC)

Thanks for opening the issue on Github. I just tried another 10x and updated the Gist. The errors seem to occur somehow randomly. ldap seems only to work part time.

fanningert commented on 2016-07-19 21:03 (UTC)

@jakschu I opened a issue on the GitHub page of Gogs. https://github.com/gogits/gogs/issues/3284 I think the problem is by Glide. (I add a link to a glide issue in the gogs issue) But you can retry, the compile process. By me, the second compile get me a working package. (sorry for this workaround)

jakschu commented on 2016-07-19 20:43 (UTC)

I can't build it anymore. https://gist.github.com/jakschu/f66b0b5863d06cf6d61577cd94bc4e41

geekinthesticks commented on 2016-07-08 14:05 (UTC)

@fanningert Yes, I did install base-devel. I'll try again and paste the full trace. Interestingly I get exactly the same error trying to install on Ubuntu 16.04.

fanningert commented on 2016-07-07 18:53 (UTC)

@geekinthesticks: I think the error is some lines up. But one question. Did you installed base-devel package?

geekinthesticks commented on 2016-07-03 11:03 (UTC)

I am getting the following error, but ti's not clear what is causing it: cd /home/ian/AUR/gogs/src/build/src/github.com/gogits/gogs /home/ian/AUR/gogs/src/build/go/pkg/tool/linux_amd64/compile -o $WORK/github.com/gogits/gogs.a -trimpath $WORK -p main -complete -buildid 14015d61327f125aaf39de90793f540dd83defc2 -importmap github.com/codegangsta/cli=github.com/gogits/gogs/vendor/github.com/codegangsta/cli -D _/home/ian/AUR/gogs/src/build/src/github.com/gogits/gogs -I $WORK -I /home/ian/AUR/gogs/src/build/pkg/linux_amd64 -pack ./gogs.go cd . /home/ian/AUR/gogs/src/build/go/pkg/tool/linux_amd64/link -o $WORK/github.com/gogits/gogs/_obj/exe/a.out -L $WORK -L /home/ian/AUR/gogs/src/build/pkg/linux_amd64 -extld=gcc -buildmode=exe -buildid=14015d61327f125aaf39de90793f540dd83defc2 $WORK/github.com/gogits/gogs.a go build github.com/gogits/gogs: /home/ian/AUR/gogs/src/build/go/pkg/tool/linux_amd64/link: signal: killed ==> ERROR: A failure occurred in build(). Aborting...

runical commented on 2016-06-03 08:40 (UTC)

@fanningert: Thanks!