pbzip2 -cd sometimes (rarely) truncates data
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pbzip2 |
Fix Released
|
Medium
|
Yavor Nikolov |
Bug Description
I occasionally get Gentoo binary packages that will not unpack. I am aware of the previous issues with trailing garbage but this appears to be different and--ignore-
If I do 'tar -tvf broken.tar.bz2' it works fine.
If I do 'pbzip2 -d broken.tar.bz2' I get a correct tar file.
However, if I do 'pbzip2 -cd broken.tar.bz2 > broken.tar' I get a tar file that is truncated at 16384 bytes.
I have placed a small (40KB) example file here for testing: https:/
This was tested on version 1.1.12 on a Gentoo Linux system.
When I hit a package file that has this problem it is repeatable with that file. My only solutions when I hit this problem are to either delete and rebuilt the package or to temporarily remove the bzip2>pbzip2 symlink so that portage will use regular bzip2 which is fine with these files.
Related branches
Changed in pbzip2: | |
status: | New → Fix Committed |
assignee: | nobody → Yavor Nikolov (yavor-nikolov) |
importance: | Undecided → Medium |
milestone: | none → 1.1.13 |
Changed in pbzip2: | |
status: | Fix Committed → Fix Released |
Thanks for reporting that issue. I managed to reproduce it on Ubuntu.
Another way I managed to get a non-truncated tar: pbzip2 -cd < broken.tar.bz2 > broken.tar