Issue #72: Cloning SVN repo fails
| Reported by: | Ilya Evseev |
| State: | resolved |
| Created on: | 2015-01-10 06:25 |
| Updated on: | 2015-02-25 20:05 |
Description
Kallithea contains a SVN import bug that seems already fixed in Rhodecode: https://rhodecode.tenderapp.com/help/discussions/problems/232-error-on-import-svn-repository
Error message:
Exception <urlopen error url [http://:*@...] does not look like an hg repo org_exc: cannot look up remote revision; remote repository does not support the 'lookup' capability> occured when forking repository, doing cleanup...
Here is my patch for /usr/local/lib/python2.7/dist-packages/kallithea/lib/vcs/backends/hg/repository.py
Attachments
kallithea-hgsvn-repository.patch
Comments
Comment by Mads Kiilerich, on 2015-01-21 16:46
Fixed with a slightly different approach. Please test!
Comment by Ilya Evseev, on 2015-02-25 19:31
Cannot test because "pip install --proxy=http://192.0.2.2:8123 --upgrade kallithea" ignores already installed mercurial-2.8.2-1ubuntu1 package and tries to exec "Downloading/unpacking mercurial>=2.8.2,<3.2 ...".
Comment by Mads Kiilerich, on 2015-02-25 19:33
Why is that a problem? And is it a new problem?
Comment by Ilya Evseev, on 2015-02-25 19:44
"pip install --upgrade --no-deps kallithea" says:
Requirement already up-to-date: kallithea in /usr/local/lib/python2.7/dist-packages Cleaning up...
And Kallithea version is not updated - still 0.1..
Comment by Mads Kiilerich, on 2015-02-25 20:05
It would not be good to make a new release without getting verification that the issues have been fixed. So you have to test the development version. See developer setup on https://bitbucket.org/conservancy/kallithea/wiki/Home .