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
Describe the bug
The compress command is no longer available on Debian based systems. It still appears to be available in Unix and BSD systems. In LzwStreamWrapp::checkBinary() there is a check for both compress and uncompress. When attempting to extract a .tar.Z file the extract fails because of the isBinaryAvailable() check but uncompress is in fact still available.
The archive xmlfeed_lic475-2021_09_24.tar.Z could not be extracted. compress and uncompress commands are required
Configration (please complete the following information):
OS: Ubuntu 20.04.3
Version of library: 1.4.14
To Reproduce
Attempt to extract a LZW compressed .tar.Z file on newer debian systems where compress is not available or installable.
Expected behavior
Perhaps there could be a separate check. If writing to the archive then check for compress? Please take a look at the below. If that works for you then I can submit a pull request
Describe the bug
The compress command is no longer available on Debian based systems. It still appears to be available in Unix and BSD systems. In LzwStreamWrapp::checkBinary() there is a check for both compress and uncompress. When attempting to extract a .tar.Z file the extract fails because of the isBinaryAvailable() check but uncompress is in fact still available.
The archive xmlfeed_lic475-2021_09_24.tar.Z could not be extracted. compress and uncompress commands are required
Configration (please complete the following information):
To Reproduce
Attempt to extract a LZW compressed .tar.Z file on newer debian systems where compress is not available or installable.
Expected behavior
Perhaps there could be a separate check. If writing to the archive then check for compress? Please take a look at the below. If that works for you then I can submit a pull request
Possible Fix
The text was updated successfully, but these errors were encountered: