Merge branch 'master' of ssh://git-annex.branchable.com
This commit is contained in:
commit
e910f19010
10 changed files with 117 additions and 0 deletions
|
@ -0,0 +1,12 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://joeyh.name/"
|
||||
ip="4.154.0.63"
|
||||
subject="comment 3"
|
||||
date="2013-08-24T19:27:57Z"
|
||||
content="""
|
||||
Leonardo, you made me boot up my windows machine just to check if cygwin git truncated files at the colon. It does not.
|
||||
|
||||
AFAIK, Cygwin transliterates colons to another unicode character or something like that. I would be highly surprised if the Cygwin people consider this feature to be a bug.
|
||||
|
||||
Since you need Cygwin to build git-annex on Windows anyway (though not to run it!), this remains WONTFIX.
|
||||
"""]]
|
|
@ -0,0 +1,15 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://joeyh.name/"
|
||||
ip="4.154.0.63"
|
||||
subject="comment 9"
|
||||
date="2013-08-24T19:10:21Z"
|
||||
content="""
|
||||
@Michael how large a copy are you doing? And what kind of remote are you copying the files to?
|
||||
It would be helpful if you could be more specific about something I could do to reproduce the problem. Without a test case, I am unlikely to fix the bug. With a test case, I'd be surprised if it took long to fix it.
|
||||
|
||||
If you have a process running that is experiencing the problem, you can also narrow it down a *lot* by looking at what these leaking pipe file descriptors are pipes to. For example, if you have:
|
||||
|
||||
lr-x------ 1 michael michael 64 Aug 10 20:14 895 -> pipe:[2251602]
|
||||
|
||||
You can run `find /proc/ -ls 2251602` and find the process at other end of the pipe, and look its pid up in ps to see what command it is.
|
||||
"""]]
|
|
@ -0,0 +1,10 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://joeyh.name/"
|
||||
ip="4.154.0.63"
|
||||
subject="bad bug report title 101"
|
||||
date="2013-08-24T19:17:29Z"
|
||||
content="""
|
||||
I don't understand why you think the problem has something to do with Windows drive letters. There are no Windows drive letters in the symlinks you show. The only place I see any Windows drive letter is in the descripton of the remote that `git annex get` displays when it fails to get the file. That description is purely informative, it's not a path that git-annex is trying to use.
|
||||
|
||||
I'd suggest that you run `git annex get --debug` to see if it is doing anything obviously wrong. The mostly likely culprit is your SMB setup, which I am not going to be able to replicate.
|
||||
"""]]
|
|
@ -0,0 +1,10 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://joeyh.name/"
|
||||
ip="4.154.0.63"
|
||||
subject="comment 2"
|
||||
date="2013-08-24T19:48:46Z"
|
||||
content="""
|
||||
I'm confused by this bug report, because it seems to me I already fixed this same problem in commit a64106dcef5c5aad825662ef115cb2a1cc6985a8. There the problem was that encfs in paranoia mode doesn't support hard links. So I made it detect when createLink fails, and fall back to a code path that doesn't need hard links.
|
||||
|
||||
Can you re-check the version you have, and perhaps try with a current daily build?
|
||||
"""]]
|
|
@ -0,0 +1,12 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://joeyh.name/"
|
||||
ip="4.154.0.63"
|
||||
subject="seems like a general git problem"
|
||||
date="2013-08-24T19:55:56Z"
|
||||
content="""
|
||||
\"unable to create temporary sha1 filename\" is a git error message. I don't actually see any git-annex failure here, just a git failure that seems to lead to a cascade of other failures.
|
||||
|
||||
I'm not sure if the \"/media/freebox/.t/tmprepo3/.git: No such file or directory\" is because git clone has failed due to the other errors, or if git clone somehow failed to set up the .git directory.
|
||||
|
||||
It would probably be helpful to have a play around with git on this filesystem and see what breaks. Alternatively, you can use git-annex with `--debug` to see the git commands it's running that fail, and try them yourself and perhaps strace or gdb them or something to see where they go wrong.
|
||||
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue