headers
David Summers | 2 Feb 2004 18:34
Picon

Successful conversion of 10.5 Gig CVS repository


I'd like to report my (finally) succesful conversion of my 10.5 Gigabyte 
CVS repository to Subversion.  I tried again about 1 or 2 weeks ago and 
got cvs2svn errors, but evidently some changes in cvs2svn this last week 
fixed the remaining problems (that I was having) and I finally got my 
repository to convert and load this last Friday.  I've tried about 4-5 
times beginning this last summer and ran into various problems each time.

Statistics:
===========

CVS Repository: ~10.5 Gigabytes
SVN Repository: ~10 Gigabytes
Total Commits: 7754 (spanning from 2000-04-05 to present)
Working Copy: ~6 Gigabytes
Conversion Time: ~10 hours

My supervisor has told me he won't consider Subversion until it hits 1.0 
so I'm getting everything in place to present him with the 
advantages/disadvantages of converting to Subversion and showing him a 
working demonstration from a snapshot of our CVS repository taken last 
week.

  Thanks to Karl and everyone else on the team for the hard work and great 
software!

--

-- 
David Wayne Summers          "Linux: Because reboots are for hardware upgrades!"
david <at> summersoft.fay.ar.us   PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
PGP Key fingerprint =  C0 E0 4F 50 DD A9 B6 2B  60 A1 31 7E D2 28 6D A8
(Continue reading)

Permalink | Reply | 0 comments |
headers
kfogel | 3 Feb 2004 21:28
Favicon

Re: Successful conversion of 10.5 Gig CVS repository

David Summers <david <at> summersoft.fay.ar.us> writes:
> I'd like to report my (finally) succesful conversion of my 10.5 Gigabyte 
> CVS repository to Subversion.  I tried again about 1 or 2 weeks ago and 
> got cvs2svn errors, but evidently some changes in cvs2svn this last week 
> fixed the remaining problems (that I was having) and I finally got my 
> repository to convert and load this last Friday.  I've tried about 4-5 
> times beginning this last summer and ran into various problems each time.

Thanks for the report!

Note that some of the remaining cvs2svn bugs are about correctness of
branch/tag deduction.  You might not notice such problems until you go
back to dig into old history.  So even though it "succeeds" now, you
should still be cautious until all the 'cvs2svn-1.0' bugs are fixed.

-Karl
Permalink | Reply | 0 comments |
headers
David Summers | 3 Feb 2004 22:39
Picon

Re: Successful conversion of 10.5 Gig CVS repository


On 3 Feb 2004 kfogel <at> collab.net wrote:
> David Summers <david <at> summersoft.fay.ar.us> writes:
> > I'd like to report my (finally) succesful conversion of my 10.5 Gigabyte 
> > CVS repository to Subversion.  I tried again about 1 or 2 weeks ago and 
> > got cvs2svn errors, but evidently some changes in cvs2svn this last week 
> > fixed the remaining problems (that I was having) and I finally got my 
> > repository to convert and load this last Friday.  I've tried about 4-5 
> > times beginning this last summer and ran into various problems each time.
> 
> Thanks for the report!
> 
> Note that some of the remaining cvs2svn bugs are about correctness of
> branch/tag deduction.  You might not notice such problems until you go
> back to dig into old history.  So even though it "succeeds" now, you
> should still be cautious until all the 'cvs2svn-1.0' bugs are fixed.
> 

Will do, thanks for the heads up.

--

-- 
David Wayne Summers          "Linux: Because reboots are for hardware upgrades!"
david <at> summersoft.fay.ar.us   PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
PGP Key fingerprint =  C0 E0 4F 50 DD A9 B6 2B  60 A1 31 7E D2 28 6D A8
Permalink | Reply | 0 comments |
headers
Kai Bartels | 5 Feb 2004 13:30
Picon
Favicon

Re: [w] Re: cvs2svn.py takes long but sleeps?

Hi *!

I had another try with revision 8547 of cvs2svn.py and the behaviour is
basicly the same. :^(
I think it's pass 5 that takes up the time. The first commits are fast,
but it has reached commit 19xxx now and each file in a commit, even the
small ones take about 30 seconds where the machine seems to do
nothing at all. (NB: I think the nfs mount is not used in pass 5.)

Maybe it's the bigger number of commits that slow down cvs2svn, or
subversion itself??

I get kind of a stack trace when I cancel the process; I append both
(the 7921 and the 8547) stack trace below, maybe someone has an idea
when looking over them!?

Regards, Kai

On Mon, Feb 02, 2004 at 11:34:26AM -0600, David Summers wrote:
> 
> I'd like to report my (finally) succesful conversion of my 10.5 Gigabyte 
> CVS repository to Subversion.  I tried again about 1 or 2 weeks ago and 
> got cvs2svn errors, but evidently some changes in cvs2svn this last week 
> fixed the remaining problems (that I was having) and I finally got my 
> repository to convert and load this last Friday.  I've tried about 4-5 
> times beginning this last summer and ran into various problems each time.
> 
> Statistics:
> ===========
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ben Collins-Sussman | 6 Feb 2004 17:58
Favicon

Dispelling Subversion FUD

On Wed, 2004-01-28 at 22:18, Greg Hudson wrote:

> Ben has been working on collecting together anti-Subversion commentary

...because for the last couple of weeks, I've been writing a short
document that tries to dispel some of the more common FUD I've heard
about Subversion.  Here's the essay, link freely and often to it:

   http://www.red-bean.com/sussman/svn-anti-fud.html
Permalink | Reply | 0 comments |
headers
Gareth McCaughan | 7 Feb 2004 11:50
Picon
Favicon

Re: Dispelling Subversion FUD

On Friday 06 February 2004 4:58 pm, Ben Collins-Sussman wrote:

>    http://www.red-bean.com/sussman/svn-anti-fud.html

Very nice. But you probably didn't quite mean it to say

  | A well-functioning system should need its repository "hacked".

:-)

--

-- 
g
Permalink | Reply | 0 comments |
headers
Christian Schaffner | 9 Feb 2004 18:33
Picon

ANN: Fink Packages for Subversion 0.37.0 Released

The fink (<http://fink.sf.net>) packages are now available for the 
latest version of svn:

<http://fink.sourceforge.net/pdb/search.php?s=svn>

To get the latest package descriptions type 'fink selfupdate'.

To use the client: 'fink install svn-client-ssl'
To use the stand-alone server: 'fink install svn-ssl'
To use the apache server: 'fink install libapache2-ssl-mod-svn'
To use the cvs2svn conversion tool: 'fink install cvs2svn-ssl'

The swig perl and python bindings are now also available. See 'fink 
list svn' for all packages.

For general questions about fink (e.g. regarding getting the latest 
package) please write to
<mailto:fink-users <at> lists.sourceforge.net>

Note that the svn Fink package is still in the unstable tree.  To 
enable it, please read the Fink FAQ:
<http://fink.sourceforge.net/faq/usage-fink.php#unstable>

PS: Some info about unstable/stable fink packages and subversion in 
Fink:

One of Finks goals is to provide binary packages. But the policy is to 
only provide binaries of packages in the stable tree. Subversion is not 
yet in the stable tree of Fink, since it didn't hit 1.0 yet. So, what 
you are doing right now is beta testing a beta package for a beta
(Continue reading)

Permalink | Reply | 0 comments |
headers
Christian Schaffner | 9 Feb 2004 18:33
Picon

ANN: Fink Packages for Subversion 0.37.0 Released

The fink (<http://fink.sf.net>) packages are now available for the 
latest version of svn:

<http://fink.sourceforge.net/pdb/search.php?s=svn>

To get the latest package descriptions type 'fink selfupdate'.

To use the client: 'fink install svn-client-ssl'
To use the stand-alone server: 'fink install svn-ssl'
To use the apache server: 'fink install libapache2-ssl-mod-svn'
To use the cvs2svn conversion tool: 'fink install cvs2svn-ssl'

The swig perl and python bindings are now also available. See 'fink 
list svn' for all packages.

For general questions about fink (e.g. regarding getting the latest 
package) please write to
<mailto:fink-users <at> lists.sourceforge.net>

Note that the svn Fink package is still in the unstable tree.  To 
enable it, please read the Fink FAQ:
<http://fink.sourceforge.net/faq/usage-fink.php#unstable>

PS: Some info about unstable/stable fink packages and subversion in 
Fink:

One of Finks goals is to provide binary packages. But the policy is to 
only provide binaries of packages in the stable tree. Subversion is not 
yet in the stable tree of Fink, since it didn't hit 1.0 yet. So, what 
you are doing right now is beta testing a beta package for a beta
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mike Javorski | 11 Feb 2004 01:45

RE: RE: "not under version control" error - continued

Any news on this issue? There has been another occurrence of this merge bug reported by Adam Lackorzynski in
the dev list (http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=56106)

I am starting to get a bit concerned here.. Merge is a core function for any version control system; if the
problem stems from something deeper this could be an even bigger issue, and 1.0 is suppposed to be just
around the corner.. 

I have several people that want to start using our repository and I can't safely let them do that at the moment
if their data is being corrupted (possibly)..

I would really appreciate any help you all can give.. Please let me know if there is any further details that
would help to diagnose the problem. 

Thanks,

- Mike

-----Original Message-----
From: Mike Javorski 
Sent: Wednesday, February 04, 2004 3:05 PM
To: users <at> subversion.tigris.org
Subject: RE: "not under version control" error - continued

Anyone have any ideas? Need more info? 

Anyone.... Anyone.... Bueller..... :-D

- Mike

-----Original Message-----
(Continue reading)

Permalink | Reply | 0 comments |
headers
Philip Martin | 11 Feb 2004 02:08
Picon

Re: "not under version control" error - continued

"Mike Javorski" <mjavorski <at> spokesoftware.com> writes:

> Any news on this issue? There has been another occurrence of this
> merge bug reported by Adam Lackorzynski in the dev list
> (http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=56106)

It's still a bug.  The dry-run merge doesn't handle properties on
added files.  Is there an issue in the issue tracker?  If not, you
should raise one.

$ svnadmin create repo
$ svn co file://`pwd`/repo wc
$ svn mkdir wc/foo wc/bar
$ svn ci -m "" wc
$ touch wc/foo/zig
$ svn add wc/foo/zig
$ svn ps x x wc/foo/zig
$ svn ci -m "" wc
$ svn merge --dry-run -r1:head file://`pwd`/repo/foo wc/bar
../svn/subversion/clients/cmdline/delete-cmd.c:47: (apr_err=200005)
svn: Use --force to override this restriction
../svn/subversion/libsvn_wc/props.c:279: (apr_err=200005)
svn: 'wc/bar/zig' is not under version control
$ svn merge -r1:head file://`pwd`/repo/foo wc/bar
A  wc/bar/zig

--

-- 
Philip Martin
Permalink | Reply | 0 comments |

Gmane