-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 status confirmed importance medium done -----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEExwf+p6/3mDvUSsaGH1G0ZBEHM/EFAmBmFfMACgkQH1G0ZBEH M/FnDQgAhImWqh76T9WUH4NzzfarEEZsdLKXg6lspkK14v3nEV0J1kd4PnsgxmL0 k0c2q3vcUOuB0QTyydWb5Jzf4C6JzmIRZEkJaHNojU7oFgyzu+AFq3r56/UdVFh/ yw84Ly3vaxN25BlR+T5kHENHtzmp9sMS8KdcECwh7EfxtxluItF/bkXk8kYukhlO WhnEkiyw/Fb6+5sQ0tl73t+V9zLOn2WrTLpSxaAsiZMel33aOBYgoPOic0v+Wpsv B407MFxAen5Z4EKHWwpQ2HLHik6OXiir6ZVX400+6inSJflqBCobJM0Lm/NH8OKu NacHNc7wXXHVGI9vKMliwg36OTJvCg== =/NIB -----END PGP SIGNATURE----- ** Changed in: duplicity Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1576051 Title: Duplicity cannot handle sparse files efficiently Status in Duplicity: Confirmed Status in duplicity package in Ubuntu: Confirmed Bug description: When running backup with duplicity, it cannot handle sparse files efficiently. I have a virtual machine image on my home dir, 26G -rw-r--r-- 1 libvirt-qemu kvm 33G huhti 28 08:59 dev02.img And duplicity is backing it up 33G, when it should only back up 26G. Steps to reproduce 1. Use qemu-image to create a sparse file 2. Run duplicity 3. Observe duplicity back it up whole instead of very small size To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1576051/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
