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 2019-03-18 16:00:20 -04:00
commit c96e623343
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 27 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
doc/bugs/git-annex_standalone_provides_gpg_but_not_gpg-agent/comment_2_f2b6e4e863e99f6acef44f8e4e013b0d._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="Ilya_Shlyakhter"
avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
subject="comment 2"
date="2019-03-18T18:08:06Z"
content="""
Tests that rely on gpg fail. I think the latest gpg versions always run gpg-agent. So if you package gpg but not gpg-agent it will try to run the host's gpg-agent which may be incompatible with the gpg included in the standalone package.
"""]]

10
doc/bugs/git-annex_standalone_runshell_locale_cache_fails_on_too-long_filenames/comment_2_71603e2b624c4e07bbf59e260fd83a8f._comment Normal file
View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="Ilya_Shlyakhter"
avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
subject="comment 2"
date="2019-03-18T19:44:07Z"
content="""
\"Wouldn't you have had to put it in a directory path that's almost 4096 bytes deep for this to happen?\" -- I think it's trying to make a single pathname component corresponding to a directory path, so the relevant limit is 255 chars.
For my specific use cases I've found a way not to need the standalone version for now, by building git-annex conda package the normal way.
"""]]

9
doc/bugs/git_worktree_remove_fails/comment_2_2c6ce2244c885bb21ca82a841987dd47._comment Normal file
View file

@ -0,0 +1,9 @@
[[!comment format=mdwn
username="Ilya_Shlyakhter"
avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
subject="comment 2"
date="2019-03-18T19:54:04Z"
content="""
Maybe git considers .git an internal detail, so they might not guarantee things working correctly if it's changed to a symlink?
A clean way to handle this would be to add a 'git annex worktree' command, which normally just passes the rest of the command line to 'git worktree', but handles any git-annex-specific details as needed: e.g. 'git annex worktree add' calls 'git worktree add' then replaces the .git pointer file with symlink; 'git annex worktree remove' puts the .git pointer back then calls 'git worktree remove', etc.
"""]]