Hi Gavin,
I have tried using a GUI and command line client, and both have the same
problem.
As for where I got my command-line client, I am using the pre-compiled
binaries from CollabNet.
svn --version prints this:
> svn, version 1.6.6 (r40053)
> compiled Oct 19 2009, 09:36:48
>
> Copyright (C) 2000-2009 CollabNet.
> Subversion is open source software, see http://subversion.tigris.org/
> This product includes software developed by CollabNet (
> http://www.Collab.Net/).
>
> The following repository access (RA) modules are available:
>
> * ra_neon : Module for accessing a repository via WebDAV protocol using
> Neon.
> - handles 'http' scheme
> - handles 'https' scheme
> * ra_svn : Module for accessing a repository using the svn network
> protocol.
> - with Cyrus SASL authentication
> - handles 'svn' scheme
> * ra_local : Module for accessing a repository on local disk.
> - handles 'file' scheme
> * ra_serf : Module for accessing a repository via WebDAV protocol using
> serf.
> - handles 'http' scheme
> - handles 'https' scheme
>
Thanks,
~Chris
On Thu, Nov 12, 2009 at 4:34 PM, Gavin 'Beau' Baumanis <
gavinb_at_thespidernet.com> wrote:
> Hi Chris,
>
> Just in case you tried it - but just didn't get around to updating your
> mail,
> Ryan asked what kind of client are using?
> And to also try another type.
> I.e. if you're using the command line version - try a GUI version.
>
> if you're using the command line version from where did you get it?
> Was it already compiled or did you compile it yourself?
>
> And while I am sincerely not being condescending - Have you tried the
> simple option? Download a new (pre-compiled) client and see if that works
> for you?
>
> Gavin.
>
>
> On 13/11/2009, at 11:07 , Chris Johnson wrote:
>
> A lot of these questions are answered in my previous posts, but I can
> understand if you don't want to dredge through all of that :P
>
> This seems to only be a problem on this computer, but I don't have another
> client handy to test. However, the problem is almost certainly internal,
> because when attempting to commit, the client does not open a port or
> otherwise make any sign of attempting to connect to a repository, but svn
> status and svn update operations work exactly as expected.
>
> Just to make sure that it wasn't a repository problem, I tried committing
> to three different repositories hosted in three different locations, all of
> which were mine and I had full permissions to, and the client had this
> problem when connecting to any of them.
>
> The server program being used on all the repositories is Apache, and I will
> try your suggestion of attempting to connect to an svnserve server.
>
> ~Chris
>
> On Thu, Nov 12, 2009 at 3:54 PM, Ryan Schmidt <
> subversion-2009b_at_ryandesign.com> wrote:
>
>> On Nov 12, 2009, at 17:48, Chris Johnson wrote:
>>
>> On Thu, Nov 12, 2009 at 1:57 PM, Ryan Schmidt wrote:
>>>
>>> Does this only happen with the svn command line client or also with any
>>>> of the several GUI clients?
>>>>
>>>> If CLI only, where is your svn? ("which svn"?) How was it compiled? Do
>>>> you have a wrapper around svn? Do you have a shell alias for svn?
>>>>
>>>
>>> The problem occurs both from the command line and in GUI clients. I am
>>> using the version 1.6.6 binaries from CollabNet. I do not have any wrappers,
>>> and no shell aliases for svn.
>>>
>>
>> I forget if you mentioned already, but do you see this problem only on one
>> client computer or multiple client computers? When accessing only a single
>> repository or have you tried different repositories on the same server? What
>> about a different server? What server program is being used -- apache?
>> svnserve? Have you tried the other?
>>
>> Don't forget to Reply All so your reply goes to the list too, not just to
>> me.
>>
>>
>>
>
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2417335
Received on 2009-11-13 02:38:13 CET