jarpublic_at_gmail.com wrote:
> I have searched the archives and couldn't find anything that addressed
> my issue directly. I have always accessed my repositories via a mapped
> AFS drive. Recently when I try to do an update, commit, or browse the
> repository I get a "no such revision #" error where # is the most recent
> revision number of the particular repository. I initially thought that
> my repository was corrupt. However, after messing around with that for a
> long time, I believe it is some issue withing accessing my repository
> over AFS. I can access the repository via ssh+svn without getting the
> "no such revision" errors, but I have to type in my password tons of
> times and my server doesn't allow private key authentication. I have
> tried creating a brand new repository. I can create the repository,
> check it out, and do a single commit. Howerver after the first commit I
> get the error if I update, commit, or try to browse the repository. I
> have tried this on multiple computers and have seen this same behavior
> on each of them. Any help or any direction on alternative things to try
> or test would be greatly appreciated.
We strongly recommend to *not* access a repository over a network share:
http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-repository.html#tsvn-repository-local-share
Also, there are problems with SAMBA based shares (and AFS most likely
suffers from the same problems):
http://tortoisesvn.tigris.org/faq.html#samba
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=984644
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2008-12-15 21:15:53 CET