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

Merge branch 'master' of ssh://git-annex.branchable.com

Browse source
This commit is contained in:
Joey Hess 2014-08-15 12:54:11 -04:00
commit aa31a7182e
7 changed files with 61 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
doc/bugs/can__39__t_connect_jabber_with_custom_google_apps_domain/comment_2_b639ad750a4635d95f6ad16a1aa39a3e._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawlU0H3uyacCnqWxjSI_chHBlHu8TDIkTt0"
nickname="Matt"
subject="cannot connect via google apps domain"
date="2014-08-14T15:55:07Z"
content="""
Having the same issue with our domain: zebradog.com SRV records are correctly specified (as defined here: https://support.google.com/a/answer/34143?hl=en)
"""]]

8
doc/devblog/day_216__various_minor_bugs/comment_1_0d0a0e75b9446f8a1c4cc43f36569473._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="EskildHustvedt"
ip="80.202.103.55"
subject="comment 1"
date="2014-08-14T05:30:46Z"
content="""
What exactly does «git-annex cannot add a file that has a space in its filename» mean? git-annex (/assistant) actually can't handle tracking any file that has a space in its filename?
"""]]

3
doc/forum/armhf_binary.mdwn Normal file
View file

@ -0,0 +1,3 @@
Does a armhf binary tarball exist anywhere? I'm running Ubuntu trusty on a armhf platform (beagleboard), and the repository package is out of date. I might try to get the standalone armel binary working using multiarch, but that seems only slightly less painful than compiling from scratch.
Or am I better off changing to a debian boot image, and be done with it?

8
doc/forum/armhf_binary/comment_1_9ca7ff6cb1f5dfc1e5ce8527e7e0a45f._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="209.250.56.7"
subject="comment 1"
date="2014-08-15T15:58:02Z"
content="""
The standalone armel build should work fine on armhf, assuming that the kernel supports EABI, which I'm pretty sure it does (or multiarch armel would not work).
"""]]

18
doc/forum/gcrypt_os_x_app_vs_brew.mdwn Normal file
View file

@ -0,0 +1,18 @@
Gcrypt remotes work when using the git-annex command bundled in the git-annex.app. But gcrypt doesn't work when git-annex is installed via home-brew (brew install git-annex).
The initial push will work, any subsequent commands (push/pull) will fail with:
gpg: anonymous recipient; trying secret key...
gpg: anonymous recipient; trying secret key...
gpg: anonymous recipient; trying secret key...
gpg: anonymous recipient; trying secret key...
gpg: decryption failed: No secret key
gcrypt: Failed to decrypt manifest!
In both cases (app/brew) it tries the same keys. The app version will use its own version of gpg, which will trigger password prompts. With the brew version gpgtools is used, so I won't get any prompts. (Keychain)
I tried "echo i | gpg -e -R XX -R XX | gpg -d" with the same recipients as the repo. It works well.
Has anybody hints or ideas what to try next?
Best, Jean-Louis

8
doc/forum/gcrypt_os_x_app_vs_brew/comment_1_cce5e2c16720cc8e32a4a479f50ce6b3._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="Ganwell"
ip="178.174.3.221"
subject="Problem solved"
date="2014-08-14T23:53:05Z"
content="""
It turns out gpgtools will save to wrong passphrase to the keychain without complaining. Thats why standard gpg worked and gpgtools didn't: There was a typo in the passphrase in the keychain.
"""]]

8
doc/forum/gcrypt_os_x_app_vs_brew/comment_2_8df8ba1ccea0f68110593ed90a9cad6d._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="209.250.56.7"
subject="comment 2"
date="2014-08-15T16:04:08Z"
content="""
Note that you can avoid the trying of multiple keys by doing `git config gcrypt.publish-participants true` -- this is done by default by the assistant when setting up new gcrypt remotes. It needs my branch of git-remote-gcrypt, which is included in the osx app, I don't know which one is being used in brew.
"""]]