I'm sending manually a followup to bug #714234 generated by reportbug because of issues I've been having with my provider's SMTP.
Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Alessandro Selli<[email protected]> To: Debian Bug Tracking System<[email protected]> Subject: Re: dump: restore #157 dump fails to restore incremental if directory was removed Message-ID:<[email protected]> X-Mailer: reportbug 6.4.4 Date: Sun, 08 Sep 2013 16:09:53 +0200 Package: dump Followup-For: Bug #714234 I incurred into this bug first on Fedora18 (https://bugzilla.redhat.com/show_bug.cgi?id=972370, filed on June 28th, 2013), and today on Debian Wheezy (7.1). On both systems, following the advice given inhttp://sourceforge.net/p/dump/bugs/157/ (created on 2012-06-21) works. That is, installing dump version b42 allows greater than 0 levels of backups to be successfully restored. In the case of Debian, I could restore a filesystem removing dump-0.4b44-1 and installing dump-0.4b42-1 downloaded fromhttp://it.archive.ubuntu.com/ubuntu/pool/universe/d/dump/dump_0.4b42-1_amd64.deb. The filesystem to be restored is an ext4 one, formatted without the huge_file feature. -- System Information: Debian Release: 7.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11.0.mini0 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dump depends on: ii e2fslibs 1.42.5-1.1 ii libblkid1 2.20.1-5.3 ii libc6 2.13-38 ii libcomerr2 1.42.5-1.1 ii libdevmapper1.02.1 2:1.02.74-7 ii libncurses5 5.9-10 ii libreadline5 5.2+dfsg-2~deb7u1 ii libselinux1 2.1.9-5 ii libsepol1 2.1.4-3 ii libuuid1 2.20.1-5.3 ii tar 1.26+dfsg-0.1 dump recommends no packages. dump suggests no packages. -- no debconf information -- Alessandro Selli<[email protected]> Tel. 340.839.73.05 VOIP SIP: [email protected] Chiavi PGP/GPG keys: B7FD89FD, 4A904FD9 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
