Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#74948 - [gitlab-gitaly] should use custom git binary instead of system git
Attached to Project:
Community Packages
Opened by Joshua Holmer (Soichiro) - Friday, 03 June 2022, 02:23 GMT
Last edited by Caleb Maclennan (alerque) - Wednesday, 24 May 2023, 20:14 GMT
Opened by Joshua Holmer (Soichiro) - Friday, 03 June 2022, 02:23 GMT
Last edited by Caleb Maclennan (alerque) - Wednesday, 24 May 2023, 20:14 GMT
|
DetailsDescription:
It is recommended to use the custom git binary which is included with gitaly, according to https://docs.gitlab.com/ee/install/installation.html#git. Using the system git can cause issues such as this one: https://gitlab.com/gitlab-org/gitlab/-/issues/360783 Additional info: * package version(s): All * config and/or log files etc.: N/A * link to upstream bug report, if any: See description |
This task depends upon
Closed by Caleb Maclennan (alerque)
Wednesday, 24 May 2023, 20:14 GMT
Reason for closing: Won't implement
Wednesday, 24 May 2023, 20:14 GMT
Reason for closing: Won't implement
The specific issue linked above was a bug in Gitlab/Gitaly and subsequently fixed. Looking forward with Gitaly 16 they are dropping Ruby and the mix-and-match with Rugged wrapper on libgit2 plus Git system calls in favor of Go and *only* Git system calls. We'll see how packaging that goes, but the initial goal for Arch will be to use the system Git unless we really need to let it be vendored.
Feel free to open bugs if you have ongoing issues with this approach.