e213ef310f
* Fix minor FD leak in journal code. Closes: #754608 * direct: Fix handling of case where a work tree subdirectory cannot be written to due to permissions. * migrate: Avoid re-checksumming when migrating from hashE to hash backend. * uninit: Avoid failing final removal in some direct mode repositories due to file modes. * S3: Deal with AWS ACL configurations that do not allow creating or checking the location of a bucket, but only reading and writing content to it. * resolvemerge: New plumbing command that runs the automatic merge conflict resolver. * Deal with change in git 2.0 that made indirect mode merge conflict resolution leave behind old files. * sync: Fix git sync with local git remotes even when they don't have an annex.uuid set. (The assistant already did so.) * Set gcrypt-publish-participants when setting up a gcrypt repository, to avoid unncessary passphrase prompts. This is a security/usability tradeoff. To avoid exposing the gpg key ids who can decrypt the repository, users can unset gcrypt-publish-participants. * Install nautilus hooks even when ~/.local/share/nautilus/ does not yet exist, since it is not automatically created for Gnome 3 users. * Windows: Move .vbs files out of git\bin, to avoid that being in the PATH, which caused some weird breakage. (Thanks, divB) * Windows: Fix locking issue that prevented the webapp starting (since 5.20140707). # imported from the archive
37 lines
1.8 KiB
Markdown
37 lines
1.8 KiB
Markdown
Finished moving the Android autobuilder over to the new clean build
|
|
environment. Tested the Android app, and it still works. Whew!
|
|
|
|
There's a small chance that the issue with the Android app not working on
|
|
Android 4.3 has been fixed by this rebuild. I doubt it, but perhaps someone
|
|
can download the daily build and give it another try..
|
|
|
|
----
|
|
|
|
I have 7 days left in which I'd like to get remote gcrypt repositories
|
|
working in the assistant. I think that should be fairly easy, but a
|
|
prerequisite for it is making git-annex-shell support being run on a gcrypt
|
|
repository. That's needed so that the assistant's normal locked down ssh
|
|
key setup can also be used for gcrypt repositories.
|
|
|
|
At the same time, not all gcrypt endpoints will have git-annex-shell
|
|
installed, and it *seems* to make sense to leave in the existing support
|
|
for running raw rsync and git push commands against such a repository. So
|
|
that's going to add some complication.
|
|
|
|
It will also complicate git-annex-shell to support gcrypt repos. Basically,
|
|
everything it does in git-annex repos will need to be reimplemented in
|
|
gcrypt repositories. Generally in a more simple form; for example it
|
|
doesn't need to (and can't) update location logs in a gcrypt repo.
|
|
|
|
----
|
|
|
|
I also need to find a good UI to present the three available choices
|
|
(unencrypted git, encrypted git, encrypted rsync) when setting up a repo
|
|
on a ssh server. I don't want to just remove the encrypted rsync option,
|
|
because it's useful when using xmpp to sync the git repo, and is simpler to
|
|
set up since it uses shared encryption rather than gpg public keys.
|
|
|
|
My current thought is to offer just 2 choices, encrypted and non-encrypted.
|
|
If they choose encrypted, offer a choice of shared encryption or encrypting
|
|
to a specific key. I think I can word this so it's pretty clear what the
|
|
tradeoffs are.
|