Package: tar Version: 1.14-2 Severity: normal
If you invoke tar with a remote device name it tries to invoke /usr/libexec/rmt on the remote box, but this file (and indeed the whole directory) does not exist on a Debian Sarge system. Examining the executable of tar with "strings", the name of the executable appears to be hard-coded into the tar program. A workaround is to create the libexec directory on the remote system, then a symlink for rmt pointing to /etc/alternatives/rmt. The tar package doesn't seem to have changed recently - has the Debian policy perhaps changed and left tar behind? -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-1-686-smp Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) (ignored: LC_ALL set to en_GB) Versions of packages tar depends on: ii libc6 2.3.2.ds1-21 GNU C Library: Shared libraries an -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
