Age | Commit message (Collapse) | Author | Files | Lines |
|
Signed-off-by: Ben Boeckel <mathstuf@gmail.com>
|
|
It seems CentOS 6 has a version of gpg that says "No secret key"
instead of "secret key not available". Fixed yarns to check for that.
Reported-by: Dennis Jacobfeuerborn
|
|
|
|
|
|
Remove use of extended attributes from some tests.
Make the remaining tests be conditional on whether
extended attributes actually work in the temporary
directory (in the user.* namespace).
|
|
The actual gpg error message is now shown, instead of hidden
behind a "unknown tag found" message.
|
|
This bug was originally triggered by the test suite, because the
error message in the code had a typo. While looking for that I noticed
that the code that was parsing the code seemed fishy.
This is now cleaner. First of all, I split the error messages for
"unknown tag" and "no tag". Then I rewrote the loop that parses
so it is robust against error situations. Then I tweaked the yarn
test so it now works.
|
|
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.
|
|
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.
|