@kageru: Note that the repo package enabled bindata again after finding the root issue with assets.
Search Criteria
Package Details: gitea-git v1.19.0_dev_286_g477a1cc40e-1
Package Actions
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: | 7 |
Popularity: | 0.000000 |
First Submitted: | 2016-11-15 09:57 (UTC) |
Last Updated: | 2023-01-11 19:12 (UTC) |
Dependencies (10)
- git (git-gitAUR, git-glAUR)
- go (go-gitAUR, gcc-go-gitAUR, go-sylixosAUR, gcc-go-snapshotAUR, gcc-go) (make)
- npm (corepackerAUR, python-nodejs-wheelAUR) (make)
- mariadb (mysql55AUR, mysql56AUR, mytop-gitAUR, mysql81AUR, mysql57AUR, mysql80AUR, mysqlAUR, mariadb-lts, percona-server) (optional) – MariaDB support
- memcached (memcached-gitAUR) (optional) – MemCached support
- openssh (openssh-gitAUR, openssh-dotconfigAUR, openssh-dotconfig-binAUR, openssh-selinuxAUR, openssh-hpn-shimAUR, openssh-gssapiAUR) (optional) – GIT over SSH support
- pam (pam-selinuxAUR) (optional) – Authentication via PAM support
- postgresql (postgresql-12AUR, postgresql13AUR, postgresql15-docsAUR, postgresql15AUR, postgresql17-docsAUR, postgresql17AUR, postgresql-gitAUR) (optional) – PostgreSQL support
- redis (redis-testingAUR, redis-gitAUR, keydbAUR, valkey) (optional) – Redis support
- sqlite (sqlite-fossilAUR) (optional) – SQLite support
Required by (3)
- act-runner (requires gitea)
- act_runner (requires gitea) (optional)
- gitea-github-theme (requires gitea)
Sources (5)
Archange commented on 2020-12-22 09:56 (UTC)
kageru commented on 2020-09-25 17:47 (UTC)
Upstream made changes to the default config that broke the patch. I fixed it and pushed a new version.
fclad commented on 2020-09-25 01:29 (UTC)
Current build is failing:
==> Validating source files with sha512sums... gitea ... Skipped gitea.tmpfiles ... Passed gitea.service ... Passed gitea.sysusers ... Passed gitea-arch-defaults.patch ... Passed ==> Removing existing $srcdir/ directory... ==> Extracting sources... -> Creating working copy of gitea git repo... Cloning into 'gitea'... done. Updating files: 100% (9521/9521), done. ==> Starting prepare()... patching file custom/conf/app.example.ini Hunk #1 FAILED at 7. Hunk #2 succeeded at 324 (offset 9 lines). Hunk #3 succeeded at 394 (offset 9 lines). Hunk #4 succeeded at 801 (offset 40 lines). Hunk #5 succeeded at 829 (offset 40 lines). 1 out of 5 hunks FAILED -- saving rejects to file custom/conf/app.example.ini.rej ==> ERROR: A failure occurred in prepare(). Aborting...
WSDMatty commented on 2020-06-08 04:19 (UTC)
Cannot build package. I'm not sure what's wrong....
Output from makepkg -si
tinywrkb commented on 2020-02-27 13:17 (UTC)
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 (UTC)
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 (UTC)
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 (UTC)
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 (UTC)
Great! Thanks.
Pinned Comments