I just double-checked and I can only produce this issue on one machine (tested on 3). Apparently, this is has nothing to do with Git itself then. Any ideas of what could be wrong? Cheers, Nico On Thu, Feb 12, 2015 at 8:18 PM, Eric Wong <normalperson@xxxxxxxx> wrote: > Valery Yundin <yuvalery@xxxxxxxxx> wrote: >> On 31 January 2015 at 13:51, Nico Schlömer <nico.schloemer@xxxxxxxxx> wrote: >> > I tried the patch and I still get >> > ``` >> > [...] >> > r100 = e2a9b5baa2cebb18591ecb04ff350410d52f36de (refs/remotes/git-svn) >> > Unexpected result returned from git cat-file at >> > /home/nschloe/share/perl/5.18.2/Git/SVN/Fetcher.pm line 335. >> > Failed to read object 619f9d1d857fb287d06a70c9dac6b8b534d0de6a at >> > /home/nschloe/share/perl/5.18.2/Git/SVN/Fetcher.pm line 336, <GEN16> >> > line 757. >> > >> > error closing pipe: Bad file descriptor at >> > /home/nschloe/libexec/git-core/git-svn line 0. >> > error closing pipe: Bad file descriptor at >> > /home/nschloe/libexec/git-core/git-svn line 0. >> > ``` >> > when >> > ``` >> > git svn clone https://geuz.org/svn/gmsh/trunk >> >> It seems that the same commit dfa72fdb96 is responsible for the error >> in "git svn clone https://geuz.org/svn/gmsh/trunk";. But unlike in my >> case, the patch doesn't fix it. > > (top-posting corrected) > > Odd, I managed to clone that without issues, but I couldn't reproduce > this problem with or without the tempfile clearing patch applied. > > git svn clone --username gmsh https://geuz.org/svn/gmsh/trunk > > Anybody else? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html