So this is an alleged pigz bug being reported? Then why is it being reported on this gzip bug list? It should be reported instead at https://github.com/madler/pigz/issues .
Though don’t bother, because this is not a bug in pigz. The problem is with the “other un/zippers” which per the linked report on sourceforge is actually just 7-Zip. The bug/feature in 7-Zip, according to the author (Igor Pavlov), is that it intentionally refuses to rename entries that have a data descriptor, regardless of whether or not the data descriptor uses a signature. Igor notes that he could have added code to detect the nature of the data descriptor to enable the rename, but he simply opted not to and instead declines the rename request. Otherwise, 7-Zip appears to have no issues with pigz-created zip files. Mark Adler pigz author On Jun 15, 2025, at 5:49 AM, oset <o...@superbox.pl> wrote: Zip created by pigz[1] is deemed to be corrupted even though it is considered valid by unzip et alli [2]. I do not claim pigz's zip is correct but other un/zippers think so. Apparently it is mentioned in paragraph 4.3.9.3 of ZIP File Format Specification [3][4]. 4.3.9.3 Although not originally assigned a signature, the value 0x08074b50 has commonly been adopted as a signature value for the data descriptor record. Implementers SHOULD be aware that ZIP files MAY be encountered with or without this signature marking data descriptors and SHOULD account for either case when reading ZIP files to ensure compatibility. Also made a script that shows that in practice (attached). If you find this zip correct make gzip aware of it, if otherwise you find it incorrect else let me know, I may raise in pigz issues. Regards. -- 1. github.com https://github.com/madler/pigz 2. unzip, doublecmd, totalcmd, 7zip, winrar, and likely others 3. pkware.cachefly.net https://pkware.cachefly.net/webdocs/casestudies/APPNOTE.TXT 4. sourceforge.net https://sourceforge.net/p/sevenzip/bugs/2416/#84d4
<<attachment: gunzip-pigzip.zip>>
