On Jul 29, 2007, at 4:54 AM, Ralf S. Engelschall wrote:

>
> Thanks for all your efforts, Jeff.
>
> But unfortunately, although this procedure correctly upgraded db/
> subdir content, you missed to append the corresponding entries to
> CVSROOT/history! This way the CVSTrac frontend and the CVS backend are
> out of sync!! And because you already made two new commits we  
> cannot fix
> it easily by _NOW_ appending the CVSROOT/history entries (as the  
> two new
> entries were already taken over into the CVSTrac SQLite RDBMS)...
>

OK.

> As I said multiple times in the past, whatever you do, you always
> _HAVE_ to go through the "cvs" command line and _NEVER EVER_ touch
> the repository manually. Replacing content on the server side gets
> the backend and frontend totally out of sync and it cannot be fixed
> afterwards easily.
>

The track command was segfaulting, likely cvs itself, on the simple
sequence that works on linux.

> Puhh.... may I suggest that we reverse this again by moving
> /v/rpm/cvs/db-OLD into place again and _I_ do your above procedure  
> again
> by using the regular remote CVS access?
>

Sure. Alternatively, I do have the history from where the act was  
performed.

73 de Jeff