Hi,
due to some strict business requirements, I need to do an overly
complex subversion repository access through Apache. I won't
configure it myself, so please see this is a no exit alley. Maybe
there is even a simpler way to configure it.
I'm integrating two repositories using the svn:external
Hello all!
I've tried this at IRC rooms without results, then I'm here to try the list!
:)
I'm trying enable Apache + LDAP + SVN to enable my SVN server service. All
almost done, but with this config at Apache (I have this VH only to
subversion!):
1.
2.
3. ServerAdmin m...@me.
Some more news! I changed a little and the error changed. I removed the
"DocumentRoot" from configuration too.
The new error is:
[Mon May 10 17:12:10 2010] [error] [client 192.168.254.241] client denied by
server configuration: /etc/apache2/htdocs
But /etc/apache2/htdocs does not exists, and I
Hi,
On Mon, May 10, 2010 at 7:33 PM, Ryan Schmidt
wrote:
>
> On May 10, 2010, at 09:07, Edward Knoll wrote:
>
>> Not Subversion source control, but some custom SCM/bookkeeping that has been
>> built around/on top of Subversion - layers application teams don't have
>> direct access. My (forlorn
On May 10, 2010, at 09:07, Edward Knoll wrote:
> Not Subversion source control, but some custom SCM/bookkeeping that has been
> built around/on top of Subversion - layers application teams don't have
> direct access. My (forlorn) hope is there's a way of extending the keywords,
> so the appli
On Mon, May 10, 2010 at 07:45:07PM +0800, Jean Seurin wrote:
> Here's the whole thing, minus unconcerned subprojects:
>
> Properties on '$REPO/trunk/project/src/test/resources/log4j.properties':
> svn:mergeinfo
> /branches/project-1.10/src/test/resources/log4j.properties:2344-2345,2347,2349,2351
I suspect I have corrupt mergeinffo but I'm not sure. Does anyone know how
I'd make a determination and what resources are out there to help fix
problems?
Here’s the issue. My team recently moved to agile and uses feature branches
(story branches really) where different teams work on the same sour
BD wrote on 05/10/2010 09:52:39 AM:
> Thats a very interesting way of looking at this problem. It does
> make sense that multiple commit processes coming from the same
> machine really wouldnt be that different from the question I was
> asking. I guess from here I'll have to do some testing som
Thanks Hyrum,
Thats a very interesting way of looking at this problem. It does make sense
that multiple commit processes coming from the same machine really wouldnt
be that different from the question I was asking. I guess from here I'll
have to do some testing somehow, with nfs in the mix and see
Not Subversion source control, but some custom SCM/bookkeeping that has been
built around/on top of Subversion - layers application teams don't have direct
access. My (forlorn) hope is there's a way of extending the keywords, so the
application team could reference these other bookkeeping artif
> In that case I would recommend sending a mail to
users{_AT_}tortoisesvn.tigris.org
> instead of this list, as it would have to be fixed in TortoiseSVN.
Hi Bert,
thank you very much for your answers. As suggested I placed this issue
on
the tortoise list.
Kind regards,
Markus
> -Original Message-
> From: Walser Markus [mailto:markuswal...@schleuniger.ch]
> Sent: maandag 10 mei 2010 14:56
> To: Bert Huijben; users@subversion.apache.org
> Subject: AW: Automatically merge of new binary file.
>
> Hi Bert
>
> Sorry I forgot this important information:
>
> It was
Hi Bert
Sorry I forgot this important information:
It was Tortoise 1.6.8 Build 19260 (SVN 1.6.11).
Regards,
Markus
-Ursprüngliche Nachricht-
Von: Bert Huijben [mailto:b...@qqmail.nl]
Gesendet: Montag, 10. Mai 2010 14:53
An: Walser Markus; users@subversion.apache.org
Betreff: RE: Auto
> -Original Message-
> From: Walser Markus [mailto:markuswal...@schleuniger.ch]
> Sent: maandag 10 mei 2010 14:25
> To: users@subversion.apache.org
> Subject: Automatically merge of new binary file.
>
> Hi
>
> Recently I ran into following subversion use case:
>
> 1. A new binary file
Hi,
1: Did backup of live repository as below:
hot-backup.py --archive-type=zip /my/svn/repo /my/svn/backup
2: Unzipped /my/svn/backup/repo-7.zip
3: checkout /my/svn/backup/repo-7 (using Tortoise)
4: On commit, am getting below error in Apache error_log
###
Can't create directory
Hi
Recently I ran into following subversion use case:
1. A new binary file was created in a working copy 1 and *not* added:
e.g. C:\Test\WorkingCopy1\BinaryFile.pdf
2. In another working copy 2 of the same repo another binary file with
the same filename but different content was created a
Here's the whole thing, minus unconcerned subprojects:
Properties on '$REPO/trunk/project/src/test/resources/log4j.properties':
svn:mergeinfo
/branches/project-1.10/src/test/resources/log4j.properties:2344-2345,2347,2349,2351,2361,2363,2405
/branches/project-1.13/src/test/resources/lo
On Mon, May 10, 2010 at 12:08:15PM +0800, Jean Seurin wrote:
> Hi Stefan,
>
> mergeinfo properties are exactly as I mention for the file causing problems:
>
> all and only the 5 files concerned with the problem have been
> commited after a merge from the trunk, empty of modification, but
> with t
On Fri, May 7, 2010 at 8:08 PM, BD wrote:
>
> So the question remains, taking physical restraints out of the question, is
> there anyone out there who knows about managing the risks assocciated with
> having two or more apache/svn nodes accessing repos that are stored on a
> shared NFS storage sy
On Friday 07 May 2010, Arpad Ilia wrote:
> Is there somewhere a generic linux binary distribution of subversion? One
> that just needs to be unpacked and needs no root privileges on a debian
> system.
No, Subversion is still compiled to CPU-specific code, so there can not be
generic binaries. Tha
> > -Original Message-
> > From: David Darj [mailto:z...@alagazam.net]
> > Sent: Tuesday, 27 April 2010 6:26 AM
> > To: Cooke, Mark
> > Cc: users@subversion.apache.org; Troy Simpson
> > Subject: Re: Tigris binary packages for Windows
> >
> > On 2010-04-26 13:58, Cooke, Mark wrote:
> > > Hi
21 matches
Mail list logo
