Package Details: gitea-git v1.13.0_dev_234_gd9aa007a9-1

Git Clone URL: https://aur.archlinux.org/gitea-git.git (read-only, click to copy)
Package Base: gitea-git
Description: Painless self-hosted Git service. Community managed fork of Gogs.
Upstream URL: https://gitea.io/
Keywords: git
Licenses: MIT
Conflicts: gitea
Provides: gitea
Submitter: francoism90
Maintainer: kageru
Last Packager: kageru
Votes: 6
Popularity: 0.005701
First Submitted: 2016-11-15 09:57
Last Updated: 2020-06-23 08:38

Dependencies (10)

Required by (0)

Sources (5)

Latest Comments

1 2 3 4 Next › Last »

WSDMatty commented on 2020-06-08 04:19

Cannot build package. I'm not sure what's wrong....

http://codepad.org/N92ySkac

Output from makepkg -si

tinywrkb commented on 2020-02-27 13:17

With the latest Go release there's no need for the workaround for issue 33326 so it can be dropped for the PKGBUILD.

  # Workaround for https://github.com/golang/go/issues/33326
  export GOPATH="${srcdir}/gopath"

Archange commented on 2020-01-11 16:04

Indeed, the default path is now specified at build time (code.gitea.io/gitea/modules/setting.AppWorkPath=/var/lib/gitea).

kageru commented on 2020-01-11 14:47

I updated to PKGBUILD, and 1.12 builds fine on my end now. I also replaced the ldflags patch with the fix from the repo package as suggested by Archange.

Because of https://github.com/go-gitea/gitea/issues/6203, npm/nodejs is now a makedep.

1.12 seems to have changed some behavior when not using the default data path (/var/lib/gitea), at least it did for me. I added a notice to the install script.

Archange commented on 2019-12-04 10:48

They are other changes you could do in order to simplify the PKGBUILD, just have a look at the current repo one: https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/gitea

tinywrkb commented on 2019-11-28 23:38

Great! Thanks.

kageru commented on 2019-11-28 18:59

Thank you. I updated the package.

tinywrkb commented on 2019-11-25 20:22

The package has two issues:

  • On the patch directives it points to the start folder which is wrong because everything in the source array is copied to $srcdir and it also breaks if the user set makepkg's BUILDDIR environment var.

  • go mod init will fail if it cannot create pkg/mod/cache/lock in GOPATH. I noticed this because my ~ is immutable. So GOPATH var is required to be set to $srcdir/gopath. This looks like a bug in Go which was solved recently so it should be fixed in the next release though I still added the workaround.

diff --git a/PKGBUILD b/PKGBUILD
index 28c2a81..813f9ae 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -9,7 +9,7 @@

 _pkgname='gitea'
 pkgname=gitea-git
-pkgver=v1.11.0_dev_43_g05e437f8f
+pkgver=v1.11.0_dev_330_gf5bd0884d
 pkgrel=1
 pkgdesc='Painless self-hosted Git service. Community managed fork of Gogs.'
 arch=('x86_64' 'i686' 'arm' 'armv6h' 'armv7h' 'aarch64')
@@ -50,11 +50,12 @@ pkgver() {
 prepare() {
   cd ${srcdir}/${_pkgname}
   # Change default repos path for ArchLinux
-  patch -Np1 -i ../../gitea-arch-defaults.patch
+  patch -Np1 -i ../gitea-arch-defaults.patch
   # Fix LDFLAGS not being passed correctly
-  patch -Np1 -i ../../gitea-ldflags.patch
+  patch -Np1 -i ../gitea-ldflags.patch

   # Make sure we rebuild the mod file from Gopkg.toml to pick up any changes.
+  export GOPATH="${srcdir}/gopath"
   rm -f go.mod
   go mod init || true
   GOCACHE="${srcdir}/cache" go mod download

SamWhited commented on 2019-02-01 14:12

Hi all, I'm no longer using Gitea for any projects, so I am going to disown this package so that someone who's actually using it and will see when problems crop up can maintain it.

SamWhited commented on 2018-12-23 13:31

oops, you're quite right. Thanks!