| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
Summain default has changed, so to be compatible with old
summain output files, we have to force the checksum algorithm to what
the old default was.
|
|
|
|
This used to assume things of gpg's output, which break when gpg
becomes version 2.1.something. This changed version of the step should
hopefully work with either version of gpg.
|
|
Yarn now does that automatically.
|
|
|
|
This has never worked, *sigh*.
|
|
|
|
|
|
|
|
|
|
|
|
The actual gpg error message is now shown, instead of hidden
behind a "unknown tag found" message.
|
|
|
|
Originally, we would create L/wanted, then do a manifest, then create
L/cache, then backup, restore, verify. This would sometimes fail, if
the full-second timestamp of L would change when L/cache was created.
So we (well, I) changed it so that we fiddled with the manifest just
before making a backup, but this was weird and confusing and would
still sometimes fail. This should now be much clearer and therefore
more robust.
|
|
The single file restore test had a bug, in that it was depending on
various test steps to execute fast enough that the wall clock did not
advance to the next second. This has been fixed by allowing manifests
to be done on single files instead of just directories.
Add a test for an extended attribute value changing, and that being
the only change in the live data. The backup needs to notice that it
has changed. This was intended to be the original change in this
commit, but I ran into the test bug above, so I had to fix that too.
I was too lazy to detangle the two sets of changes for commits.
|
|
Some filesystems don't store sub-second parts of mtime. Bleh.
|
|
Depending on how the encrypted data is, the error message, when
accessing an encrypted repository without encryption enabled, may be
different. Deal with it.
|
|
|
|
This sets up a whole lot of infrastructure, too.
|
|
As part of this, make every repository operation step require an
explicit client name. The v6 reference formats have a client
name embedded that is the hostname of my laptop, so make those tests
use that name. This fixes what would not have run previously on any
system that isn't named havelock. Oops.
|
|
Remove cmdtest test for this.
To make things clearer in the new test, also change all the steps that
use a backup repository to have the user specify it explicitly.
|
|
|
|
It is just as, if not more, clear, and not much more tedious, to be
explicit about this.
|
|
|
|
|
|
|
