Your message dated Mon,  4 Feb 2019 10:02:55 -0700 (MST)
with message-id <[email protected]>
and subject line fixed in 1.30
has caused the Debian Bug report #565898,
regarding tar: --checkpoint-action dot option does not work
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
565898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565898
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: tar
Version: 1.20-1
Severity: normal

The option --checkpoint-action dot doesn't get recognized by tar.
Other options like bell or echo do work. For example:
$ tar --checkpoint-action dot
tar: dot: unknown checkpoint action
tar: Error is not recoverable: exiting now

$ tar --checkpoint-action echo
tar: You must specify one of the `-Acdtrux' options
Try `tar --help' or `tar --usage' for more information.

The error can be traced on the source to the file
"src/checkpoint.c:83". The if present there should be an "else if".
This is the fix upstream have applied.



-- System Information:
Debian Release: 5.0.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages tar depends on:
ii  libc6                         2.7-18     GNU C Library: Shared libraries

tar recommends no packages.

Versions of packages tar suggests:
ii  bzip2                         1.0.5-1    high-quality block-sorting file co
pn  ncompress                     <none>     (no description available)

-- no debconf information

--
Félix Ortega Hortigüela
Sent from Madrid, Spain



--- End Message ---
--- Begin Message ---
This bug no longer exists in 1.30, not sure when it got fixed upstream offhand.

Bdale

--- End Message ---

Reply via email to