7189dfd77d
* webapp: Detect when upgrades are available, and upgrade if the user
desires.
(Only when git-annex is installed using the prebuilt binaries
from git-annex upstream, not from eg Debian.)
* assistant: Detect when the git-annex binary is modified or replaced,
and either prompt the user to restart the program, or automatically
restart it.
* annex.autoupgrade configures both the above upgrade behaviors.
* Added support for quvi 0.9. Slightly suboptimal due to limitations in its
interface compared with the old version.
* Bug fix: annex.version did not get set on automatic upgrade to v5 direct
mode repo, so the upgrade was performed repeatedly, slowing commands down.
* webapp: Fix bug that broke switching between local repositories
that use the new guarded direct mode.
* Android: Fix stripping of the git-annex binary.
* Android: Make terminal app show git-annex version number.
* Android: Re-enable XMPP support.
* reinject: Allow to be used in direct mode.
* Futher improvements to git repo repair. Has now been tested in tens
of thousands of intentionally damaged repos, and successfully
repaired them all.
* Allow use of --unused in bare repository.
# imported from the archive
23 lines
1.1 KiB
Markdown
23 lines
1.1 KiB
Markdown
Worked on making the assistant able to merge in existing encrypted
|
|
git repositories from rsync.net.
|
|
|
|
This had two parts. First, making the webapp UI where you click to enable a
|
|
known special remote work with these encrypted repos. Secondly, handling
|
|
the case where a user knows they have an encrypted repository on rsync.net,
|
|
so enters in its hostname and path, but git-annex doesn't know about that
|
|
special remote. The second case is important, for example, when the
|
|
encrypted repository is a backup and you're restoring from it. It wouldn't
|
|
do for the assistant, in that case, to make a *new* encrypted repo and
|
|
push it over top of your backup!
|
|
|
|
Handling that was a neat trick. It has to do quite a lot of probing, including
|
|
downloading the whole encrypted git repo so it can decrypt it and merge it,
|
|
to find out about the special remote configuration used for it. This all
|
|
works with just 2 ssh connections, and only 1 ssh password prompt max.
|
|
|
|
Next, on to generalizing this rsync.net specific code to work with
|
|
arbitrary ssh servers!
|
|
|
|
----
|
|
|
|
Today's work was made possible by [RMS's vision 30 years ago](http://article.olduse.net/771@mit-eddie.UUCP).
|