On Wed, May 21, 2014 at 4:02 AM, Aleš Vojáček wrote:
> Hi all,
> we are trying to upgrade our svn repo from 1.6 to 1.8.9 using svnsync.
That's a fairly big jump, to bleeding edge release. Can you try an
intermediate repository, such as 1.7 based? And can you try doing an
"svnadmin dump" and "svn
On May 21, 2014, at 09:48, Dan Ellis wrote:
> On Wed, May 21, 2014 at 3:22 AM, Ryan Schmidt wrote:
>
>> On May 20, 2014, at 17:02, Dan Ellis wrote:
>>
>>> I'm attempting to copy a file from a working copy to the server, but using
>>> an incorrect case for one of the folders in the path. The pa
Sir,
Thanks for the help I'll compile SVN 1.8.9 with Apache 2.2.24 and check .
I'll contact with you if face any issue . Again thanks for your support : )
On Wed, May 21, 2014 at 4:10 PM, Stefan Sperling wrote:
> On Wed, May 21, 2014 at 07:28:34PM +0500, Mohsin Abbas wrote:
> > I want to add o
On Wed, May 21, 2014 at 07:28:34PM +0500, Mohsin Abbas wrote:
> I want to add one point all repositories are accessible when I access
> through browser but encountered above reported issue when access through
> tortoise SVN client why this happen I mean If this is bug in Apache HTTPD
> then It shou
On Wed, May 21, 2014 at 07:22:48PM +0500, Mohsin Abbas wrote:
> I have installed Apache 2.2.27 with subversion 1.8.9 version you are
> saying this Apache version is venerable for this issue ? right ? Now please
> tell me what Apache version should I use which is not venerable for this
> issue ?
A
On Wed, May 21, 2014 at 3:22 AM, Ryan Schmidt <
subversion-2...@ryandesign.com> wrote:
>
> On May 20, 2014, at 17:02, Dan Ellis wrote:
>
> > I'm attempting to copy a file from a working copy to the server, but
> using an incorrect case for one of the folders in the path. The paths all
> exist and
I want to add one point all repositories are accessible when I access
through browser but encountered above reported issue when access through
tortoise SVN client why this happen I mean If this is bug in Apache HTTPD
then It should not work in browser too .. What to you say about this ?
Regards
Hello sir,
I have installed Apache 2.2.27 with subversion 1.8.9 version you are
saying this Apache version is venerable for this issue ? right ? Now please
tell me what Apache version should I use which is not venerable for this
issue ?
Regards
On Wed, May 21, 2014 at 2:21 PM, Stefan Sperling
On May 20, 2014, at 17:02, Dan Ellis wrote:
> I'm wondering if I'm getting an incorrect error message...
>
> I'm attempting to copy a file from a working copy to the server, but using an
> incorrect case for one of the folders in the path. The paths all exist and
> everything works fine using
Ok,
that problem is somewhere in tortoise client.
When I show log from repository browser it seems that bugtack properties
does not work.
When I show log from working copy it works a show bug ids and url to bug
tracking system.
I'm sorry for that question.
A.
Dne 21.5.2014 11:17, Johan Corveley
On Wed, May 21, 2014 at 11:28 AM, Aleš Vojáček wrote:
>
> Dne 21.5.2014 11:17, Johan Corveleyn napsal(a):
>
>> On Wed, May 21, 2014 at 10:02 AM, Aleš Vojáček
>> wrote:
>>>
>>> Hi all,
>>> we are trying to upgrade our svn repo from 1.6 to 1.8.9 using svnsync.
>>> But at the end svnsync writes a me
On Wed, May 21, 2014 at 12:14:25AM +, Mohsin Abbas wrote:
> Hello Sir,
>
> 403 permission denied issue has been resolved after removing trailing
> slash. Thanks for help.
>
> Now one more issue i am facing when i access repositories URL in Tortoise
> SVN client it gives unable to parse error
On Wed, May 21, 2014 at 10:02 AM, Aleš Vojáček wrote:
> Hi all,
> we are trying to upgrade our svn repo from 1.6 to 1.8.9 using svnsync.
> But at the end svnsync writes a message NOTE: Normalized svn:* properties to
> LF line endings .
> Is it possible to disable this behavior or to undo this norm
Hello!
I work with a redmine+svn server which manages svn access through redmine but
- out of the box - does not support per-directory restrictions.
I need to restrict write access to certain ("results", "tags") directories to
certain project members.
I know the commit-access-control.pl script
Hi all,
we are trying to upgrade our svn repo from 1.6 to 1.8.9 using svnsync.
But at the end svnsync writes a message NOTE: Normalized svn:*
properties to LF line endings .
Is it possible to disable this behavior or to undo this normalization?
After that we have no working our Issue tracker pro
15 matches
Mail list logo