-
-
Notifications
You must be signed in to change notification settings - Fork 208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: v0.14.0 Unable to build .deb package #458
Comments
And to be more precise, the error comes from
Produce :
Everything worked fine before the commit c496bae |
Fix eza-community#458 + remove extra whitespaces
Hm, my initial guess would be that the bash version in the container is too old maybe ... can you tell us what version that is? I'm running bash 5.1.16 on my machine and there it works. Also, as a side note ... the |
And
And yeah, i noticed deb.gierens.de (thanks for that 👍 ) but has i don't have access to this domain at work… I managed to have my own auto-build of Eza .deb package based on a tiny script + Docker and the tools available at work ^^ I will comment in the PR for the rest :) |
just updated the deb repo by the way ... now ships v0.14.0 ;) |
This also avoid "useless cat" and allow `just` command to build manpages. Resolves eza-community#458
This also avoid "useless cat" and allow `just` command to build manpages. Resolves eza-community#458
This also avoid "useless cat" and allow `just` command to build manpages. Resolves eza-community#458 Co-authored-by: gierens <sandro@gierens.de> Co-authored-by: Gardouille <gardouille@gmail.com>
This also avoid "useless cat" and allow `just` command to build manpages. Resolves eza-community#458 Co-authored-by: gierens <sandro@gierens.de> Co-authored-by: Gardouille <gardouille@gmail.com>
If eza fails to compile, or if there is a problem during the build process, then please include the following information in your report:
If you are seeing compilation errors, please include the output of the build process.
./devtools/deb-package.sh
output :To reproduce :
The text was updated successfully, but these errors were encountered: