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

Re: Bizarre SVNServe Issues (Auth?)

From: Ulrich Eckhardt <eckhardt_at_satorlaser.com>
Date: Wed, 3 Jun 2009 09:01:51 +0200

On Wednesday 03 June 2009, Arthur Axel fREW Schmidt wrote:
> So one of my users was recently having issues commiting to SVN. He was
> commiting *from* a shared repository on a windows remote share. In the irc
> channel someone told me that was problematic so we stopped using the remote
> share and gave each person a local copy.

Just for the record: I'm very sure you are confusing the terms "repository"
and "working copy" here. That said, it absolutely makes sense that every
developer has one or multiple working copies separate from other users.

> Whenever *anyone* checked out a new checkout from the repo they could not
> check in and got a "Authorization failed" error. I verified the repo and
> everything was fine. Next I did an svnadmin dump foo | svnadmin load bar.

I'm a bit confused, because here you get WC and repository sorted right.
Anyway, if you dump and reload the repository, and the new repository also
has a different name, existing WCs need to be redirected to the new URL
using 'svn switch --relocate' (also of course possible via TSVN).

> After I did that I was forced to upgrade from our ghetto SVNServer to the
> regular svnserve. That was fine. After that I could check out and check
> in from the repo in question. My coworker still had issues. In fact,
> after we checked in from his account, no one could check in.

What access method are you using? If you are using svn://, make sure the
repository is only accessed and completely owned by the user as which
svnserve runs. This is not an TSVN thing though and the SVN docs actually
treat this problem and its various solutions.

Further, if you are using a shared working copy or copies of a formerly shared
working copy, you might still have messed up authentication information
embedded therein. The point is that after a checkout, some authentication
info is stored in the WC's metadata. You can not and should not try to use
the same WC or a copy thereof as a different user. Check out a fresh WC
instead of copying the directory.


ML: http://tortoisesvn.tigris.org/list_etiquette.html
FAQ: http://tortoisesvn.net/faq
Sator Laser GmbH
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
Sator Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
           Visit our website at <http://www.satorlaser.de/>
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte Änderungen enthalten. Sator Laser GmbH ist für diese Folgen nicht verantwortlich.
Received on 2009-06-03 09:02:11 CEST

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.