Hi,
Thank for your answer.
I verify my repository and could'nt find any error or warning (see verify_log_buey0389_3690.txt).
Then I recover the repository (see recover_log_buey0389_3690.txt).
After the verify/recovery actions:
1. Using "svn list -v svn://buey0389" give me
1854 bao2bue Okt 25 11:05 ./
1853 bao2bue Okt 25 09:42 branches/
1849 bem2bue Okt 25 07:20 tags/
1854 bao2bue Okt 25 11:05 trunk/
2. Using "svn list -v svn://buey0389" give me also
1854 bao2bue Okt 25 11:05 ./
1853 bao2bue Okt 25 09:42 branches/
1849 bem2bue Okt 25 07:20 tags/
1854 bao2bue Okt 25 11:05 trunk/
But I still have the problem, that the repository browser:
a. goes to svn://buey0389/buey0389:3690 when I enter "svn://buey0389:3690"
b. goes to svn://buey0389 when I enter "svn://buey0389".
????
Olivier
> On 24.10.2011 11:33, Risotto Oregano wrote:
> > Hi,
> >
> > I have some problems with TortoiseSVN1.7.0 (and 1.7.1 also)
> >
> > I upgraded my Subversion server (WinXP SP3) to the CollabNet
> > Subversion Edge 2.1.0. Because the security policies of my company
> > doesn't allow us to install Apache, we are using svnserve as daemon
> > to work with about 7 repositories (from port 3690 to 3696).
> >
> > After the upgrade, we were unable to update current workcopies of the
> > 3690-repository with TortoiseSVN (all other repositories [3691-3696]
> > worked fine). We got the message 'svn://buey0389:3690' isn't in the
> > same repository as 'svn://buey0389'.
> >
> > Then we upgraded our client to TortoiseSVN 1.7.0 and after restart
> > the problem was gone. We could upgrade our 3690-workcopy and work
> > with it.
> >
> > Today I look inside the repository browser into my 3690-repository
> > and see a new folder, that nobody here create/commit/copy: please see
> > screenshot.png
> >
> >
> > The log file of this folder is empty as the version graph.
> >
> > I tried to delete the folder from the repository, then the repository
> > browser crashed. Here the dump of Tortoise: please see dump file
> >
> >
> > I check for this issue in the issue tracker and couldn't find it, so
> > I send the dump - may be it is a new issue?
>
> Maybe your repository is corrupted? Try running
> svnadmin verify path/to/repo
> and/or
> svnadmin recover path/to/repo
>
> on the server.
>
> And use the CL client on your machine and run
> svn list -v svn://buey0389
>
> Stefan
>
> --
> ___
> oo // \\ "De Chelonian Mobile"
> (_,\/ \_/ \ TortoiseSVN
> \ \_/_\_/> The coolest Interface to (Sub)Version Control
> /_/ \_\ http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2863480
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-10-25 17:27:19 CEST