Package: apt-utils Version: 0.7.3 Severity: normal File: /usr/bin/apt-ftparchive
I have a package containing a file dating back to 1969 (as distributed by upstream). When running apt-ftparchive with --db, it interprets the warning to that effect from tar as a fatal error, and skips over the package saying "E: Corrupted archive". This does not occur when omitting the --db option. While I agree that supporting negative timestamps isn't exactly a top priority, it seems to me that apt-ftparchive ought to be able to tell the difference between tar errors and warnings, and not choke on the latter. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.22-1-k7 (SMP w/1 CPU core) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages apt-utils depends on: ii apt [libapt-pkg-libc6.5-6-4.4 0.7.3 Advanced front-end for dpkg ii libc6 2.6-3 GNU C Library: Shared libraries ii libdb4.4 4.4.20-8 Berkeley v4.4 Database Libraries [ ii libgcc1 1:4.2.1-0 GCC support library ii libstdc++6 4.2.1-0 The GNU Standard C++ Library v3 apt-utils recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
