On Sun, Jul 29, 2007, 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)...
>
> 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.
>
> 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?

Ok, Thomas and I've looked into the problem in more detail. We cannot
bring the frontend and backends into sync without lots of hacking
(again, as done in May 2007). So, sorry, we decided to revert the db to
the db-ORIG dir again to be in sync again. We'll now look what the best
approach is to repeat your import operation so the stuff does not again
go out of sync.
                                       Ralf S. Engelschall
                                       rse@engelschall.com
                                       www.engelschall.com