Bug#972831: tar: produces incorrect TAR+zstd archive when creating archive remotely

2020-10-25 Thread Laurent Bonnaud

On 10/24/20 6:22 PM, Bdale Garbee wrote:


I took a quick look and the problem is with the use of localhost: in
the filename,


Thanks for checking!  In fact the problem also exists for remote hosts.


it appears to be unrelated to the compression algorithm chosen.


With xz I can create correct archives on remote hosts.

--
Laurent.



Bug#972831: tar: produces incorrect TAR+zstd archive when creating archive remotely

2020-10-24 Thread Laurent Bonnaud



Package: tar
Version: 1.30+dfsg-7
Severity: important


Dear Maintainer,

here is a a short list of commands that demonstrate the problem (it needs a SSH 
server):

$ mkdir foo
$ tar --zstd -cvf localhost:foo.tar.zst foo
$ zstd -t foo.tar.zst
foo.tar.zst  : 0 MB... zstd: foo.tar.zst: unsupported format

$ tar --zstd -tvf foo.tar.zst
zstd: /*stdin*\: unsupported format
drwxr-xr-x bonnaudl/bonnaudl 0 2020-10-24 17:41 foo/
tar: Child returned status 1
tar: Error is not recoverable: exiting now

The same thing without SSH (creating the archive on a local filesystem) works 
well.


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.9.0-1-rt-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages tar depends on:
ii  libacl1  2.2.53-8
ii  libc62.31-4
ii  libselinux1  3.1-2+b1

tar recommends no packages.

Versions of packages tar suggests:
ii  bzip21.0.8-4
ii  ncompress4.2.4.6-3
pn  tar-doc  
pn  tar-scripts  
ii  xz-utils 5.2.4-1+b1

-- no debconf information

--
Laurent.



Bug#972831: tar: produces incorrect TAR+zstd archive when creating archive remotely

2020-10-24 Thread Bdale Garbee
Laurent Bonnaud  writes:

> $ tar --zstd -cvf localhost:foo.tar.zst foo

I took a quick look and the problem is with the use of localhost: in the
filename, it appears to be unrelated to the compression algorithm
chosen.  I don't have time to chase this further today.

Bdale


signature.asc
Description: PGP signature