Package: duply Version: 2.0.3-1 Severity: minor Tags: upstream Dear Maintainer,
Duply occasionally displays silly runtimes like the following:
| --- Finished state OK at 00:14:15.001 - Runtime 00:00:00.-930 ---
This is due to it taking start/stop timestamps by doing
| RUN_START=$(date_fix %s)$(nsecs)
, which is compatibility machinery that amounts to
| RUN_START=$(date +%s)$(date +%N)
, which is obviously not atomic and produces incorrect results if the
second happens to tick over between the two date calls.
Should be fixed by doing
| RUN_START=$(date +%s%N)
instead. I'm not writing a patch because of the compatibility concerns.
Thank you for maintaining duply.
regards,
Jan
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (650, 'testing-debug'), (550,
'unstable-debug'), (550, 'unstable'), (10, 'experimental-debug'), (10,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages duply depends on:
ii duplicity 0.7.14-2
ii gnupg 2.2.1-5
duply recommends no packages.
Versions of packages duply suggests:
ii openssh-client 1:7.6p1-2
-- no debconf information
signature.asc
Description: PGP signature
