So at the very least we have to try running svn to see if it is a repository, if svn isn't there, but if .svn does exist then fallback on some old code with a deprecation warning. If there is no .svn and no svn then it should be silent and add nothing to the file list. I wrote a little dummy package for a test case and just removed the .svn: - I'm not seeing much. Could you try out 1.3.2 (is it out yet?) There were a couple fixes for SVN including a bug in the legacy code interface. Anyway, I will add a test case for output on a not svn repo and try out sdist and egg_info to see if travis-ci turns up anything.
File "/home/travis/build/pombredanne/buildout/src/zc/buildout/tests.py", line 1074, in zc.buildout.tests.changes_in_svn_or_CVS_dont_affect_sig
print_(system(join(sample_buildout, 'bin', 'buildout')), end='')
Fallback onto .svn parsing
/sample-buildout/eggs/setuptools.eggpyN.N.egg/setuptools/svn_utils.py:234: DeprecationWarning: No SVN 1.3+ command found: falling back on pre 1.7 .svn parsing
"on pre 1.7 .svn parsing"), DeprecationWarning)
That seems to be a test named "changes_in_svn_or_CVS_dont_affect_sig" are you sure that the test case isn't an SVN working copy?
Anyway I can remove the log.warn line just before the depreciation warning which might make it easier to deal with.
Ok yes this is the trigger for determining if we need to crawl the directory. The legacy parser will operating on incomplete working copies also (only needs .svn/Enteries). I could make the initial trigger based on the existence of any of .svn/Enteries, .svn/dir-props, and .svn/dir-prop-base. I think this will work since you are only creating an (empty?) .svn. Would you agree that this would allow the test case to slip by?