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

Re: Subversion 1.5 (r26502) - Log Message Bug?

From: Malcolm Rowe <malcolm-svn-dev_at_farside.org.uk>
Date: 2007-09-24 16:36:28 CEST

On Fri, Sep 21, 2007 at 08:27:05PM +0200, Karl Heinz Marbaise wrote:
> "svn log svn://localhost" which should print out the log message i gave
> on the command line, but i got the following:
>
> ------------------------------------------------------------------------
> r1 | (no author) | (no date) | 1 line
>

This is expected behaviour. Here's what's happening:

Your initial connection to the server is made using an anonymous
connection (the server allows anonymous access, so this is okay).
However, although this anonymous user has read access in theory, the
authz configuration effectively disallows all access to all paths.

'svn list' requires authorisation to access the paths that you're
listing, while 'svn import' requires general write access. In both
cases, issuing the command results in an immediate prompt for
authorisation, and the command succeeds using the 'kama' user.

'svn log', however, can run with degraded access, and will censor
revisions to which the user has no, or limited, access. This is the
behaviour you're seeing: the censored results of a user with no access
to the paths modified in the revision.

Your problem is in the svnserve.conf configuration:

> auth-access = write
> password-db = passwd
> authz-db = authz
> realm = My First repository

You left the default value of 'anon-access' as 'read'; change that to
'none', and all connections will require authorisation. You'll then get
the correct behaviour from 'log'.

> This seemed to be a bug in the new version.
>

I was able to get identical results with both trunk and 1.4.2. It
doesn't look like anything's changed.

Regards,
Malcolm

  • application/pgp-signature attachment: stored
Received on Mon Sep 24 16:38:13 2007

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

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