improve display when lockcontent fails

/dev/null stderr; ssh is still able to display a password prompt
despite this

Show some messages so the user knows it's locking a remote, and
knows if that locking failed.
This commit is contained in:
Joey Hess 2015-10-09 17:21:02 -04:00
parent 3b89d5a20c
commit 6145f905e0
Failed to extract signature
3 changed files with 40 additions and 22 deletions

9
debian/changelog vendored
View file

@ -5,6 +5,15 @@ git-annex (5.20150931) UNRELEASED; urgency=medium
all copies of its content being lost.
* git-annex-shell: Added lockcontent command, to prevent dropping of
a key's content. This is necessary due to the above bugfix.
* In some cases, the above bugfix changes what git-annex allows to be dropped:
- When a file is present in several special remotes,
but not in any accessible git repositories, dropping it from one of
the special remotes will now fail. Instead, the file has to be
moved from one of the special remotes to the git repository, and can
then safely be dropped from the git repository.
- If a git remote has too old a version of git-annex-shell installed,
git-annex won't trust it to hold onto a copy of a file when dropping
that file from some other remote.
* Do verification of checksums of annex objects downloaded from remotes.
* When annex objects are received into git repositories from other git
repos, their checksums are verified then too.