mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Browse source
This commit is contained in:
spwhitton 2013-03-12 09:42:04 +00:00 committed by admin
parent 7bb6e6e305
commit 16da0f7ba2
1 changed files with 28 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

28
doc/bugs/Renamed_special_remote_cannot_be_reactivated_by_the_webapp.mdwn Normal file
View file

@ -0,0 +1,28 @@
Setup:
* fresh install of Debian Wheezy with git-annex 4.20130227 pulled in from unstable
* clone existing repository and activate assistant
* repository has encrypted rsync remote originally setup with the name `metaarray`
* this remote was renamed to `ma` a long time ago, using the webapp
* had to perform this rename on each client
Steps:
* attempt to reactivate special remote using webapp repositories page, on reinstalled machine
Expected:
* special remote starts working
* renaming special remotes ought to survive clones
Actual:
* firstly, special remote activation page has blank hostname box and the hostname of the machine is in the username box
* form gives error "cannot change encryption type of existing remote"
Workaround:
* execute `git annex initremote metaarray`
* rename `metaarray` to `ma` again using the webapp
Perhaps the renaming of the remote not surviving clones is unavoidable, but the webapp should be able to cope with the situation. Thanks.