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#49372 - [gitlab-workhorse] Lack of gitlab-zip-cat and gitlab-zip-metadata
Attached to Project:
Community Packages
Opened by Janne Heß (das_j) - Tuesday, 17 May 2016, 12:13 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Wednesday, 18 May 2016, 10:07 GMT
Opened by Janne Heß (das_j) - Tuesday, 17 May 2016, 12:13 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Wednesday, 18 May 2016, 10:07 GMT
|
DetailsDescription:
When a gitlab runner is submitting artifacts to the coordinator (which is workhorse), workhorse requires the gitlab-zip-cat and gitlab-zip-metadata commands. These are statically linked executables which can be found in the root of the build directory after building workhorse and belong to /usr/bin. Additional info: * package version(s) gitlab-workhorse 0.7.2-4 * config and/or log files etc. Steps to reproduce: Try to submit articats from a gitlab runner. It will fail with a 500 error and a message in the logs like: "error: handleFileUploads: extract files from multipart: exec: "gitlab-zip-metadata": executable file not found in $PATH" |
This task depends upon
Closed by Sven-Hendrik Haase (Svenstaro)
Wednesday, 18 May 2016, 10:07 GMT
Reason for closing: Fixed
Wednesday, 18 May 2016, 10:07 GMT
Reason for closing: Fixed