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

Re: Show log

From: Konstantin Kolinko <knst.kolinko_at_gmail.com>
Date: Wed, 15 Oct 2008 00:41:47 +0400

2008/10/11 Anto Marky <markysvn_at_gmail.com>:
>
> On Sat, Oct 11, 2008 at 4:30 PM, Konstantin Kolinko <knst.kolinko_at_gmail.com>
> wrote:
>>
>> 2008/10/11 Anto Marky <markysvn_at_gmail.com>:
>> >
>> > I have earlier posted this problem a week ago, still not able to sort
>> > it.I
>> > get an error "svn: Item is not readable" when check for svn log from the
>> > CLI
>> > and from TSVN i get a message like " offline for now, Permanently
>> > offline
>> > and Don't go offline" when I click Don't go offline, it asks fro the svn
>> > user name and pssword when I give the username and password it again
>> > asks to
>> > select the above three.I again select Don't go offline it gives a TSVN
>> > message subversion/libsvn_repos/log.c.
>> >
>>
>>
>> By googling I found the following page that mentions the message:
>>
>> http://sdesmedt.wordpress.com/2006/11/04/building-a-development-environment-part-1-managing-your-sourcecode-with-subversion/
>>
>> It says:
>> "(...) uses the log command of subversion to decide if something changed
>> in the repository, (..). Unfortunatly, this subversion command fails
>> with a message
>> "Item is not readable" if you didn't provide read access to the root for
>> anyone in the authz file."
>>
>> I do not 100% agree with all that is written there, but at least it
>> gives you a direction
>> where to look: check the access rights.
>>
>>
>> Best regards,
>> Konstantin Kolinko
>
>
> Hi Konstantin,
>
> this my authz file do you find anything wrong?
>
> ### This file is an example authorization file for svnserve.
> ### Its format is identical to that of mod_authz_svn authorization
> ### files.
> ### As shown below each section defines authorizations for the path and
> ### (optional) repository specified by the section name.
> ### The authorizations follow. An authorization line can refer to:
> ### - a single user,
> ### - a group of users defined in a special [groups] section,
> ### - an alias defined in a special [aliases] section,
> ### - all authenticated users, using the '$authenticated' token,
> ### - only anonymous users, using the '$anonymous' token,
> ### - anyone, using the '*' wildcard.
> ###
> ### A match can be inverted by prefixing the rule with '~'. Rules can
> ### grant read ('r') access, read-write ('rw') access, or no access
> ### ('').
>
> [aliases]
> # joe = /C=XZ/ST=Dessert/L=Snake City/O=Snake Oil, Ltd./OU=Research
> Institute/CN=Joe Average
>
> [groups]
> # harry_and_sally = harry,sally
> # harry_sally_and_joe = harry,sally,&joe
>
> # [/foo/bar]
> # harry = rw
> # &joe = r
> # * =
>
> [/]
> # @harry_and_sally = rw
> sam = rw
> bob = rw
> xavier = rw
>
> abdul = rw
> raja = rw
> praveena = rw
> remeshan = rw
>
> Thanks
>
> Marky
>
>

Marky,

From your other messages I see that you are using svn://
protocol.

What is the contents of your svnserve.conf file?

I am able to reproduce your error with the following scenario:

1. svnserve.conf contains
# anon-access = read
# auth-access = write
or
anon-access = read
auth-access = write

2. authz is as above, that is: only explicit users are mentioned, no
rights are given to the anonymous

3. I am able to checkout from the repository (anonymously) and to
add a file to it (authentication is required):

svn commit --username sam --password rw --no-auth-cache -m "Adding text.txt" .

4. Svn log command displays the revision numbers, but no log messages:

svn update --username sam --password rw --no-auth-cache
At revision 1.

svn log --username sam --password rw --no-auth-cache
------------------------------------------------------------------------
r1 | (no author) | (no date) | 1 line

5. And diagnosis / solution is the following:
The issue is caused by inconsistency in configuration.
The following two alternative changes (either of them) do solve the issue:

Solution A):

Add the following line to authz file:

* = r

thus confirming your decision to allow read-only access to anonymous.

Solution B):

Configure the following in svnserve.conf:
anon-access = none

thus always requiring authentication.

In case anyone is interested, I am attaching a copy of repository that
reproduces this issue.

Reproduced using
svn, version 1.5.3 (r33570)
on Windows XP

Best regards,
Konstantin Kolinko

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org

Received on 2008-10-14 22:42:24 CEST

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