Boost logo

Boost :

From: Douglas Gregor (gregod_at_[hidden])
Date: 2003-05-07 09:31:34

On Wednesday 07 May 2003 09:18 am, Beman Dawes wrote:
> On 2003-05-05, the primary 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, boost, was one of the effected
> projects (we base this on information returned when we ran checks
> on the filesystem).
> 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.

Well, what do we do about this? The newest versions of all files in the
repository have to be on someone's machine, somewhere. The good news is that
they're easy to find. For instance, I run "cvs status" on
boost/type_traits/alignment_of.hpp and I get:

File: alignment_of.hpp Status: Needs Patch

   Working revision: 1.4
   Repository revision: 1.3
   Sticky Tag: (none)
   Sticky Date: (none)
   Sticky Options: (none)

Note that the working revision > the repository revision, which means that it
was checked in as version 1.4 but only version 1.3 still exists in the
repository. The status will be "Needs Patch" when the local version is
untouched from the last checked-in version (before the hard crash) or
"Locally Modified" if the file has been changed size the last checkout.

Someone could write a script to restore all of the files from a particular
Boost checkout. It would:
  - execute "cvs status" in $BOOST_ROOT once to get the status of all files in
the repository
  - find the set of files with status "Needs Patch" and working version >
repository version.
  - "touch" each of the files (so it looks like they were locally modified)
  - "cvs commit" each of the files

I can do this perhaps later today.


Boost list run by bdawes at, gregod at, cpdaniel at, john at