Closed alcad closed 6 years ago
Here is a quick fix for this issue if you have not figured it already.
gitlab-gitaly
Ebuild directory (ex. /usr/local/portage/overlays/fritteli/www-servers/gitlab-gitaly/
) and go to it.gitlab-gitaly-0.38.0-r1.ebuild
).fperms 0755 /var/lib/gitlab-gitaly/ruby/bin/*
(line 38) and save the file.repoman manifest
(if you don't have it, merge app-portage/repoman
package).chmod +x /var/lib/gitlab-gitaly/ruby/bin/*
.Thank you @mkconel your workaround worked like a charm.
@mkconel fperms simply doesn't support wildcards in this manner.
Changing the line:
fperms 0755 /var/lib/gitlab-gitaly/ruby/bin/*
to
fperms 0755 /var/lib/gitlab-gitaly/ruby/bin/{gitaly-ruby,ruby-cd}
fixes the problem for me.
Strange, it installed without problems for me. Perhaps we are using a different version of portage, or some different configuration of emerge-sandboxing? I don't know. FWIW, I'll implement @tkurbad 's change and hope it helps.
Done in ebuild 0.43.1.
Oh, and thanks for reporting, and sorry for the (very, very) long delay 😇
Hi Fritteli, i've got a trouble with update of gitlab. Gitaly cannot install and I receive this error:
It seems a path typo. Can you check please? Regards