git svn fetch spewing warnings

Hi,

I'm using git 1.5.1.rc1.13.g0872 and I just tried the following to
create a new git-svn tracked repository.

I did:


    git svn init $URL
    git svn fetch 
    # I also tried git svn fetch --no-follow-parent

The command eventually completed and left me with a working
repository, but in the process I had screenfuls of warning messages
like this:

W: Ignoring error from SVN, path probably does not exist: (175002): RA layer request failed: REPORT request failed on '/bioconductor/!svn/bc/12000': REPORT of '/bioconductor/!svn/bc/12000': Could not read chunk size: Secure connection truncated (https://hedgehog.fhcrc.org)
W: Ignoring error from SVN, path probably does not exist: (175002): RA layer request failed: REPORT request failed on '/bioconductor/!svn/bc/12100': REPORT of '/bioconductor/!svn/bc/12100': Could not read chunk size: Secure connection truncated (https://hedgehog.fhcrc.org)
W: Ignoring error from SVN, path probably does not exist: (175002): RA layer request failed: REPORT request failed on '/bioconductor/!svn/bc/12200': REPORT of '/bioconductor/!svn/bc/12200': Could not read chunk size: Secure connection truncated (https://hedgehog.fhcrc.org)

I haven't seen them before, but...

  1. I haven't initialized a new repository in this way for awhile and
     git-svn has been updated

  2. The subversion server I'm talking to was recently upgraded to
     1.4.2

Thanks,

+ seth
-- 
Seth Falcon | Computational Biology | Fred Hutchinson Cancer Research Center
http://bioconductor.org

Seth Falcon [off-list ref] wrote:

Hi,

I'm using git 1.5.1.rc1.13.g0872 and I just tried the following to
create a new git-svn tracked repository.

I did:


    git svn init $URL
    git svn fetch 
    # I also tried git svn fetch --no-follow-parent

The command eventually completed and left me with a working
repository, but in the process I had screenfuls of warning messages
like this:

We now try harder to find previous versions of the path we're tracking.
I've also changed the window from 1000 to 100 revisions, so the
warning message spewing is 10 times more frequent.  Don't worry, though
it's harmless :)

-- 
Eric Wong