newsNews: Recover your repositories

 
 
Latest News
The git service has moved to the new server posted by rwp, Sun Dec 4 00:38:44 2016 - 0 replies
Savannah is migrating to updated systems. posted by rwp, Wed Nov 30 23:56:33 2016 - 0 replies
Savannah suffering networking problems posted by rwp, Fri May 13 22:58:25 2016 - 0 replies
Savannah https SSL certificates updated posted by rwp, Fri Mar 25 05:32:10 2016 - 0 replies
Savannah IPv4 address has changed posted by rwp, Sun Aug 9 20:07:57 2015 - 0 replies
[180 news in archive]

Recover your repositories

Item posted by Sylvain Beucler <Beuc> on Thu Jun 4 07:08:47 2009.

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 savannah-users@gnu.org !

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.
e) you can use the backup from May 27 which we found a bit 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
e) The version from 27 May in the 'backup-20090527' subdirectory.

Access commands:
cvs -d:pserver:anonymous@cvs.sv.gnu.org:/sources/backup-20090429/your_project co your_module
cvs -d:pserver:anonymous@cvs.sv.gnu.org:/sources/backup-20090529-incomplete/your_project co your_module
cvs -d:pserver:anonymous@cvs.sv.gnu.org:/sources/backup-20090527/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/
rsync rsync://cvs.sv.gnu.org/sources/backup-20090527/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.

In your requests, remember to specify:
- name of the project
- VCS type (CVS / SVN / both)
- date of the backup to recover (April / May)

If after 2 weeks we didn't receive an answer for your project, we'll reinstall the latest backup we have (May 27).

  • 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)
e) The version from 27 May in the 'backup-20090527' subdirectory.

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
svn co svn://svn.sv.gnu.org/backup-20090527/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/
rsync rsync://svn.sv.gnu.org/svn/backup-20090527/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.

In your requests, remember to specify:
- name of the project
- VCS type (CVS / SVN / both)
- date of the backup to recover (April / May)

If after 2 weeks we didn't receive an answer for your project, we'll reinstall the latest backup we have (May 27).

  • 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 ..., once per public branch and tag)
e) If you didn't push yet, you can check the May 27 backup at: http://git.savannah.gnu.org/r/backup-20090527/

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.
e) If you didn't push yet, you can check the May 27 backup in the 'backup-20090527' subdirectory

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 http://www.gnu.org and http://www.nongnu.org.

Comments:

Restore autoconf-archive GIT from May 27 (posted by Peter Simons, Thu Jun 4 17:53:44 2009)

Please restore the May 27 backup of the autoconf-archive GIT repository.

Thank you very much for your efforts, you guys are providing a great service to the free software community.


git recovery (posted by Ralf Wildenhues, Tue Jun 2 18:17:44 2009)

Please do not recommend 'git push --all' for recovery, as that will push all local refs. Some developers may have local branches in their tree that are not meant for publishing.


   

 

Back to the top


Powered by Savane 3.1-cleanup