[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: upgraded repository issue

From: <dolanotoole_at_googlemail.com>
Date: Tue, 28 Oct 2008 10:40:25 -0700 (PDT)

Ah, that's done the trick! I do feel a bit silly now though :P
Thanks for the link Andy :)

On Oct 27, 7:48 pm, "Andy Levy" <andy.l..._at_gmail.com> wrote:
> On Mon, Oct 27, 2008 at 15:39, Dolan O'Toole
> <dolan.oto..._at_corelogic.co.uk> wrote:
> > Hi,
> > I'm having a strange problem viewing the revision history using the latest
> > TortoiseSVN on a repository that was upgraded from SVN 1.2 to 1.5 using the
> > standard dump/load mechanism.
> > What I did was using svn 1.5.4 windows binaries I dumped revisions 0 –
> > 10,000 of my existing repository, then loaded this dump into an empty svn
> > 1.5 repository that was first created using VisualSVN server, then on
> > another attempt using the standard svnadmin create.
> > After the load I could see the history in the new repository using Tortoise.
> > It was identical to the original repository. I then checked out a branch,
> > made a local change and committed the change. Using TortoiseSVN again to
> > look at the history of the branch I would have expected my new change to be
> > listed as the latest revision, but it was not. It was only listing the
> > revisions that were loaded from the dump file.
> > I then added a new file to my working copy and committed that. I then tried
> > to look at the log file for this new file. Tortoise prompted to work
> > offline. If I clicked "Offline for now" then the log lists one revision,
> > with an incorrect revision number. If I clicked "Don't go offline" I am
> > prompted again to work offline. A second click of "Don't go offline" and an
> > error message is displayed along the lines of "File not found: revision 929,
> > path '/trunk/somebranch/file.xml'" The revision number shown in that error
> > message changes sometimes. I checked the revisions from the error message by
> > looking in the history for the repository. The looked identical to the
> > original repository that the dump was taken from.
> > The strange thing is, if I run svn log at the command line or use subclipse
> > in eclipse, the revision history is displayed correctly. I have also tried
> > the RapidSVN client which worked. Even the Jira subversion plug-in was
> > picking up the new revisions as they were tagged with appropriate jira IDs.
> > I have tried loading the dump into a FSFS and BDB repository, accessing it
> > via http, https, svn and directly using file:// but the problem still
> > occurs.
> > It seems if I load a few revisions, say 500 this problem doesn't occur. The
> > 10,000 revisions I loaded was just a test. The actual repository I am
> > upgrading has over 30,000 revisions.
> > I have no problems with using TortoiseSVN 1.5.5 to access my old 1.2
> > repository. Could it be something that is happening during the dump loading
> > that Tortoise doesn't like?
> > If anyone has any idea what the problem could be, I would appreciate the
> > help. Thanks
> http://tortoisesvn.net/node/333
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr..._at_tortoisesvn.tigris.org
> For additional commands, e-mail: users-h..._at_tortoisesvn.tigris.org

To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-10-28 18:41:56 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.