You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Andrew Sasak <an...@gmail.com> on 2008/07/01 14:24:28 UTC
Re: Bug report: can't update or view log with 1.5
Has anybody looked into this? Can anybody else who is experiencing the same
or similar problems using the 1.5 client on windows with svn+ssh protocol,
please confirm the existence of this bug. If you are successfully using
svn+ssh with a 1.5 client on windows against a pre-1.5 server please
contradict this bug.
Thank you.
On Fri, Jun 27, 2008 at 4:50 PM, Andrew Sasak <an...@gmail.com>
wrote:
> 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 <an...@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 <ta...@gmail.com> wrote:
>>
>>> On Tue, Jun 24, 2008 at 7:23 AM, Andrew Sasak <an...@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
>>>
>>
>>
>
Re: Bug report: can't update or view log with 1.5
Posted by Andrew Sasak <an...@gmail.com>.
The server has been upgraded to 1.5.0 and the problems persist. However
since the server has been upgraded the error message when using tortoisesnv
changed to:
D:\vinithra\build\svn_1.5.0\subversion\tmp\subversion\subversion\libsvn...\log.c
On Tue, Jul 1, 2008 at 10:24 AM, Andrew Sasak <an...@gmail.com>
wrote:
> Has anybody looked into this? Can anybody else who is experiencing the same
> or similar problems using the 1.5 client on windows with svn+ssh protocol,
> please confirm the existence of this bug. If you are successfully using
> svn+ssh with a 1.5 client on windows against a pre-1.5 server please
> contradict this bug.
>
> Thank you.
>
>
> On Fri, Jun 27, 2008 at 4:50 PM, Andrew Sasak <an...@gmail.com>
> wrote:
>
>> 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 <an...@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 <ta...@gmail.com> wrote:
>>>
>>>> On Tue, Jun 24, 2008 at 7:23 AM, Andrew Sasak <an...@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
>>>>
>>>
>>>
>>
>
Re: Bug report: can't update or view log with 1.5
Posted by Karl Fogel <kf...@red-bean.com>.
"Andrew Sasak" <an...@gmail.com> writes:
> Has anybody looked into this? Can anybody else who is experiencing the
> same or similar problems using the 1.5 client on windows with svn+ssh
> protocol, please confirm the existence of this bug. If you are
> successfully using svn+ssh with a 1.5 client on windows against a
> pre-1.5 server please contradict this bug.
In particular, anyone who has a portable reproduction recipe for this,
please let us know. (Unfortunately, we can't do much with the bug
report as is, because there is no way for us to reproduce it.)
-Karl
> Thank you.
>
> On Fri, Jun 27, 2008 at 4:50 PM, Andrew Sasak <an...@gmail.com> wrote:
>
> 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 <an...@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 <ta...@gmail.com> wrote:
>
> On Tue, Jun 24, 2008 at 7:23 AM, Andrew Sasak <
> andrew.sasak@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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org