Comment 9 for bug 515850

Revision history for this message
Billie Cleek (cleekbi) wrote :

I have to echo Tomasz Gajewski's assessment. After this happened to me, I was able to checkout to a new repository, but unable to commit. Any attempts to commit resulted in the error that Huw Giddens noted, "it complains that my branch is out of date but running bzr up gives me no more revisions." I even dumped the subversion repository, removed all of my revisions that had been committed from bzr-svn from the dump and then loaded the dump file into a brand new repository. After clearing my bzr-svn cache and removing the subversion repository entry from subversion.conf, any attempts to commit changes using bzr-svn resulted in the error about the branch being out of date, but update did not bring in any more revisions. Interestingly, viewing the log using TortoiseSVN or svn.exe showed that the revisions I had removed were in fact removed, but 'bzr log' would show the log messages for the removed revisions and the file change list for the revision after the revision that had been removed.