Package: storebackup
Version: 3.2-1
Severity: important

If storeBackupRecover command is requested to recover a hidden
directory, it fails to do so:

nikita@blacky:/tmp/x> sudo storeBackupRecover -r 
/backup/home/dst/2012.01.07_04.33.06/nikita/.ssh -t .

nikita@blacky:/tmp/x> ls -aR
.:
./  ../  nikita/

./nikita:
./  ../


Although files are there in backup:

nikita@blacky:/tmp/x> ls
/backup/home/dst/2012.01.07_04.33.06/nikita/.ssh
authorized_keys.bz2  id_dsa_debian.pub  id_dsa_lc_svn      id_rsa_debian.pub
config.bz2           id_dsa_home        id_dsa_libdev.pub  known_hosts.bz2
id_dsa@              id_dsa_home.pub    id_dsa_lvk.pub     known_hosts.old.bz2
id_dsa_debian        id_dsa_ipaq.pub    id_rsa_debian.bz2  mama_id_dsa.pub


Similar command for non-hidden directory works as expected:

nikita@blacky:/tmp/x> sudo storeBackupRecover -r 
/backup/home/dst/2012.01.07_04.33.06/nikita/u-boot -t .

nikita@blacky:/tmp/x> ls -aR
.:
./  ../  nikita/

./nikita:
./  ../  u-boot/

./nikita/u-boot:
./  ../  console-diff  ramboot-diff


-- System Information:
Debian Release: 6.0.3
  APT prefers stable-updates
  APT policy: (680, 'stable-updates'), (680, 'stable'), (600, 'unstable'), 
(580, 'experimental'), (520, 'oldstable')
Architecture: i386 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages storebackup depends on:
ii  bzip2                  1.0.5-6           high-quality block-sorting file co
ii  debianutils            3.4               Miscellaneous utilities specific t
ii  perl                   5.10.1-17squeeze2 Larry Wall's Practical Extraction 

Versions of packages storebackup recommends:
ii  libio-compress-bzip2-p 2.024-1           Transitional dummy package for IO:
ii  perl [libio-compress-b 5.10.1-17squeeze2 Larry Wall's Practical Extraction 

storebackup suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to