[Tsp-devel] Re: [Savannah-announce] New recovery process

[Eric Noulard]

Sorry for the CERTI/TSP mixed previous message.
I do administrate those two projects on Savannah.org and may have
mixed messages.

Concerning TSP.
The TSP CVS has been recovered from the 27th May
complete backup.

I think this is OK for us, unless some commit have been done
between the 27th of may and the beginning of the outage
(somewhere during the day of 28th of May).

If any TSP developers knows that he/she has successfully commited something
after the 27th of May please redo the commit from your most up 2 date
local tree.
(cvs diffing from the current tree [for checking] + cvs ci should be enough)

Like I said in another message I want to begin a thread of discussion
concerning a switch from CVS to either GIT or Mercurial.
I want to do that but I'm currently lacking of time, so if anyone want to begin
before I do please go ahead.

I did begin to collect some references there:
http://www.simpy.com/group/5323

this is a totally open simpy group so feel free to add more
link in there.


2009/6/3 Eric Noulard <address@hidden>:
> Savannah hackers finally found a recent full backup
> they will be restoring from that one.
>
> I'll tell when CERTI @ Savannah is fully functionnal again.
>
> However I think we should really think of switching from CVS
> to other Distributed VCS, the 2 main choices are
>
> GIT and Mercurial (hg).
>
> I'll be preparing a message which sketch a comparison
> with pro- and cons with some external references.
>
>
>
>
> ---------- Forwarded message ----------
> From: Sylvain Beucler <address@hidden>
> Date: 2009/6/3
> Subject: [Savannah-announce] New recovery process
> To: address@hidden
> Cc : address@hidden
>
>
> To make things easier, we'll eventually recover all CVS/SVN from the
> May 27 backup, except for repositories that were already re-imported.
>
> If you have a pending (non-processed) request about importing an
> earlier backup, we'll ask you confirmation.
>
> If you already imported and want to switch back to the May 27 backup,
> submit a new request, saying that you want to replace the current
> repository.
>
>
> Status:
>
> - CVS: right now we're dealing with data copies and data allocation
>  delays, we'll get back to you within some hours
>
> - SVN: done
>
> - Git/Hg: we don't do anything right now; the new backup is still
>  available in the backup-20090527 directory if necessary. Later we'll
>  compare the last commit date with the May 27 backup, in case the
>  project has no currently active admin and wasn't repushed yet.
>
> --
> The Savannah Hackers
>
> On Wed, Jun 03, 2009 at 12:53:56AM +0200, Sylvain Beucler wrote:
>> Good news: we discovered a new backup from May 27th.
>> After tests, it appears to be a complete backup.
>>
>> We've added a new backup-20090527 directory.
>> It's available for cvs/svn/git/hg.
>>
>> We're replicating to the disk at the moment (right now it's a
>> read-only remote mount).
>>
>> If you want to use it instead of the April backup, you can modify your
>> support request.
>>
>> --
>> The Savannah Hackers
>> The FSF sysadmins
>>
>> On Tue, Jun 02, 2009 at 11:13:00AM +0200, Sylvain Beucler wrote:
>> > In your requests, remember to specify:
>> > - name of the project
>> > - VCS type (CVS / SVN / both)
>> > - date of the backup to recover (April / May)
>> >
>> > --
>> > Sylvain
>> >
>> > On Tue, Jun 02, 2009 at 07:15:48AM +0000, Sylvain Beucler wrote:
>> > >
>> > > The system is now completely functional.
>> > > It's time to decide what to do with your data.
>> > > (see first explanations at
>> > > http://lists.gnu.org/archive/html/savannah-users/2009-05/msg00023.html)
>> > >
>> > >
>> > > Please discuss and send questions at address@hidden !
>> > >
>> > > For import requests: see below, you need to send a support request via
>> > > the web interface.
>> > >
>> > >
>> > >
>> > > Basically your choices are:
>> > > a) you can use the backup from April 29
>> > > b) you can use our latest (incomplete) backup from May 29
>> > > c) you can import another backup you have
>> > > d) you can wait a few days until we possibly recover latest data from the
>> > > crashes disk (nothing is sure though). More details about this later.
>> > >
>> > >
>> > > Here's how do it for the various VCSs:
>> > >
>> > > * CVS:
>> > > a) The version from 29 April in the 'backup-20090429' subdirectory.
>> > > b) The version from 29 May in the 'backup-20090529-incomplete' 
>> > > subdirectory.
>> > > c) Upload your backup in your download area (SFTP) for us to import
>> > >
>> > > Access commands:
>> > > cvs -d:pserver:address@hidden:/sources/backup-20090429/your_project
>> > > co your_module
>> > > cvs
>> > > -d:pserver:address@hidden:/sources/backup-20090529-incomplete/your_project
>> > > co your_module
>> > > rsync rsync://cvs.sv.gnu.org/sources/backup-20090429/your_project/
>> > > rsync
>> > > rsync://cvs.sv.gnu.org/sources/backup-20090529-incomplete/your_project/
>> > >
>> > > IN ALL CASES: post a support request, authenticated (i.e. login first) at
>> > > https://savannah.gnu.org/support/?func=additem&group=administration with
>> > > category "RECOVERY: CVS/SVN". Requests send by mail or in the wrong 
>> > > category
>> > > won't be processed.
>> > >
>> > > If after 2 weeks we didn't receive an answer for your project, we'll
>> > > reinstall the latest backup we have.
>> > >
>> > >
>> > > * SVN:
>> > > a) The version from 29 April in the 'backup-20090429' subdirectory.
>> > > b) The version from 29 May in the 'backup-20090529-incomplete' 
>> > > subdirectory.
>> > > c) Upload your backup in your download area (SFTP)
>> > >
>> > > Access commands:
>> > > svn co svn://svn.sv.gnu.org/backup-20090429/your_project
>> > > svn co svn://svn.sv.gnu.org/backup-20090529-incomplete/your_project
>> > > rsync rsync://svn.sv.gnu.org/svn/backup-20090429/your_project/
>> > > rsync rsync://svn.sv.gnu.org/svn/backup-20090529-incomplete/your_project/
>> > > (if you get an error from this last one, it's probably corrupted)
>> > >
>> > > IN ALL CASES: post a support request, authenticated (i.e. login first) at
>> > > https://savannah.gnu.org/support/?func=additem&group=administration with
>> > > category "RECOVERY: CVS/SVN". Requests send by mail or in the wrong 
>> > > category
>> > > won't be processed.
>> > >
>> > > If after 2 weeks we didn't receive an answer for your project, we'll
>> > > reinstall the latest backup we have.
>> > >
>> > >
>> > > * Git:
>> > > a) We installed the version from 29 April.
>> > > b) You can attempt to recover from the partial 29 May backup:
>> > > http://git.savannah.gnu.org/r/backup-20090529-incomplete/
>> > > c) You can push a local version if you have one (git push --all; git push
>> > > --tags)
>> > >
>> > > You can import the repository directly, without our help.
>> > >
>> > >
>> > > * Mercurial:
>> > > a) We installed the version from 29 April.
>> > > b) We don't have a more recent backup
>> > > c) You can push a local version if you have one.
>> > >
>> > > You can import the repository directly, without our help.
>> > >
>> > >
>> > > * WebCVS:
>> > >
>> > > We plan to either recover the data from disk, or failing that, manually
>> > > commit the latest version at www.gnu.org and www.nongnu.org.
>
>
> _______________________________________________
> address@hidden mailing list
> http://lists.gnu.org/mailman/listinfo/savannah-announce
>
>
>
> --
> Erk
>



-- 
Erk