[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: gnome stuck on cvs2svn

From: Michael Haggerty <mhagger_at_alum.mit.edu>
Date: 2006-04-21 14:58:18 CEST

Giovanni Bajo wrote:
> Ben Collins-Sussman <sussman@red-bean.com> wrote:
>>The gnome project was supposed to migrate to subversion a month ago,
>>but have been stuck on a cvs2svn conversion problem:
>>
>>http://mail.gnome.org/archives/gnome-announce-list/2006-March/msg00025.html
>
> Marginally, I'll quote this:
>
> ----------------------------------------------------------
> The second spanner is that container, our CVS (and to-be Subversion)
> server, is still running python2.2. Since I first started planning this
> migration (back in Aug/Sep), the cvs2svn code has moved on a fair bit,
> and includes some useful new features (e.g. storing the CVS version
> number for each revision as a subversion property). Unfortunately, it
> now requires python2.3, and I've been unsuccessful so far in getting a
> newer version of python working on container for various reasons
> (<cough>RHEL3</cough).
> ----------------------------------------------------------
>
> I think it's a clear demonstration why client-side tools should try to be as
> compatible as possible with Python versions. svnmerge.py runs with any Python
> 2.0+ for a reason. It could be *marginally* cleaned up if the requisite was
> made higher, but to me it's really not worth the price to pay in compatibility.

Normally I would suggest that this discussion take place on the
dev@cvs2svn.tigris.org mailing list, except for the fact that things are
rather lonely over there. Some assistance supporting and improving
cvs2svn would be much appreciated.

We made a conscious decision last November, discussed on the cvs2svn-dev
mailing list, to bump the required Python version up to 2.2. The
backwards-compatibility requirements for cvs2svn, which only has to be
run once on an arbitrary computer, are not as critical as those for
svnmerge.py, which has to run regularly on every developer's computer.
(cvs2svn is more of a server-side than client-side program.) Therefore
I think that requiring Python 2.2 for cvs2svn is not unreasonable.

After that decision, a Python 2.3 feature was inadvertently used in
trunk. This problem was reported at the end of February and I committed
what I believe to be a fix about a week ago. I haven't heard
confirmation yet that that fix helped the Gnome conversion efforts (they
were having technical problems with anonymous access to the cvs2svn
repository).

I haven't been following the other travails of the Gnome project very
closely.

Michael

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 21 18:51:19 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.