Yeah, there have been a lot of bup releases in the last few days. But
version numbers are cheap, and this version is especially fun, because
it brings us the long-awaited 'bup restore' command!
'bup restore' in this version is about as simple-minded as it gets; it
runs a bit slowly (everything still gets ground through 'git cat-file
--stdin' in a subprocess), and it certainly doesn't do anything smart
with the bupindex. (A really smart bup restore implementation would
update the bupindex. Then it would know when a file hasn't changed
since the last time it was restored/saved, and it could skip
overwriting it like 'git checkout' would do. Someday...)
Still, mark this day in your calendars! Today is the day bup became
an actual potentially useful backup program!
Avery Pennarun (6):
options.py: better support for explicit no-* options.
options.py: handle optspecs that include inline square brackets.
options.py: remove extra newlines in usage string.
options.py: get the real tty width for word wrapping purposes.
cmd/save: always print a progress() message after a log() message.
cmd/restore: embarrassingly slow implementation of 'bup restore'
That makes one less thing in the "reasons bup is stupid" list in the README.
Have fun,
Avery
YAY *fireworks*
Just watch... now people are going to have *expectations* :)
Have fun,
Avery
I haven't done the great md5sum-the-whole-tree thing, (since I've made
some local changes) but I did a bup restore of a 50GB Aperture library,
and opened the restored library with no issues.
So, Win!
As soon as my 500GB backup finishes (it's been slowing down) I'll do a
test restore and md5sum the whole tree before and after. To me, that's a
pretty thorough end-to-end test, and I'll happily trust my photo library
to bup. :D
-Zandr