Package: rdiff-backup Version: 1.1.5-4 Severity: grave Justification: renders package unusable
This is arguably not a duplicate of bug 426110, since that bug report has been sitting around getting stale for a year, and the problem is actually grave. Basically, the current version of "rdiff-backup" is not compatible with that in Etch. People who trusted this backup software for backups to Debian *stable* servers have been screwed. The cause seems to be that Debian included in *stable* a development version of "rdiff-backup" with an unstable data format that is no longer supported. The problem has now become worse. As an interim measure to avoid abandoning 70GB of backup data on a remote server, I have kept my Debian *testing* workstations at "rdiff-backup" version 1.1.5-4. Unfortunately, this now means that I can't have the latest "python" nor software like "openoffice.org-writer". I assume the problem will get worse. I have no reasonable means for recovering all my backup data, and I assume other Debian *stable* users are in the same position. I need to know whether Debian intends to work with upstream to fix this problem. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/2 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 rdiff-backup depends on: ii libc6 2.7-10 GNU C Library: Shared libraries ii librsync1 0.9.7-1 Library which implements the rsync ii python 2.4.4-6 An interactive high-level object-o ii python-support 0.7.7 automated rebuilding support for P Versions of packages rdiff-backup recommends: ii python-pylibacl 0.2.2-1+b1 module for manipulating POSIX.1e A ii python-pyxattr 0.2.2-1 module for manipulating filesystem -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
