Package: tar Version: 1.27.1-2+deb8u1 Severity: normal Dear Maintainer,
the following happens: # /bin/tar cz -p -P --atime-preserve --warning=no-file-ignored --warning=no-file-changed --one-file-system / /bin/tar: /etc/machine-id: Cannot utime: Read-only file system /bin/tar: Exiting with failure status due to previous errors "atime-preserve" does advise tar to write back the former access time, so the error message is correct, *but* if a file system is read-only there is no need to write back the access time in the first place, as can't have been changed. Searching for this lead me to <https://bugzilla.redhat.com/show_bug.cgi?id=500742>, so obviously there is already a (quite trivial) fix for this. Bye, Stefan -- System Information: Debian Release: 8.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages tar depends on: ii libacl1 2.2.52-2 ii libc6 2.19-18+deb8u9 ii libselinux1 2.3-2 tar recommends no packages. Versions of packages tar suggests: ii bzip2 1.0.6-7+b3 pn ncompress <none> pn tar-scripts <none> ii xz-utils 5.1.1alpha+20120614-2+b3 -- no debconf information
