You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by lo...@reddwarf.xs4all.nl on 2002/04/02 00:00:56 UTC

cvs2svn

hello,

I'm trying to get cvs2svn.py to work, but it dumps core. the problem seems to
be in the swig-generated _wrap_svn_fs_apply_textdelta(), where it says:

  void **arg2 ;

  ... nothing done to arg2 ...

  result = (svn_error_t *)svn_fs_apply_textdelta(arg1,arg2,arg3,(char const *)arg4,arg5);

and then in svn_fs_apply_textdelta():

  *contents_baton_p = tb;

and there it goes. is this a bug or is cvs2svn as a whole not supposed to be
functional yet anyway?

svn is current, swig is 1.3, python 2.1.

thanks,
Lodewijk

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

Re: cvs2svn

Posted by Lodewijk Voge <lo...@reddwarf.xs4all.nl>.
On Mon, Apr 01, 2002 at 04:20:38PM -0800, you wrote:

  > Upgrade to SWIG 1.3.11 and try again. We need a very recent SWIG to work
  > correctly. Once you do that, then cvs2svn should work reasonably well.

oops, I claimed 1.3 because that's the debian package name. it actually is
1.3.11 already.

I'll check out the cvs version and see if that helps. it does seem to be a
swig problem to my untrained eye, given that svn_fs.i does declare void ** as
an out parameter but the generated code doesn't allocate storage for it.

Lodewijk

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

Re: cvs2svn

Posted by Garrett Rooney <ro...@electricjellyfish.net>.
On Sat, Apr 06, 2002 at 07:34:31PM -0800, Blair Zajac wrote:
> Daniel Berlin wrote:
> > 
> > On Sat, 6 Apr 2002, Blair Zajac wrote:
> > > If anybody tells me the steps, I can write the HOWO-TO and check it
> > > in.
> > 
> > Install swig 1.3.11
> > Install python 2.2 (Probably 1.5.2+ would work fine, i just happen to have
> > 2.2, and haven't tried older versions)
> > Install rcsparse from viewcvs (this is the part that sucks right now)
> > into either the same dir as cvs2svn.py, or in the python module path so
> > that "import rcsparse" picks it up properly.
> 
> I've done all that, but don't you need to run swig on the files in
> 
> svn/subversion/bindings/swig
> 
> When I run
> 
> % cd svn/subversion/bindings/swig
> % swig -python *i
> swig error : Unrecognized option apr.i
> swig error : Unrecognized option svn_client.i
> swig error : Unrecognized option svn_delta.i
> swig error : Unrecognized option svn_fs.i
> swig error : Unrecognized option svn_ra.i
> swig error : Unrecognized option svn_repos.i
> swig error : Unrecognized option svn_string.i
> swig error : Unrecognized option svn_types.i
> swig error : Unrecognized option svn_wc.i
> Use 'swig -help' for available options.

try rerunning configure now that you have swig installed.  it should
pick up on the presence of swig and build the swig bindings as a part
of the normal build.  at least it did when i had swig installed on my
machine, although i never actually tried the bindings.

-garrett 

-- 
garrett rooney                    Remember, any design flaw you're 
rooneg@electricjellyfish.net      sufficiently snide about becomes  
http://electricjellyfish.net/     a feature.       -- Dan Sugalski

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

Re: cvs2svn

Posted by Daniel Berlin <da...@dberlin.org>.
On Sat, 6 Apr 2002, Blair Zajac wrote:

> Daniel Berlin wrote:
> > 
> > On Sat, 6 Apr 2002, Blair Zajac wrote:
> > > If anybody tells me the steps, I can write the HOWO-TO and check it
> > > in.
> > 
> > Install swig 1.3.11
> > Install python 2.2 (Probably 1.5.2+ would work fine, i just happen to have
> > 2.2, and haven't tried older versions)
> > Install rcsparse from viewcvs (this is the part that sucks right now)
> > into either the same dir as cvs2svn.py, or in the python module path so
> > that "import rcsparse" picks it up properly.
> 
> I've done all that, but don't you need to run swig on the files in
No, run "python setup.py install" in the python subdir

> 
> svn/subversion/bindings/swig
> 
> When I run
> 
> % cd svn/subversion/bindings/swig
> % swig -python *i
> swig error : Unrecognized option apr.i
> swig error : Unrecognized option svn_client.i
> swig error : Unrecognized option svn_delta.i
> swig error : Unrecognized option svn_fs.i
> swig error : Unrecognized option svn_ra.i
> swig error : Unrecognized option svn_repos.i
> swig error : Unrecognized option svn_string.i
> swig error : Unrecognized option svn_types.i
> swig error : Unrecognized option svn_wc.i
> Use 'swig -help' for available options.
> 
> Also, when I run cvs2svn.py:
> 
> % python2 cvs2svn.py
> Traceback (most recent call last):
>   File "cvs2svn.py", line 17, in ?
>     from svn import fs, util, _delta, _repos
> ImportError: No module named svn

The "python setup.py install" will take care of this.

> 
> Best,
> Blair
> 
> 


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

Re: cvs2svn

Posted by Blair Zajac <bl...@orcaware.com>.
Daniel Berlin wrote:
> 
> On Sat, 6 Apr 2002, Blair Zajac wrote:
> > If anybody tells me the steps, I can write the HOWO-TO and check it
> > in.
> 
> Install swig 1.3.11
> Install python 2.2 (Probably 1.5.2+ would work fine, i just happen to have
> 2.2, and haven't tried older versions)
> Install rcsparse from viewcvs (this is the part that sucks right now)
> into either the same dir as cvs2svn.py, or in the python module path so
> that "import rcsparse" picks it up properly.

I've done all that, but don't you need to run swig on the files in

svn/subversion/bindings/swig

When I run

% cd svn/subversion/bindings/swig
% swig -python *i
swig error : Unrecognized option apr.i
swig error : Unrecognized option svn_client.i
swig error : Unrecognized option svn_delta.i
swig error : Unrecognized option svn_fs.i
swig error : Unrecognized option svn_ra.i
swig error : Unrecognized option svn_repos.i
swig error : Unrecognized option svn_string.i
swig error : Unrecognized option svn_types.i
swig error : Unrecognized option svn_wc.i
Use 'swig -help' for available options.

Also, when I run cvs2svn.py:

% python2 cvs2svn.py
Traceback (most recent call last):
  File "cvs2svn.py", line 17, in ?
    from svn import fs, util, _delta, _repos
ImportError: No module named svn

Best,
Blair

-- 
Blair Zajac <bl...@orcaware.com>
Web and OS performance plots - http://www.orcaware.com/orca/

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

Re: cvs2svn

Posted by Daniel Berlin <da...@dberlin.org>.
On Sat, 6 Apr 2002, Blair Zajac wrote:

> Brian Huddleston wrote:
> > ----- Original Message -----
> > From: "Greg Stein" <gs...@lyra.org>
> > To: <lo...@reddwarf.xs4all.nl>
> > Cc: <de...@subversion.tigris.org>
> > Sent: Monday, April 01, 2002 6:20 PM
> > Subject: Re: cvs2svn
> > 
> > > Upgrade to SWIG 1.3.11 and try again. We need a very recent SWIG to work
> > > correctly. Once you do that, then cvs2svn should work reasonably well.
> > (I've
> > > test-converted several repositories, and Daniel Berlin has been doing a
> > > bunch of conversions with the current code)
> > >
> > > Cheers,
> > > -g
> > >
> > > --
> > > Greg Stein, http://www.lyra.org/
> > 
> > Has anyone had time to write up a short HOW-TO on playing with this
> > (cvs2svn)?  I am afraid I am dirt ignorant when it comes to Python and SWIG,
> > but I would love to play with my current CVS repository in svn.
> > 
> > Thanks.
> > -Brian
> 
> I could use one too.
> 
> If anybody tells me the steps, I can write the HOWO-TO and check it
> in.

Install swig 1.3.11
Install python 2.2 (Probably 1.5.2+ would work fine, i just happen to have 
2.2, and haven't tried older versions)
Install rcsparse from viewcvs (this is the part that sucks right now) 
into either the same dir as cvs2svn.py, or in the python module path so 
that "import rcsparse" picks it up properly.

That should do it.

> 
> Also, is cvs2svn.py the preferred method now over cvs2svn.pl?

I would think so.

> 
> Best,
> Blair
> 
> 


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

Re: cvs2svn

Posted by Blair Zajac <bl...@orcaware.com>.
Brian Huddleston wrote:
> ----- Original Message -----
> From: "Greg Stein" <gs...@lyra.org>
> To: <lo...@reddwarf.xs4all.nl>
> Cc: <de...@subversion.tigris.org>
> Sent: Monday, April 01, 2002 6:20 PM
> Subject: Re: cvs2svn
> 
> > Upgrade to SWIG 1.3.11 and try again. We need a very recent SWIG to work
> > correctly. Once you do that, then cvs2svn should work reasonably well.
> (I've
> > test-converted several repositories, and Daniel Berlin has been doing a
> > bunch of conversions with the current code)
> >
> > Cheers,
> > -g
> >
> > --
> > Greg Stein, http://www.lyra.org/
> 
> Has anyone had time to write up a short HOW-TO on playing with this
> (cvs2svn)?  I am afraid I am dirt ignorant when it comes to Python and SWIG,
> but I would love to play with my current CVS repository in svn.
> 
> Thanks.
> -Brian

I could use one too.

If anybody tells me the steps, I can write the HOWO-TO and check it
in.

Also, is cvs2svn.py the preferred method now over cvs2svn.pl?

Best,
Blair

-- 
Blair Zajac <bl...@orcaware.com>
Web and OS performance plots - http://www.orcaware.com/orca/

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

Re: cvs2svn

Posted by Brian Huddleston <br...@huddleston.net>.
Has anyone had time to write up a short HOW-TO on playing with this
(cvs2svn)?  I am afraid I am dirt ignorant when it comes to Python and SWIG,
but I would love to play with my current CVS repository in svn.

Thanks.
-Brian
----- Original Message -----
From: "Greg Stein" <gs...@lyra.org>
To: <lo...@reddwarf.xs4all.nl>
Cc: <de...@subversion.tigris.org>
Sent: Monday, April 01, 2002 6:20 PM
Subject: Re: cvs2svn


> On Tue, Apr 02, 2002 at 02:00:56AM +0200, lodewijk@reddwarf.xs4all.nl
wrote:
> >...
> > and there it goes. is this a bug or is cvs2svn as a whole not supposed
to be
> > functional yet anyway?
>
> cvs2svn isn't quite "ready" yet; partly based on its own code, but partly
> based on the swig stuff. We have some more robustness issues to deal with
> for the conversion process.
>
> > svn is current, swig is 1.3, python 2.1.
>
> Upgrade to SWIG 1.3.11 and try again. We need a very recent SWIG to work
> correctly. Once you do that, then cvs2svn should work reasonably well.
(I've
> test-converted several repositories, and Daniel Berlin has been doing a
> bunch of conversions with the current code)
>
> Cheers,
> -g
>
> --
> Greg Stein, http://www.lyra.org/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
>



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

Re: cvs2svn

Posted by Greg Stein <gs...@lyra.org>.
On Tue, Apr 02, 2002 at 02:00:56AM +0200, lodewijk@reddwarf.xs4all.nl wrote:
>...
> and there it goes. is this a bug or is cvs2svn as a whole not supposed to be
> functional yet anyway?

cvs2svn isn't quite "ready" yet; partly based on its own code, but partly
based on the swig stuff. We have some more robustness issues to deal with
for the conversion process.

> svn is current, swig is 1.3, python 2.1.

Upgrade to SWIG 1.3.11 and try again. We need a very recent SWIG to work
correctly. Once you do that, then cvs2svn should work reasonably well. (I've
test-converted several repositories, and Daniel Berlin has been doing a
bunch of conversions with the current code)

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/

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