Package: libtar0 Version: 1.2.16-1+deb7u2 Severity: serious Tags: patch Hi,
libtar as in stable is computing checksums with signed char when it writes archives, but with unsigned char when it reads them. This means that if you try to write an archive with e.g. UTF-8 in the filenames (where the high bit is set and thus the signed/unsigned distinction matters), libtar will write an archive it cannot itself read, unless you turn on the TAR_IGNORE_CRC option. GNU tar can read the archives without error, since Sun once had the same bug. unstable is fine, since the problem was fixed in 1.2.17, but stable is broken. You probably want these two patches from upstream; the first fixes the checksum writing, the second makes libtar accept both signed and unsigned checksums: http://repo.or.cz/w/libtar.git/commit/7611cc65f45aef9aad3d8756396caf017607bedf http://repo.or.cz/w/libtar.git/commit/e44cab4de65b5a6dbeb23f3f8b947b6b4117f628 -- System Information: Debian Release: 7.6 APT prefers stable APT policy: (750, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.3 (SMP w/40 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libtar0 depends on: ii libc6 2.13-38+deb7u4 libtar0 recommends no packages. libtar0 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
