From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30317 invoked by alias); 3 Jun 2009 08:06:18 -0000 Received: (qmail 30308 invoked by uid 22791); 3 Jun 2009 08:06:17 -0000 X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=AWL,BAYES_05,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail.network-theory.co.uk (HELO mail.network-theory.co.uk) (66.199.228.187) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 03 Jun 2009 08:06:11 +0000 Date: Wed, 03 Jun 2009 08:06:00 -0000 Message-ID: From: Brian Gough To: GSL Discuss Mailing List Subject: Forward: [Savannah-announce] Recover your repositories References: <20090602071655.GA28957@perso.beuc.net> User-Agent: Wanderlust/2.14.0 (Africa) Emacs/22.2 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: multipart/mixed; boundary="Multipart_Wed_Jun__3_08:08:03_2009-1" X-Message-Mac: 984f2973f7a6eab41cbba91e3f214445 Mailing-List: contact gsl-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gsl-discuss-owner@sourceware.org X-SW-Source: 2009-q2/txt/msg00009.txt.bz2 --Multipart_Wed_Jun__3_08:08:03_2009-1 Content-Type: text/plain; charset=US-ASCII Content-length: 166 There was a disk crash on savannah which wiped out some of the recent commits, I've re-pushed the repository from my personal copy so everything should be back now. --Multipart_Wed_Jun__3_08:08:03_2009-1 Content-Type: message/rfc822 Content-length: 4688 Date: Tue, 2 Jun 2009 09:16:55 +0200 From: Sylvain Beucler To: savannah-announce@gnu.org Message-ID: <20090602071655.GA28957@perso.beuc.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: GNU/Linux User-Agent: Mutt/1.5.18 (2008-05-17) X-Detected-Operating-System: by mx20.gnu.org: GNU/Linux 2.6 (newer, 3) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. Subject: [Savannah-announce] Recover your repositories X-BeenThere: savannah-announce@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: savannah-users@gnu.org List-Id: Low-volume notifications of important issues and changes at Savannah List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: savannah-announce-bounces+bjg=network-theory.co.uk@gnu.org Errors-To: savannah-announce-bounces+bjg=network-theory.co.uk@gnu.org Content-length: 3343 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. 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: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 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. _______________________________________________ Savannah-announce@gnu.org mailing list http://lists.gnu.org/mailman/listinfo/savannah-announce --Multipart_Wed_Jun__3_08:08:03_2009-1--