lrzuntar fails on m1 macOS

[demhademha]

LRZIP-next version: 0.8.9:
command used: lrzuntar -vv *.lrz
output:

The following options are in effect for this DECOMPRESSION.
Threading is ENABLED. Number of CPUs detected: 8
Detected 8,589,934,592 bytes ram
Nice Value: 19
Show Progress
Max Verbose
Overwrite Files
Temporary Directory set as: /var/folders/f1/lghqjk9d30g0g7c1bbs438ww0000gn/T/
Output filename is: usr.tar

Malloced 2,863,300,608 for tmp_outbuf
Detected lrzip version 0.8 file.
MD5 being used for integrity testing.
Validating file for consistency...[OK]
Detected lrzip version 0.8 file.
Decompressing...
Reading chunk_bytes at 18
Expected size: 563,200
Chunk byte width: 3
Reading eof flag at 19
EOF: 1
Reading expected chunksize at 20
Chunk size: 563,200
Reading stream 0 header at 24
Reading stream 1 header at 34
Reading ucomp header at 44
Fill_buffer stream 0 c_len 6,790 u_len 17,968 last_head 0

note that: LRZIP-next -d *.lrz does not work as well.
regards

[demhademha]

interestingly, the output of `tar -xf *.tar.lrzz is:

tar: Error opening archive: Can't initialize filter; unable to run program "lrzip -d -q"

[pete4abw]

Thank you for continuing to shake out lrzip-next @demhademha . But I must ask that you be clear and specific when reporting bugs. I do not believe you can use a wildcard with lrztar and lrzuntar.

I do not see an error for lrzuntar or lrzip-next -d in your post.
You cannot extract an lrz file from tar. You cannot use a wildcard with tar -xf.
FWIW lrztar and lrzuntar are not really useful since you can pipe into and out of tar and lrzip-next. Also lrztar is a terribly complicated program.
Try without wildcards. If you must use *.lrz then do it as a script and pass one file at a time to lrz...

[demhademha]

I can confirm that without wildcards, lrzuntar works. However, unzstd (the zstd decompression tool) works with wild cards, so I was expecting similar behaviour.

Thanks for your continuous support

[demhademha]

Also, perhaps it may be an idea to rename lrztar to lrzip-next-tar or similar to prevent conflict with lrzip

[pete4abw]

lrzip-next DOES handle wild card filenames easily and successfully. Perhaps this is because you are using the zsh shell. Shell expansion is processed properly. I cannot vouch for lrztar and untar. But they must be used with TAR files that are lrzip'ped.

$ lrzip-next -L1 e*
Output filename is: enwik8.lrz
enwik8 - Compression Ratio: 3.033. Average Compression Speed: 47.500MB/s.
Total time: 00:00:02.28

Output filename is: enwik9.lrz
enwik9 - Compression Ratio: 3.444. Average Compression Speed: 52.944MB/s.
Total time: 00:00:17.44

$ lrzip-next -df e*lrz
Output filename is: enwik8
Validating file for consistency...[OK]
100%      95.37 /     95.37 MB0 /     95.37 MB
Average DeCompression Speed: 95.000MB/s

MD5:a1fa5ffddb56f4953e226637dabbb36a
Output filename is: enwik8: [OK] - 100,000,000 bytes                                
Total time: 00:00:00.82
Output filename is: enwik9
Validating file for consistency...[OK]
100%     953.67 /    953.67 MB0 /    953.67 MB
Average DeCompression Speed: 476.500MB/s

MD5:e206c3450ac99950df65bf70ef61a12d
Output filename is: enwik9: [OK] - 1,000,000,000 bytes                                
Total time: 00:00:30.38

[demhademha]

I can confirm this behaviour is correct
Thanks once again for your guidance