build script errors (fix-installers branch)
See original GitHub issueHello,
following the instructions of the fix-installers
building.md on Debian bullseye I encountered the following issues:
- deb-prepare.sh tries to install 2 packages from debian-backports that don´t exist.
- deb-gen-source.sh returns the following error:
dpkg-source: error: can't build with source format '3.0 (native)': native package version may not have a revision
Issue Analytics
- State:
- Created a year ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Fix installers and repo information #764 - GitHub
Fix installers and repo information by ibauersachs · Pull Request #764 · jitsi/jitsi. ... build script errors (fix-installers branch) #770.
Read more >How to expose bash script errors? | Apple Developer Forums
I have an Xcode Server and was able to find the "unary operator expected" error under Logs in "Raw Build Log" but there's...
Read more >"Error running command: Build script returned non-zero exit ...
Locally (using ' gatsby develop ') it runs fine - but when I deploy to Netlify with ' gatsby build ' I get...
Read more >Solved: Branch builds - Bamboo - Atlassian Community
Solved: Hi, I started experimenting with the branch build feature. ... Run a script file (phplint.sh); Fail if errors are reported.
Read more >Common Build Problems - Travis CI Docs
Common Build Problems. My tests broke but were working yesterday; My build script is killed without any error; My build fails unexpectedly; Segmentation...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thank you. I made it work that way. I found that the gpg key is hardcoded into the script and created a PR to make it a parameter see https://github.com/jitsi/jitsi/pull/773/files.
Create the folder /var/cache/m2-sbuild on your build host.
This is mounted into the chroot to cache the downloaded Maven dependencies.