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

This commit is contained in:
Joey Hess 2019-02-27 16:50:32 -04:00
commit 84c9c93d58
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
7 changed files with 65 additions and 4 deletions

View file

@ -0,0 +1,29 @@
[[!comment format=mdwn
username="cman122887@9badeb8bdb364090f0a22e00ba16426ad65c34c9"
nickname="cman122887"
avatar="http://cdn.libravatar.org/avatar/6b9d25d94633a5002be6fe34da1b97a0"
subject="similar?"
date="2019-02-27T02:47:56Z"
content="""
Hello!
I think I am getting something similar, but I can't quite tell:
git-annex: MoveFileEx \".git\\annex\\tmp\\SHA256E-s555--205ac67c0c3fdc7cbe48007246dd0642dda416a57e8604b241cebfd6d83fb00a.txt\" Just \".git\\annex\\objects\\510\\441\\SHA256E-s555--205ac67c0c3fdc7cbe48007246dd0642dda416a57e8604b241cebfd6d83fb00a.txt\\SHA256E-s555--205ac67c0c3fdc7cbe48007246dd0642dda416a57e8604b241cebfd6d83fb00a.txt\": does not exist (The system cannot find the path specified.)
This might just be the plain long path issue but I thought I saw similarities in what I am getting and this post.
Windows 10
Git for Win: 2.20.1
git-annex version: 7.20190219-g728228d5d
...
operating system: mingw32 i386
local repository version: 7
TIA for any advice you can bestow!
"""]]

View file

@ -0,0 +1 @@
git-annex-import currently refuses to import any files under the repo dir, saying to use git-add instead. I think it should treat git-ignored files as if they were outside the repo. I often have a dir under the repo that is gitignored, and acts as a temp work area; git-annex-import should treat the files there as if they were outside the repo.

View file

@ -0,0 +1,4 @@
In the sandbox environment used by git-annex standalone, the gpg binary exists, but not gpg-agent (or gpgconf or other potentially needed binaries). This causes problems when the host system provides a different version of gpg that does provide these programs. E.g. git-annex-test crypto tests seem to (indirectly?) use gpg-agent.
If I want to use my own gpg version (compatible with my own gpg-agent), is it safe to just delete all files named 'gpg' from the git-annex.linux directory?

View file

@ -0,0 +1,5 @@
In the standalone build of git-annex, the runshell script caches locale info in a directory the name of which is based on the full path to the script:
<http://source.git-annex.branchable.com/?p=source.git;a=blob;f=standalone/linux/skel/runshell;h=32849e3f8df85e9d260498539f147d0cbe96889a;hb=HEAD#l131>
When the full path is too long, this fails with the error "filename too long".
Also, if the locale info is specific to the standalone environment, maybe it could be built as part of the process that creates the standalone package, rather than built on-the-fly and cached in the user's home dir?

View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="gueux"
avatar="http://cdn.libravatar.org/avatar/47e44a21505727b2d6bb5d88f0468f34"
subject="comment 4"
date="2019-02-27T09:34:12Z"
content="""
Was the patch forgotten? It does not seem to be part of v2.21.0...
"""]]

View file

@ -1,4 +0,0 @@
Hi Everyone
I'm a new member and my name is Kullboys.
I'm happy to be familiar with you.
Thanks[.](https://lab.louiz.org/snippets/421)

View file

@ -0,0 +1,18 @@
[[!comment format=mdwn
username="mario"
avatar="http://cdn.libravatar.org/avatar/4c63b0935789d29210d0bd8cad8d7ac7"
subject="Find (and other operations) over multiple repos"
date="2019-02-25T14:33:26Z"
content="""
Sometimes I want to move files from one git annex repo to another. It would be really awesome if one could so something like:
git annex find --in here --and --not --in-repo /path/to/OTHER-REPO
Just to make myself clear. I do not mean \"other remote\" (foreign instance of \"same\" repo). I actually mean different repos without common location tracking, no common branches, etc. The only concession I would make (since I think it's necessary) would be that the same backend has to be used in both repos.
This approach could also be relevant for other git annex commands, e.g.:
git annex move file --to-repo /path/to/OTHER-REPO
Is there any way to do it? Or would this be a feature request worth to consider?
"""]]