Package: tar Version: 1.16-2 Severity: normal
I had made listed-incremental backups with GNU tar 1.16 on Gentoo (which worked nicely). Then I switched to Debian Etch, and tried to continue the incremental backups of the non-root file systems. But the result is that I got full backups (judging from the file sizes of the tar files). Looking in the snapshot files, the format seems to be different; the Gentoo tar produced ASCII snapshot files that list only directories (e.g., attached file boot-base.list), whereas the Debian tar produces binary files (apparently with NUL as separator) that list individual files (e.g., attached file boot-latest.list; these two snapshot files are for the same file system with only a few files added). My guess is that the Debian tar did not understand the Gentoo tar snapshot format and therefore procuded a full backup. The command line I used was, e.g.: tar -czf /usbd/backups/usr-local-`date -I`.tar.gz --listed-incremental=/usbd/backups/usr-local-latest.list --one-file-system /usr/local -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.19.3-perfctr-2 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages tar depends on: ii libc6 2.3.6.ds1-8 GNU C Library: Shared libraries tar recommends no packages. -- no debconf information
boot-base.list
Description: application/not-regular-file
boot-latest.list
Description: Binary data
