Re: FW: SourceForge.net support: project CVS issue: opensymphony

At worst, I've got all the cvs emails. Would be a chore, but not
impossible to salvage code from them.

--Erik

On Wed, 7 May 2003, Hani Suleiman wrote:

> Ooooh shit. Aaaargh!
>
> I had made a whole buttload of osworkflow fixes then, which all seems
> to have gone away, and I foolishly updated and just lost all my
> changes. Can some kind soul who has an osworkflow snapshot from 1-2
> days ago please send me their src dir? You can check if you have a
> 'good' cvs dir if the file
> src/java/com/opensymphony/workflow/util/LogRegister.java exists. If it
> does, do NOT cvs update, send me your src instead so I can put in all
> the changes again.
>
> On Wednesday, May 7, 2003, at 09:11 AM, Mike Cannon-Brookes wrote:
>
> > Guys,
> >
> > Can we recommit all changes made singe the 3rd of May?
> >
> > You should have them all in your local repositories so I suggest you
> > make a
> > backup before talking to CVS (to be sure).
> >
> > This especially applies to OSWF and XW/WW2 as they have both had heavy
> > changes in this time.
> >
> > Cheers,
> > Mike
> >
> > ------ Forwarded Message
> > From: "Jacob Moorman" <[email protected]>
> > Date: Wed, 07 May 2003 05:49:32 -0700
> > To: [email protected], [email protected],
> > [email protected], [email protected]
> > Subject: SourceForge.net support: project CVS issue: opensymphony
> >
> > Greetings,
> >
> > My name is Jacob Moorman; I am the Quality of Service Manager for
> > SourceForge.net. I am writing to you today regarding your
> > SourceForge.net project, opensymphony. If you feel this message has
> > been sent in error, please reply and let me know.
> >
> > On 2003-05-05, the primary SourceForge.net project CVS server
> > sufferred a hard crash which resulted in the corruption of CVS
> > repositories for a small number of projects.  Unfortunately, we
> > believe that your project, opensymphony, was one of the effected
> > projects (we base this on information returned when we ran checks
> > on the filesystem).
> >
> > We have taken the following steps:
> >
> > 1. Revalidated the filesystem, to ensure that further corruption
> > will not occur.
> >
> > 2. Made a backup of the contents of your CVS repository as of
> > 2003-05-06 and 2003-05-07 (we made two backups).
> >
> > 3. Restored your project CVS repository as of 2003-05-03.  This
> > action was taken as we could not ensure the stability of your
> > repository in its current state.
> >
> > We have done our best to respond to this issue in a complete manner,
> > and to bring your repository back online as quickly as possible.
> > This matter has been handled with high priority, resulting in a
> > turnaround time on this issue of less than two business days from the
> > time this issue was discovered.
> >
> > Moving forward, you should work within your development team to come
> > up with a course of action for committing all more recent repository
> > changes; obviously some intermediate history will be lost in this
> > process, but you should be able to bring things back to a current
> > state fairly quickly now that the repository has been stabilized.
> >
> > Additionally:
> > If you would like access to the backups from 2003-05-03 (known stable),
> > 2003-05-06/2003-05-07 (made before your repository was restored to
> > the known state from 2003-05-03), please let us know; if you believe
> > (based on work in the past few days) that your repository is generally
> > clean, we can restore the repository to its state as of this morning
> > and selectively use the 2003-05-03 backup to fill in any
> > gaps/corruption
> > that you detect.  Please let us know if we may be of further assistance
> > in this matter.
> >
> > If you have questions or concerns regarding this matter, please
> > submit a Support Request at:
> > https://sourceforge.net/tracker/?func=add&group_id=1&atid=200001
> >
> > Thank you,
> >
> > Jacob Moorman
> > Quality of Service Manager, SourceForge.net
> > https://sourceforge.net/users/moorman
> > [email protected]
> > [email protected]
> > [email protected]
> >
> > ------ End of Forwarded Message
> >
> >
> >
> > -------------------------------------------------------
> > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> > The only event dedicated to issues related to Linux enterprise
> > solutions
> > www.enterpriselinuxforum.com
> >
> > _______________________________________________
> > Opensymphony-developers mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/opensymphony-developers
> >
>
>
>
> -------------------------------------------------------
> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> The only event dedicated to issues related to Linux enterprise solutions
> www.enterpriselinuxforum.com
>
> _______________________________________________
> Opensymphony-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/opensymphony-developers
>



-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com