You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Ben Collins-Sussman <su...@red-bean.com> on 2006/04/20 13:30:07 UTC

gnome stuck on cvs2svn

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

The more general description of svn rollout is here:

  http://live.gnome.org/Subversion

It's not that they found a bug in cvs2svn, but rather Yet Another
Pathological Case in their RCS files.  Apparently there was some
horrible time-clock skew in their server at some point, and cvs2svn
doesn't know how to handle that particular pathology yet, so some svn
commits are appearing out-of-order.

Have they sent a patch to the cvs2svn dev list?  Has anyone been
helping them work through this?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org


Re: [Svnmerge] Re: gnome stuck on cvs2svn

Posted by Martin Furter <mf...@rola.ch>.

On Sat, 22 Apr 2006, Blair Zajac wrote:

> Giovanni Bajo wrote:
>> Ben Collins-Sussman <su...@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.
>
> If you're in the mood, contrib/server-side/svn-fast-backup could use a little 
> backport effort :)
>
> Just joking, but it uses subprocess which is distributed with Python 2.4 and 
> all the RHEL3 and RHEL4 systems have older OSes.

If you don't care about windows (which is easier to upgrade to python 2.4) 
you can use the subprocess compatibility code in 
tools/server-side/svn-backup-dumps.py. It is tested with python 2.3, but i 
think it works with older ones too.

Martin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: [Svnmerge] Re: gnome stuck on cvs2svn

Posted by Blair Zajac <bl...@orcaware.com>.
Giovanni Bajo wrote:
> Ben Collins-Sussman <su...@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.

If you're in the mood, contrib/server-side/svn-fast-backup could use a little 
backport effort :)

Just joking, but it uses subprocess which is distributed with Python 2.4 and all 
the RHEL3 and RHEL4 systems have older OSes.

Regards,
Blair

-- 
Blair Zajac, Ph.D.
<bl...@orcaware.com>
Subversion training, consulting and support
http://www.orcaware.com/svn/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: gnome stuck on cvs2svn

Posted by Michael Haggerty <mh...@alum.mit.edu>.
Giovanni Bajo wrote:
> Ben Collins-Sussman <su...@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

Re: gnome stuck on cvs2svn

Posted by Marcus Rueckert <da...@web.de>.
On 2006-04-21 01:28:45 +0200, Giovanni Bajo wrote:
> (<cough>RHEL3</cough).

oooooooooold?

> 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.

really? you can happily run the conversion on every other box and copy
it back to your RHEL3 box. either as dumpfile or as fsfs repository.
so i dont really see a reason for keeping compat with so old versions.

2.3. was released 2003-07-29
2.4  was released 2004-12-06

just my 2 cents

    darix

-- 
           openSUSE - SUSE Linux is my linux
               openSUSE is good for you
                   www.opensuse.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: gnome stuck on cvs2svn

Posted by Daniel Berlin <db...@dberlin.org>.
> 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.

I'd be more inclined to agree with you if 2.3 wasn't almost 3 years
old :)




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: gnome stuck on cvs2svn

Posted by Giovanni Bajo <ra...@develer.com>.
Ben Collins-Sussman <su...@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.

Giovanni Bajo


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: gnome stuck on cvs2svn

Posted by Eric Gillespie <ep...@pretzelnet.org>.
"Ben Collins-Sussman" <su...@red-bean.com> writes:

> Pathological Case in their RCS files.  Apparently there was some
> horrible time-clock skew in their server at some point, and cvs2svn
> doesn't know how to handle that particular pathology yet, so some svn
> commits are appearing out-of-order.

Ouch.  Is Subversion afflicted by the same problem?  It can check
that the svn:date it generates (both times) is greater than the
one on which the transaction is based.  Does it already do this?
Should it?

-- 
Eric Gillespie <*> epg@pretzelnet.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org