All the conflicts are not needed, are the variations that need to provide and conflicts gogs
Search Criteria
Package Details: gogs 1:0.12.7-1
Package Actions
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: | Martchus |
Last Packager: | Martchus |
Votes: | 53 |
Popularity: | 0.000787 |
First Submitted: | 2014-05-12 08:56 (UTC) |
Last Updated: | 2022-05-05 10:14 (UTC) |
Dependencies (9)
- git (git-git, git-vfs, git-run-command-patch-git)
- pam (pam-minimal-git, pam-selinux)
- go (go-git, go-go2go-git, gccrs-go-git, go-beta, gcc-go-git, gcc-go) (make)
- mariadb (mysql55, mysql56, mysql57, mysql, mytop-git, percona-server) (optional) – MariaDB support
- memcached (memcached-git) (optional) – MemCached support
- openssh (openssh-hpn-git, openssh-git, openssh-gssapi, openssh-xdg-git, openssh-dotconfig, openssh-selinux, openssh-hpn-shim) (optional) – GIT over SSH support
- postgresql (pipelinedb, agensgraph-git, postgresql-1c, postgresql-9.5, postgresql-9.4, postgresql-src-beta, postgresql-9.6, postgresql-11, postgresql-10, postgresql13, postgresql-lts, postgresql-12, postgresql-src) (optional) – PostgreSQL support
- redis (redis-testing, redis-git, keydb) (optional) – Redis support
- sqlite (sqlite-replication, sqlite-minimal-git, sqlite-fts3-parenthesis, sqlite-fossil) (optional) – SQLite support
Required by (0)
Sources (3)
Latest Comments
FabioLolix commented on 2022-03-19 17:04 (UTC)
Martchus commented on 2022-01-18 11:39 (UTC) (edited on 2022-01-18 11:41 (UTC) by Martchus)
@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.)
respiranto commented on 2022-01-18 11:33 (UTC)
I get a checksum mismatch for the tarball:
caee12ab0dc2c2c137788d2fed0c55c5891e889948d6bbf04d5683b7160e01cf49419a5faf9a34798bed7a79314af08409f2e1f14150a3b660e528f0d8bd4e88
jrnewell commented on 2020-08-27 20:21 (UTC)
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.
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).
lb.laboon commented on 2018-12-14 04:20 (UTC)
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.
potatoattack commented on 2018-11-03 13:28 (UTC)
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.
onidaito commented on 2018-10-16 23:09 (UTC)
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 :)
Martchus commented on 2018-07-14 20:13 (UTC)
@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.
arshlinux commented on 2018-07-13 14:20 (UTC)
Just reporting this warning:
==> WARNING: Package contains reference to $srcdir
usr/bin/gogs
runical commented on 2018-04-01 19:15 (UTC)
@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 ;-)
Martchus commented on 2018-03-31 11:12 (UTC) (edited on 2018-03-31 11:14 (UTC) by Martchus)
@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 :-)
runical commented on 2018-03-31 10:54 (UTC) (edited on 2018-03-31 10:54 (UTC) by runical)
@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
Martchus commented on 2018-03-20 20:47 (UTC)
Ok, I'll do when updating anyways.
powerarch commented on 2018-03-20 20:37 (UTC)
This package sees to build just fine on aarch64. Maybe add it to the supported architectures?
Martchus commented on 2018-03-19 22:05 (UTC) (edited on 2018-03-19 22:14 (UTC) by Martchus)
I updated Gogs to use systemd-sysusers in accordance with the official packaging: https://www.archlinux.org/todo/switch-to-systemd-sysusers
This way the install script can be omitted. Hooks will take care of everything instead (even warning about systemctl daemon-reload
).
When I upgraded the package on my server, this did not change any existing user/group IDs. So the transition should not cause any trouble.
I also included a script gogs-backup
which calls gogs backup
using the environment variable and config parameter mentioned in the last comment. It must run as user gogs
.
Martchus commented on 2018-02-07 20:58 (UTC) (edited on 2018-02-07 20:59 (UTC) by Martchus)
@drBlaze I haven't tried to restore, but creating a backup is quite easy, eg.:
sudo su gogs
export GOGS_CUSTOM=/var/lib/gogs/custom # the magic line that lets your error go away
gogs backup --config /etc/gogs/app.ini --verbose --target /tmp
drBlaze commented on 2018-02-04 11:26 (UTC) (edited on 2018-02-04 11:27 (UTC) by drBlaze)
Has anyone tried to backup & restore? $ gogs backup --config=/etc/gogs/app.ini 2018/02/04 12:02:09 [ INFO] Backup root directory: /tmp/gogs-backup-840218384 2018/02/04 12:02:09 [ INFO] Packing backup files to: gogs-backup 20180204120209.zip 2018/02/04 12:02:09 [FATAL] Fail to include 'custom': open /usr/bin/custom: no such file or directory
Running "systemctl status" confirms Custom path: /usr/bin/custom
This can't be right, right?
davidovitch commented on 2017-12-26 17:15 (UTC)
I had to use an absolute path for the SQLite database file, while the default config setting comes as a relative path. I've added this to the Arch Linux wiki. My installation is running in an Arch linux LXC container, not sure if that makes any difference.
davidovitch commented on 2017-12-23 15:06 (UTC) (edited on 2017-12-23 15:07 (UTC) by davidovitch)
@Martchus: thanks! I've updated the Arch Wiki accordingly, maybe a more experienced Gogs user could review the changes I made? For example, I could only see changes taking effect after restarting Gogs (systemctl restart gogs
), is that really the case?
I've also tried to use a custom configuration file custom/conf/app.ini
(as suggested by the Gogs docs), but I couldn't get that to work using either /usr/share/gogs
or /var/lib/gogs
as root directory.
Martchus commented on 2017-12-22 20:19 (UTC) (edited on 2017-12-22 20:21 (UTC) by Martchus)
@davidovitch This first-time-configuration via the web UI conflicts with having the config under /etc/gogs
indeed. You can decide yourself whether you want to relax the permissions (temporarily) or just edit the config file directly. Note that Gogs only alters this file through the first-time-config. Any other settings are stored in the database.
davidovitch commented on 2017-12-22 20:03 (UTC)
I am a little confused regarding the location of the config file, when finishing off the installation at localhost:3000 (Install steps for first run time) I get:
Fail to save configuration: open /etc/gogs/app.ini.747273564.tmp: permission denied
Martchus commented on 2017-11-24 10:28 (UTC)
slashme commented on 2017-11-24 09:49 (UTC)
Martchus commented on 2017-11-05 18:15 (UTC) (edited on 2017-11-05 18:36 (UTC) by Martchus)
Martchus commented on 2017-10-12 10:11 (UTC)
yan12125 commented on 2017-10-12 09:47 (UTC)
Martchus commented on 2017-10-06 14:56 (UTC)
papush commented on 2017-10-05 20:55 (UTC)
Martchus commented on 2017-10-02 17:31 (UTC)
papush commented on 2017-10-02 16:50 (UTC)
Martchus commented on 2017-09-30 18:49 (UTC)
papush commented on 2017-09-30 14:45 (UTC)
Martchus commented on 2017-08-09 19:15 (UTC)
geekinthesticks commented on 2017-08-09 18:14 (UTC)
Martchus commented on 2017-07-25 18:08 (UTC)
geekinthesticks commented on 2017-07-23 17:45 (UTC)
julian commented on 2017-06-29 12:08 (UTC)
Martchus commented on 2017-06-27 11:57 (UTC)
julian commented on 2017-06-27 09:33 (UTC) (edited on 2017-06-27 09:39 (UTC) by julian)
Martchus commented on 2017-06-23 21:32 (UTC) (edited on 2017-06-23 21:34 (UTC) by Martchus)
datawolf commented on 2017-06-23 21:00 (UTC)
colinc904 commented on 2017-06-17 07:33 (UTC)
Martchus commented on 2017-06-12 22:24 (UTC) (edited on 2020-08-24 14:22 (UTC) by Martchus)
- 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 usergit
. So that has to be changed in the config and for the ownership of/var/lib/gitea
.~~~ The official package now uses the usergitea
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.)
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 toEXTERNAL_URL
. Please read the official changelog before reporting any issues: https://github.com/gogs/gogs/releases/tag/v0.12.0Further notes from myself:
ROOT_URL
did not work at all for me anymore. So it is apparently not just deprecated (as the changelog states).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
gitea
and the official package the usergit
. So that has to be changed in the config and for the ownership of/var/lib/gitea
.~~~ The official package now uses the usergitea
similar to my initial packaging was done.