Package: backupninja
Version: 0.9.3-6
Severity: grave
Tags: fixed-upstream
As thoroughly discussed [1] on backupninja's mailing-list,
incompatibilities between various readlink and backupninja versions
cause hardly predictable behaviour when using symlinks and/or globbing
in include/exclude/vsinclude statements for the dup and rdiff
handlers' configuration.
This has already lead users to think some directories were backup'd
when they were actually not; this can cause data loss, that's why I'm
setting severity grave to this bug.
This issue was fixed upstream in SVN r437.
[1] Thread with subject "that * and readlink issue...", starting on
http://lists.riseup.net/www/arc/backupninja/2006-06/thrd1.html,
going on on http://lists.riseup.net/www/arc/backupninja/2006-07/.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set
to fr_FR.UTF-8)
Versions of packages backupninja depends on:
ii bash 3.1-5 The GNU Bourne Again SHell
ii dialog 1.0-20060221-1 Displays user-friendly dialog boxe
ii mawk 1.3.3-11 a pattern scanning and text proces
backupninja recommends no packages.
-- no debconf information
--
intrigeri <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
