I am using the Collabnet compiled win32 svn 1.5 client on Windows XP SP2.
The server is running version 1.4.5. I get the following error when running
svn as follows
D:\source>svn log svn+ssh://bilbo/repos/BAM_HTM/trunk
svn: Item is not readable
The same exact command works as expected with svn win32 client 1.4.6
I'm using a private key through pageant and windows username/password for
authentication
As previously posted a similar problem occurs when using the TortoiseSVN 1.5
client
On Wed, Jun 25, 2008 at 12:52 PM, Andrew Sasak <andrew.sasak_at_gmail.com>
wrote:
> I am using TortoiseSVN 1.5. The problems I indicated occur with the
> TortoiseSVN 1.5 client. To verify that this issue isn't specific to
> Tortoise, I tried windows collabnet svn client v1.5. I also get an error
> when trying to view a repository log. It seems that there is some sort of
> problem with svn when using ssh as I've seen other people report similar
> problems on this and other lists. The server is running svn 1.4.5
>
>
> On Tue, Jun 24, 2008 at 12:25 AM, Talden <talden_at_gmail.com> wrote:
>
>> On Tue, Jun 24, 2008 at 7:23 AM, Andrew Sasak <andrew.sasak_at_gmail.com>
>> wrote:
>> > Since upgrading my client to 1.5, I can't update my WC or view the log
>> of
>> > repositories on a particular machine. I have been able to commit to a
>> repo
>> > on this machine using Tortoise. I can view the log of repositories on
>> this
>> > machine using a different client (CommitMonitor). Other people in my
>> office
>> > that haven't upgraded their tortoise client have been able to view the
>> log
>> > and update. This particular machine uses svn+ssh. I am able to update
>> and
>> > view the log of repos on other machines that use http.
>> >
>> > When I attempt to update, I get an error "Not authorized to open root of
>> > edit operation" When I attempt to view the log, I get a message box with
>> > title "TortoiseSVN" that says
>> > "C:\Projects\subversion-1.4.5\subversion\libsvn_repos\log.c"
>>
>> I believe the 1.5 client has silently upgraded the WC. Updating to
>> TortoiseSVN 1.5.x might solve the problem.
>>
>> --
>> Talden
>>
>
>
Received on 2008-06-27 22:51:11 CEST