From: "Matthias Andree" <matthias.andree@uni-paderborn.de>
To: git@vger.kernel.org
Cc: "Eric Wong" <normalperson@yhbt.net>
Subject: git-svn intermittent issues with absent_file
Date: Thu, 27 Aug 2009 16:56:25 +0200 [thread overview]
Message-ID: <op.uzbs4bsq3myrm3@balu.cs.uni-paderborn.de> (raw)
Greetings,
we seem to have issues with checking out files from an SVN server via
https://. The problem is hard to reproduce, and shows as "absent_file"
warnings, i. e. files that are in the SVN checkout don't make it to the
Git checkin.
Perhaps this rings a bell with someone or there are similar reports that
relate to our issues...
## ISSUE ## Once in a while, a git-svn clone or rebase fails with files
missing from commits, as mentioned above. We haven't been able to figure
out under what circumstances this happens. If we try to reproduce this (i.
e. kill the directory completely and re-run the git svn clone), another
revision (for instance 170) might show this, or the clone may succeed.
This was observed with Git 1.6.0.4 under Ubuntu Linux Jaunty Jackalope
(9.04) and on a different computer with Git 1.6.4.1.196.g31f0b (from the
master branch) under a fully updated Cygwin 1.5.
Example log of failed data (sorry, we are not allowed to let you access
the repository, so we must debug by proxy).
I'm replacing substrings in the log below to maintain corporate
confidentiality levels:
$ git svn clone --no-checkout https://svnserver.example.edu/project/
Initialized empty Git repository in /tmp/compnet/.git/
W: +empty_dir: branches
W: +empty_dir: tags
W: +empty_dir: trunk
r1 = a1b0e99e3986da4d8d461944b623b6abb2460de4 (refs/remotes/git-svn)
...
r135 = 294077e62ee5f463b8ab97d961d9742ef89ae662 (refs/remotes/git-svn)
A ... (~100 PDF files)
...
A d1/u1/2009_06/f1.pdf
W: +empty_dir: d1/u2/slides/2009_06
W: absent_file: d1/u1/2009_06/d1/u1/2009_06/f2.pdf Insufficient
permissions?
W: absent_file: d1/u3/06_2009/f1/u3/2009_06/f3.pdf Insufficient
permissions?
W: absent_file: d1/u2/slides/2009_06/d1/u2/slides/2009_06/f4.pdf
Insufficient permissions?
r136 = 58523cf1fa867d33a74080dabdcbc85ae0ba99ec (refs/remotes/git-svn)
...
r139 = 2fb1647bc40d3815a5eefb32d43a375e03d2e871 (refs/remotes/git-svn)
Incomplete data: Delta source ended unexpectedly at
/usr/local/libexec/git-core/git-svn line 4605
Just re-running "git svn fetch" reproduces the "Incomplete data:" error
and aborts, but re-fetching an older version succeeds. No fiddling with
permissions needed.
## WORKAROUND ##
If this happens, I can force a checkout with, say, "git checkout -t -b
master remotes/git-svn", revert to the last good revision with "git svn
reset -r135" (this doesn't work without prior checkout) and then re-run
git svn fetch, which will usually succeed then.
The three absent_file lines are also recorded in
.git/svn/refs/remotes/git-svn/unhandled.log for r136.
Questions:
1. What causes these absent_file issues? How can we assist with debugging
this?
2. What does "Delta source ended unexpectedly" mean? (the line number is
bogus, it's just the finish_report call)
3. Is this or a similar issue known? Is this an issue with the SVN server,
the SVN bindings, or the git svn adaptor?
4. How can we avoid or fix this?
We're happy to test patches.
Thanks a lot in advance.
Cheers,
--
Matthias Andree
next reply other threads:[~2009-08-27 14:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 14:56 Matthias Andree [this message]
2009-08-27 19:19 ` git-svn intermittent issues with absent_file Eric Wong
2009-08-28 6:58 ` Matthias Andree
2009-08-28 8:14 ` Matthias Andree
2009-08-29 21:35 ` Ealdwulf Wuffinga
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=op.uzbs4bsq3myrm3@balu.cs.uni-paderborn.de \
--to=matthias.andree@uni-paderborn.de \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
/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).