You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If trying to create a .deb package on a system which has insufficient temp space, the stacktrace produced contains messages like:
org.vafer.jdeb.PackagingException: Could not create deb package
java.io.IOException: This archives contains unclosed entries.
but nothing which highlights the underlying issue. This leads to confusion which presumably explains tickets like this.
Having a separate check in createSignedDeb to catch the IOException and suggest a disk space problem (the most likely cause?) to the user would potentially speed up debugging this issue when people encounter it.
The text was updated successfully, but these errors were encountered:
If trying to create a .deb package on a system which has insufficient temp space, the stacktrace produced contains messages like:
org.vafer.jdeb.PackagingException: Could not create deb package
java.io.IOException: This archives contains unclosed entries.
but nothing which highlights the underlying issue. This leads to confusion which presumably explains tickets like this.
Having a separate check in createSignedDeb to catch the IOException and suggest a disk space problem (the most likely cause?) to the user would potentially speed up debugging this issue when people encounter it.
The text was updated successfully, but these errors were encountered: