Bug #2785
closed
pkg(8) fails to process some packages, reports a "truncated input" error
0%
Description
pkg upgrade tentative on -master, with pkg-1.4.10:
[1/35] Upgrading pciids from 20150105 to 20150124...
[1/35] Extracting pciids-20150124: 0%
pkg: archive_read_extract(): truncated input
[1/35] Extracting pciids-20150124: 100%
[1/35] Deleting files for pciids-20150124: 100%
pkg: unlinkat(usr/local/share/pciids/): Bad file descriptor
Updated by ftigeot almost 10 years ago
Various people have reported similar issues on the IRC channel.
It is unclear when pkg(8) started to fail exactly since this problem does not occur systematically.
However, we can be sure pkg-1.3.x was safe.
According to the logs of my wolfpond.org mirror, pkg(8) was upgraded to version 1.4.0 on December 16, 2014.
Updated by ftigeot almost 10 years ago
pkg-1.3.8_3 is able to successfully upgrade a system where pkg-1.4.10 fails.
Updated by ftigeot almost 10 years ago
pkg-1.4.10 still fails on world+kernel from December 15, 2014 (as of commit 08223d8ccc101b6ac6cfaf19be98117596423a8b).
Updated by ftigeot almost 10 years ago
pkg-1.4.2 is able to successfully upgrade a system where pkg-1.4.10 fails.
Updated by ftigeot almost 10 years ago
pkg-1.4.4 is able to successfully upgrade a system where pkg-1.4.10 fails.
Updated by ftigeot almost 10 years ago
pkg-1.4.6 also fails to upgrade the test system.
Updated by ftigeot almost 10 years ago
pkg 1.4.5 also fails.
Last good pkg version: 1.4.4
First bad pkg version: 1.4.5
Updated by ftigeot almost 10 years ago
pkg 1.4.5 started using chflags features.
According to tests made by zrj, chflags support is what is breaking package extraction.
pkg-1.4.10 without chflags support works as expected.
Updated by dragonflybsd1 over 9 years ago
- Status changed from New to Resolved
fixed starting with package 1.4.12