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

RE: svnserve 64bit losing history (sort of)

From: Edward Ned Harvey <edward.harvey_at_patni.com>
Date: Sat, 16 May 2009 10:36:45 -0400

> It is known that certain misconfiguration that can result in the

> following output:

>

> > (no author) | (no date) For every single entry

> > and also no comment.

>

> Please take a look at the following thread:

> "Re: Show log"

> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessage

> Id=88192

This was a really informative lead. I would like to describe in more detail, exactly what happens here, because it's just so bizarre. I configured both apache and svnserve to serve the same repository, so I can simply toggle them on/off one at a time.

Until today, I did not have "anon-access = none" Instead I had only:

      [/]

      @mygroup = rw

This does require authentication to do anything, but it is still a misconfiguration, as described below:

* Using http:// everything is fine. It requires authentication. I can read/write as long as I'm authenticated. I get denied when I'm not authenticated. I am able to see the complete log history of the whole repository, including all the past commits that happened via misconfigured svn://

* Using svn:// with the proper configuration "anon-access = none" in the svnserve.conf ... Things are half fine. I can read/write as long as I'm authenticated. I get denied when I'm not authenticated. I can see the log history but only for commits that happened via http:// or via svn:// without the misconfiguration. I cannot see the log history for commits that happened via svn:// with the misconfiguration.

* Using svn:// with the misconfiguration neglecting "anon-access = none" in the svnserve.conf file ... It requires authentication. I can read/write as long as I'm authenticated. I get denied when I'm not authenticated. If I do any commits, the log of those commits is only visible via http:// and not via svn:// even when properly configured. When I have the misconfiguration, yes I can see the log of commits that happened via http:// or via svn:// without the misconfiguration. Yes my misconfigured commits are authenticated and do communicate the proper information to the server (as evidenced by the fact that I can see this info via svn log http://) ... but my misconfigured commits log history are not visible via either misconfigured or correctly-configured svn://.

So now - The thing for me to figure out is - I prefer to use svnserve instead of apache. It is obviously easy for me to correct the misconfiguration, but that only helps me for future commits. I know the log information for past misconfigured commits are all in there because it's visible via apache. I'd like to fix my repository to enable this via correctly configured svnserve. Most likely, since we know the cause of the problem now (and it's not related to 32bit vs 64bit) ... I'll start a new thread on the dev list.

Thanks for your help.

________________________________
This e-mail message may contain proprietary, confidential or legally privileged information for the sole use of the person or entity to whom this message was originally addressed. Any review, e-transmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this e-mail in error kindly delete this e-mail from your records. If it appears that this mail has been forwarded to you without proper authority, please notify us immediately at netadmin_at_patni.com and delete this mail.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2280888

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-16 16:37:49 CEST

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

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