On 11/28/06, Seth Falcon <sethfalcon@xxxxxxxxx> wrote:
Is CamelEar an empty directory (or was it an empty directory in the first fetch) by any chance?
No, neither. The directory isn't empty on the requested revision, nor in the initial revision. Anyways… I've tried to init and fetch the repository again, and guess what, it worked. So my bet that this was caused by a broken connection during the initial fetch was probably right -- I'll try to "force" a broken connection and see what happens… Hmmm.… mini:/tmp pazu$ git-svn init https://tech.bga.bunge.com/BungeHomeExt/GLS/trunk/java/bg-cam mini:/tmp pazu$ git-svn fetch A bg-cam.ipr A CamelWeb/CamelWeb.iml A CamelWeb/.classpath A CamelWeb/JavaSource/.emptyDir A CamelWeb/.serverPreference A CamelWeb/.website-config ... <<Here I turned AirPort off>> Committing initial tree d14cd2aca9a6f15fdc8875212776c6a7cd111341 r8618 = 5a994a730da8dc8141fd116100a773061b7d4212 Creating fetcher for revision 5a994a730da8dc8141fd116100a773061b7d4212 Starting update on revision 9236 Opening CamelService/ejbModule/com/bunge/logistics/elevator/service/util/ElevatorConstants.java@8618 Error from SVN, (200003): Incomplete data: Delta source ended unexpectedly When I deactivated AirPort, git-svn hang for a long while, but it finally timed out and just saved what it got so far as the initial revision. Then when git-svn tried to fetch the next revision, it ended up trying to open a file that wasn't checked out during the (broken) initial fetch. Well, it seems I've found the problem. Unfortunately I have no idea how to fix that… I'll read some subversion books and source code to figure that out. -- Pazu - 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