You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Rob Weir <ro...@apache.org> on 2011/10/14 23:32:44 UTC

Legacy OOo SVN

I want to make sure we're not duplicating effort here.  I've been
working with Pedro to take the legacy OOo SVN repository (pre Hg) and
get it onto Apache-Extras.  I'm doing this via svnsync, a slow
process, but it will preserve the revision history.

It should be done in a few more days.

We should think about putting a link to this repository, along with a
link to the back up Hg repository, on our website here:

http://incubator.apache.org/openofficeorg/source.html

It should probably have a suitable disclaimer that this is the legacy
code, not the project's code, not ALv2, etc., but having access to the
history is useful.

I'm told that before SVN the project used CVS.  Is it worth backing
that up as well?

-Rob

Re: Legacy OOo SVN

Posted by Maho NAKATA <ch...@mac.com>.
From: Andrea Pescetti <pe...@openoffice.org>
Subject: Re: Legacy OOo SVN
Date: Mon, 17 Oct 2011 09:49:48 +0200

> On 17/10/2011 Maho NAKATA wrote:
>> From: Rob Weir
>>> I'm told that before SVN the project used CVS.  Is it worth backing
>>> that up as well?
>> Yes, sure. Some projects like native lang projects
>> are not covered by SVN.
> 
> What exactly is not covered by SVN in the Native-Lang projects? The
> Italian N-L project used CVS for the website content only, but that
> one was converted to SVN (a fresh import, dropping all history) with
> the Kenai migration and it is still working correctly.

Oh - I forgot that. Some of the history of NLs are dropped...

thanks
-- Nakata Maho http://accc.riken.jp/maho/ , JA OOO http://ja.openoffice.org/
http://blog.goo.ne.jp/nakatamaho/ ,GPG: http://accc.riken.jp/maho/maho.pgp.txt

Re: Legacy OOo SVN

Posted by Andrea Pescetti <pe...@openoffice.org>.
On 17/10/2011 Maho NAKATA wrote:
> From: Rob Weir
>> I'm told that before SVN the project used CVS.  Is it worth backing
>> that up as well?
> Yes, sure. Some projects like native lang projects
> are not covered by SVN.

What exactly is not covered by SVN in the Native-Lang projects? The 
Italian N-L project used CVS for the website content only, but that one 
was converted to SVN (a fresh import, dropping all history) with the 
Kenai migration and it is still working correctly.

Is there anything that is still under CVS and that we should backup?

Regards,
   Andrea.

Re: Legacy OOo SVN

Posted by Maho NAKATA <ma...@apache.org>.
From: Rob Weir <ro...@apache.org>
Subject: Legacy OOo SVN
Date: Fri, 14 Oct 2011 17:32:44 -0400

> I want to make sure we're not duplicating effort here.  I've been
> working with Pedro to take the legacy OOo SVN repository (pre Hg) and
> get it onto Apache-Extras.  I'm doing this via svnsync, a slow
> process, but it will preserve the revision history.
> 
> It should be done in a few more days.
> 
> We should think about putting a link to this repository, along with a
> link to the back up Hg repository, on our website here:
> 
> http://incubator.apache.org/openofficeorg/source.html
> 
> It should probably have a suitable disclaimer that this is the legacy
> code, not the project's code, not ALv2, etc., but having access to the
> history is useful.
> 
> I'm told that before SVN the project used CVS.  Is it worth backing
> that up as well?
Yes, sure. Some projects like native lang projects
are not covered by SVN.

thanks




Re: Legacy OOo SVN

Posted by Maho NAKATA <ch...@mac.com>.
From: Rob Weir <ro...@apache.org>
Subject: Legacy OOo SVN
Date: Fri, 14 Oct 2011 17:32:44 -0400

> I want to make sure we're not duplicating effort here.  I've been
> working with Pedro to take the legacy OOo SVN repository (pre Hg) and
> get it onto Apache-Extras.  I'm doing this via svnsync, a slow
> process, but it will preserve the revision history.
> 
> It should be done in a few more days.
> 
> We should think about putting a link to this repository, along with a
> link to the back up Hg repository, on our website here:
> 
> http://incubator.apache.org/openofficeorg/source.html
> 
> It should probably have a suitable disclaimer that this is the legacy
> code, not the project's code, not ALv2, etc., but having access to the
> history is useful.
> 
> I'm told that before SVN the project used CVS.  Is it worth backing
> that up as well?
Yes, sure. Some projects like native lang projects
are not covered by SVN.

thanks




Re: Legacy OOo SVN

Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Rob Weir wrote on Sun, Oct 16, 2011 at 18:34:33 -0400:
> On Sun, Oct 16, 2011 at 3:40 PM, Daniel Shahaf <d....@daniel.shahaf.name> wrote:
> > Daniel Shahaf wrote on Sun, Oct 16, 2011 at 21:39:12 +0200:
> >> svnrdump dump -r 49548 $SOURCE_REPOS > 1
> >> ed 1
> >> svnrdump load $TARGET_REPOS < 1
> >> svn pl --revprop -r0 $TARGET_REPOS
> >> [ edit the svn:sync-* revprops ]
> >>
> >> I like this idiom :-)
> >>
> >
> > svnrdump is available in Subversion 1.7 and newer.
> >
> 
> Cool, remote dumps.   Is a 1.7 client sufficient,

1.7 client, 1.4/1.5 source server, 1.0(?) target server.

http://subversion.apache.org/docs/release-notes/1.7

(Ignore the stuff about race conditions, it doesn't apply in your use case)

Re: Legacy OOo SVN

Posted by Rob Weir <ro...@apache.org>.
On Sun, Oct 16, 2011 at 3:40 PM, Daniel Shahaf <d....@daniel.shahaf.name> wrote:
> Daniel Shahaf wrote on Sun, Oct 16, 2011 at 21:39:12 +0200:
>> svnrdump dump -r 49548 $SOURCE_REPOS > 1
>> ed 1
>> svnrdump load $TARGET_REPOS < 1
>> svn pl --revprop -r0 $TARGET_REPOS
>> [ edit the svn:sync-* revprops ]
>>
>> I like this idiom :-)
>>
>
> svnrdump is available in Subversion 1.7 and newer.
>

Cool, remote dumps.   Is a 1.7 client sufficient, or does this require
the server also be updated?  This is the legacy OOo SVN server, so
harder to get that upgraded.

In any case, I've started the create a local mirror.  At 13348/278112
now, so ~5% done.


-Rob

Re: Legacy OOo SVN

Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Daniel Shahaf wrote on Sun, Oct 16, 2011 at 21:39:12 +0200:
> svnrdump dump -r 49548 $SOURCE_REPOS > 1
> ed 1
> svnrdump load $TARGET_REPOS < 1
> svn pl --revprop -r0 $TARGET_REPOS
> [ edit the svn:sync-* revprops ]
> 
> I like this idiom :-)
> 

svnrdump is available in Subversion 1.7 and newer.

Re: Legacy OOo SVN

Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Rob Weir wrote on Sun, Oct 16, 2011 at 15:33:36 -0400:
> On Sun, Oct 16, 2011 at 11:50 AM, Pedro Giffuni <pf...@apache.org> wrote:
> >
> >
> > --- On Sun, 10/16/11, Rob Weir <ro...@apache.org> wrote:
> > ...
> >>
> >> The sync has died.  Stuck on this error:
> >>
> > :(
> >
> >>
> >> The next revision has a huge memo, over 1MB long:
> >>
> >> svn log -r 49548 http://svn.services.openoffice.org/ooo/
> >>
> >> I wonder if that is the problem.
> >>
> >> I can't fix this on my end, at least not that I can
> >> see.  I need someone who can change the memo for
> >> revision 49548 in the legacy SVN.
> >>
> >
> > I think the dump is editable, I read so in the SVN
> > handbook.
> >
> 
> I don't have a dump.  I was doing an svnsync directly from legacy SVN
> (read-only to me) to the Google Code repository.
> 
> The other approach is to do this in two steps:  mirror locally, and
> then svnsync that to Google.  That would give more flexibility, since
> I can correct any issues like this on my local repository.
> 

svnrdump dump -r 49548 $SOURCE_REPOS > 1
ed 1
svnrdump load $TARGET_REPOS < 1
svn pl --revprop -r0 $TARGET_REPOS
[ edit the svn:sync-* revprops ]

I like this idiom :-)


Re: Legacy OOo SVN

Posted by Rob Weir <ro...@apache.org>.
On Sun, Oct 16, 2011 at 11:50 AM, Pedro Giffuni <pf...@apache.org> wrote:
>
>
> --- On Sun, 10/16/11, Rob Weir <ro...@apache.org> wrote:
> ...
>>
>> The sync has died.  Stuck on this error:
>>
> :(
>
>>
>> The next revision has a huge memo, over 1MB long:
>>
>> svn log -r 49548 http://svn.services.openoffice.org/ooo/
>>
>> I wonder if that is the problem.
>>
>> I can't fix this on my end, at least not that I can
>> see.  I need someone who can change the memo for
>> revision 49548 in the legacy SVN.
>>
>
> I think the dump is editable, I read so in the SVN
> handbook.
>

I don't have a dump.  I was doing an svnsync directly from legacy SVN
(read-only to me) to the Google Code repository.

The other approach is to do this in two steps:  mirror locally, and
then svnsync that to Google.  That would give more flexibility, since
I can correct any issues like this on my local repository.

> Pedro.
>
>

Re: Legacy OOo SVN

Posted by Pedro Giffuni <pf...@apache.org>.

--- On Sun, 10/16/11, Rob Weir <ro...@apache.org> wrote:
...
> 
> The sync has died.  Stuck on this error:
> 
:(

> 
> The next revision has a huge memo, over 1MB long:
> 
> svn log -r 49548 http://svn.services.openoffice.org/ooo/
> 
> I wonder if that is the problem.
> 
> I can't fix this on my end, at least not that I can
> see.  I need someone who can change the memo for
> revision 49548 in the legacy SVN.
> 

I think the dump is editable, I read so in the SVN
handbook.

Pedro.


Re: Legacy OOo SVN

Posted by Rob Weir <ro...@apache.org>.
On Sat, Oct 15, 2011 at 1:09 PM, Pedro Giffuni <pf...@apache.org> wrote:
>
> --- On Fri, 10/14/11, Rob Weir <ro...@apache.org> wrote:
> ...
>> I want to make sure we're not duplicating effort here.
>> I've been working with Pedro to take the legacy OOo SVN
>> repository (pre Hg) and get it onto Apache-Extras.
>> I'm doing this via svnsync, a slow
>> process, but it will preserve the revision history.
>>
>
> All the credit here is Rob's: getting a dump and
> uploading didn't seem to be much fun with my current
> ISP.
>
>> It should be done in a few more days.
>>
>
> In more than week, at the current rate, but still it's
> worth it. I am not sure if support for MySpell and
> Xalan is still buried there somewhere but in theory
> there is some stuff there that may have been otherwise
> lost during the Hg migration.
>

The sync has died.  Stuck on this error:

svnsync: At least one property change failed; repository is unchanged
svnsync: Server sent unexpected return value (413 Request Entity Too
Large) in response to PROPPATCH request for
'/a/apache-extras.org/ooo-legacy-svn/!svn/wbl/c7796956-b4eb-495d-88e0-d1d07d116ca0/49547'

The next revision has a huge memo, over 1MB long:

svn log -r 49548 http://svn.services.openoffice.org/ooo/

I wonder if that is the problem.

I can't fix this on my end, at least not that I can see.  I need
someone who can change the memo for revision 49548 in the legacy SVN.

-Rob


>> I'm told that before SVN the project used CVS.  Is it
>> worth backing that up as well?
>>
>
> I have no idea where the CVS stuff may be available but
> apache-extras doesn't support CVS and it's probably not
> worth the try anyways.
>
> The bitbucket Hg repository looks rather nice: we should
> probably sanction it the "official" historical archive.
> Actually .. "the unofficial historical OOo archive"
> sounds great too :).
>
> Pedro.
>
>

Re: Legacy OOo SVN

Posted by Jens-Heiner Rechtien <jh...@web.de>.
Hi Michael,

On 10/16/2011 09:23 AM, Michael Stahl wrote:
> On 15.10.2011 19:49, Rob Weir wrote:
>> On Sat, Oct 15, 2011 at 1:09 PM, Pedro Giffuni<pf...@apache.org>  wrote:
>>>
>>> --- On Fri, 10/14/11, Rob Weir<ro...@apache.org>  wrote:
>>> ...
>>>> I want to make sure we're not duplicating effort here.
>>>> I've been working with Pedro to take the legacy OOo SVN
>>>> repository (pre Hg) and get it onto Apache-Extras.
>>>> I'm doing this via svnsync, a slow
>>>> process, but it will preserve the revision history.
>
> sounds good; there are even still some non-integrated CWSes in there, but
> probably these are by now so outdated that they aren't of much interest.
>
>>> In more than week, at the current rate, but still it's
>>> worth it. I am not sure if support for MySpell and
>>> Xalan is still buried there somewhere but in theory
>>> there is some stuff there that may have been otherwise
>>> lost during the Hg migration.
>>>
>>>> I'm told that before SVN the project used CVS.  Is it
>>>> worth backing that up as well?
>>>
>>> I have no idea where the CVS stuff may be available but
>>> apache-extras doesn't support CVS and it's probably not
>>> worth the try anyways.
>>
>> It is probably not useful for the project, at least directly.  But I
>> was contacted by someone off list who said it might be good to have a
>> back up as a reference, for IP reasons.  This kind of make sense.  It
>> shows the provenance of the code, and it also establish an earlier
>> data (back to 2000, right?) for publication of the code.  This is
>> useful as prior art.
>
> keep in mind that the CVS repo is pretty darn enormous, Heiner said
> something about 90G:
>
> http://mail-archives.apache.org/mod_mbox/incubator-ooo-dev/201106.mbox/%3C4E05D910.5070502@web.de%3E
>

A naive conversion of the CVS repository to SVN would have resulted in a 
90 GiB repository or so. The CVS repository was, AFAIR about 7 GiB for 
source modules only, or was it 9 GiB? Can't remember exactly. Of course 
the old CVS repository was a huge mess with source code modules, 
national language modules and documentation intermingled. Maybe someone 
still has a CVSup copy of it.

Anyway, we did a pretty good job in preserving the history in the legacy 
SVN and the HG repository as far as code is concerned - at least for 
source files which were still active at the time of the legacy SVN 
conversion. I guess that would be sufficient to answer IP related questions.

>> What are our options if we wanted to back up the CVS, and preserve the
>> revision history?   Apache-Extras doesn't do CVS.
>
> hmm... converting to something non-CVS is probably not an option, because
> that would lose information (given the nature of CVS any large repo is a
> huge mess...).

Don't go there :-)

>
> perhaps mirror it with CVSup, make a tarball and upload that somewhere...
>
> probably nobody really wants to actually look at it, it's more of an
> "insurance" thing, right?


Regards,
   Heiner

-- 
Jens-Heiner Rechtien

Re: Legacy OOo SVN

Posted by Michael Stahl <ms...@openoffice.org>.
On 15.10.2011 19:49, Rob Weir wrote:
> On Sat, Oct 15, 2011 at 1:09 PM, Pedro Giffuni <pf...@apache.org> wrote:
>>
>> --- On Fri, 10/14/11, Rob Weir <ro...@apache.org> wrote:
>> ...
>>> I want to make sure we're not duplicating effort here.
>>> I've been working with Pedro to take the legacy OOo SVN
>>> repository (pre Hg) and get it onto Apache-Extras.
>>> I'm doing this via svnsync, a slow
>>> process, but it will preserve the revision history.

sounds good; there are even still some non-integrated CWSes in there, but
probably these are by now so outdated that they aren't of much interest.

>> In more than week, at the current rate, but still it's
>> worth it. I am not sure if support for MySpell and
>> Xalan is still buried there somewhere but in theory
>> there is some stuff there that may have been otherwise
>> lost during the Hg migration.
>>
>>> I'm told that before SVN the project used CVS.  Is it
>>> worth backing that up as well?
>>
>> I have no idea where the CVS stuff may be available but
>> apache-extras doesn't support CVS and it's probably not
>> worth the try anyways.
> 
> It is probably not useful for the project, at least directly.  But I
> was contacted by someone off list who said it might be good to have a
> back up as a reference, for IP reasons.  This kind of make sense.  It
> shows the provenance of the code, and it also establish an earlier
> data (back to 2000, right?) for publication of the code.  This is
> useful as prior art.

keep in mind that the CVS repo is pretty darn enormous, Heiner said
something about 90G:

http://mail-archives.apache.org/mod_mbox/incubator-ooo-dev/201106.mbox/%3C4E05D910.5070502@web.de%3E

> What are our options if we wanted to back up the CVS, and preserve the
> revision history?   Apache-Extras doesn't do CVS.

hmm... converting to something non-CVS is probably not an option, because
that would lose information (given the nature of CVS any large repo is a
huge mess...).

perhaps mirror it with CVSup, make a tarball and upload that somewhere...

probably nobody really wants to actually look at it, it's more of an
"insurance" thing, right?

regards,
 michael


Re: Legacy OOo SVN

Posted by Rob Weir <ro...@apache.org>.
On Sat, Oct 15, 2011 at 1:09 PM, Pedro Giffuni <pf...@apache.org> wrote:
>
> --- On Fri, 10/14/11, Rob Weir <ro...@apache.org> wrote:
> ...
>> I want to make sure we're not duplicating effort here.
>> I've been working with Pedro to take the legacy OOo SVN
>> repository (pre Hg) and get it onto Apache-Extras.
>> I'm doing this via svnsync, a slow
>> process, but it will preserve the revision history.
>>
>
> All the credit here is Rob's: getting a dump and
> uploading didn't seem to be much fun with my current
> ISP.
>
>> It should be done in a few more days.
>>
>
> In more than week, at the current rate, but still it's
> worth it. I am not sure if support for MySpell and
> Xalan is still buried there somewhere but in theory
> there is some stuff there that may have been otherwise
> lost during the Hg migration.
>
>> I'm told that before SVN the project used CVS.  Is it
>> worth backing that up as well?
>>
>
> I have no idea where the CVS stuff may be available but
> apache-extras doesn't support CVS and it's probably not
> worth the try anyways.
>

It is probably not useful for the project, at least directly.  But I
was contacted by someone off list who said it might be good to have a
back up as a reference, for IP reasons.  This kind of make sense.  It
shows the provenance of the code, and it also establish an earlier
data (back to 2000, right?) for publication of the code.  This is
useful as prior art.

What are our options if we wanted to back up the CVS, and preserve the
revision history?   Apache-Extras doesn't do CVS.

-Rob

> The bitbucket Hg repository looks rather nice: we should
> probably sanction it the "official" historical archive.
> Actually .. "the unofficial historical OOo archive"
> sounds great too :).
>
> Pedro.
>
>

Re: Legacy OOo SVN

Posted by Pedro Giffuni <pf...@apache.org>.
--- On Fri, 10/14/11, Rob Weir <ro...@apache.org> wrote:
...
> I want to make sure we're not duplicating effort here.
> I've been working with Pedro to take the legacy OOo SVN
> repository (pre Hg) and get it onto Apache-Extras.
> I'm doing this via svnsync, a slow
> process, but it will preserve the revision history.
> 

All the credit here is Rob's: getting a dump and
uploading didn't seem to be much fun with my current
ISP.

> It should be done in a few more days.
>

In more than week, at the current rate, but still it's
worth it. I am not sure if support for MySpell and
Xalan is still buried there somewhere but in theory
there is some stuff there that may have been otherwise
lost during the Hg migration.

> I'm told that before SVN the project used CVS.  Is it
> worth backing that up as well?
> 

I have no idea where the CVS stuff may be available but
apache-extras doesn't support CVS and it's probably not
worth the try anyways.

The bitbucket Hg repository looks rather nice: we should
probably sanction it the "official" historical archive.
Actually .. "the unofficial historical OOo archive"
sounds great too :).

Pedro.