git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike <ipso@snappymail.ca>
To: git@vger.kernel.org
Subject: git svn import failure : write .git/Git_svn_hash_BmjclS: Bad file descriptor
Date: Fri, 16 Jan 2015 09:13:17 -0800	[thread overview]
Message-ID: <54B946AD.5050701@snappymail.ca> (raw)

Similar to the issue mintywalker originally mentioned on Jan 8th 2015, 
during a "git svn clone" I get a Bad File Descriptor error using:

git-svn version 2.2.2 (svn 1.8.8) on Ubuntu 14.04.

<snip>
r460 = 456377de3906d689c56e51af842e18abe086a980 (refs/remotes/origin/trunk)
         A       client/binary/App_Client_v2.1.2.exe
r461 = 36848dbb7f417da2e381b61b68ff7b0d22a5bf7f (refs/remotes/origin/trunk)
write .git/Git_svn_hash_0WWL4a: Bad file descriptor
  at /usr/lib/perl5/SVN/Ra.pm line 623.


$ svn diff --diff-cmd diff -c 461
Index: client/binary/App_Client_v2.1.2.exe
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
Index: client/binary/App_Client_v2.1.2.exe
===================================================================
--- client/binary/App_Client_v2.1.2.exe    (revision 0)
+++ client/binary/App_Client_v2.1.2.exe    (revision 461)

Property changes on: client/binary/App_Client_v2.1.2.exe
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property


Not sure if it helps or not, but here is the commit immediately after 
that one:

$ svn diff --diff-cmd diff -c 462
Index: interface/help/App_Client.exe
===================================================================
--- interface/help/App_Client.exe  (revision 0)
+++ interface/help/App_Client.exe  (revision 462)
@@ -0,0 +1 @@
+link ../../client/binary/App_Client_v2.1.2.exe
\ No newline at end of file

Property changes on: interface/help/App_Client.exe
___________________________________________________________________
Added: svn:special
## -0,0 +1 ##
+*
\ No newline at end of property

Unfortunately the repository is private, but it seems like a pretty 
simple commit that is causing the problem?

If you need more information please let me know.

Thanks.


-- 
Mike

             reply	other threads:[~2015-01-16 17:23 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-16 17:13 Mike [this message]
     [not found] <CAK6Z60ciheWOUGOv1sYcA==B2WR1Rs_eMU+9a=R3FBwc_37CyQ@mail.gmail.com>
2015-02-26  9:09 ` git svn import failure : write .git/Git_svn_hash_BmjclS: Bad file descriptor Nico Schlömer
2015-02-26 13:49   ` Kyle J. McKay
2015-02-26 21:27     ` Eric Wong
2015-03-23 19:11       ` Junio C Hamano
2015-03-23 19:36         ` Eric Wong
2015-03-23 19:56           ` Junio C Hamano
  -- strict thread matches above, loose matches on Subject: below --
2015-01-29 22:03 Valery Yundin
2015-01-29 23:34 ` Eric Wong
2015-01-29 23:59   ` Valery Yundin
2015-01-30  0:22     ` Eric Wong
2015-01-30  0:40       ` Valery Yundin
2015-01-30  1:30         ` Eric Wong
2015-01-31 12:51           ` Nico Schlömer
2015-01-31 14:52             ` Valery Yundin
2015-02-12 19:18               ` Eric Wong
2015-02-16 15:10                 ` Nico Schlömer
2015-02-17  6:17                   ` Eric Wong
2015-02-25 10:19                     ` Kyle J. McKay
     [not found]                       ` <CAK6Z60fqEkM_tON6tcnwBqJzBCvLB=eVJdyXSnNb7N1iR_DSsw@mail.gmail.com>
2015-02-25 20:08                         ` Eric Wong
2015-02-25 20:33                         ` Kyle J. McKay
2015-01-08 12:43 Minty
2015-01-08 17:51 ` Minty
2015-01-14  1:50 ` Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54B946AD.5050701@snappymail.ca \
    --to=ipso@snappymail.ca \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).