Hi,
What I want to do is, create app (may be WCF service) which will do smart
evidence about changes in svn vs our bugtrack systém (mantis).
I will parse output from svnlook and I will try to make decision what that
change does mean.
If that was creation of branch, tag, Update and so on.
I
I run a small team of web developers (6) who all work from an in-house
repository. We make lots of commits and often and notice the performance gets
pretty bad. Sometimes taking as long as 2 minutes to commit a change. We rely a
lot on server-side software so we often need to commit to see what
On Wed, May 5, 2010 at 09:21, Brendan Farr-Gaynor
bren...@resolutionim.com wrote:
I run a small team of web developers (6) who all work from an in-house
repository. We make lots of commits and often and notice the performance gets
pretty bad. Sometimes taking as long as 2 minutes to commit a
Hello,
I am running SVN/DAV/Apache:
Apache/2.2.15 (Unix) mod_ssl/2.2.15 OpenSSL/FIPS DAV/2 SVN/1.6.11 configured
I waited for 1.6.11 to come out so I could stop having to open my repository
to all users *=r , so I upgraded to 1.6.11, and closed the permissions to the
repository root #*=r,
Hi Andy,
Thanks for your response! Running local copies of the environment doesn't seem
practical in this case, my guys are working on 10+ projects at a time all of
which can be in different states and which need many different modules in place
via apache and php which would take forever to
The fix was to the client, not the server. Did you use a 1.6.11
client? It looks like you are using 1.6.6.
This was never a server problem. The problem was that the command was
changed in a way such that the client needed to access the root of the
repository. The client was fixed to not need
On 5/5/2010 8:46 AM, Brendan Farr-Gaynor wrote:
Hi Andy,
Thanks for your response! Running local copies of the environment doesn't seem
practical in this case, my guys are working on 10+ projects at a time all of
which can be in different states and which need many different modules in place
I have developing on xp using TortoiseSVN ( 1.38). In my project I am
committing at the directory level and all the files in the directory
have a green icon. But icon for directory stays red. I have tried svn
clean but no changes to the color of the icon. With the red Icon - I am
not sure
Hi,
I've had a svnsync job running every day since Mar 3 with no issues. Today May
5 it will no longer synchronize with the below error. Any way to fix this
without starting over (if that would work)?
svnsync synchronize file:///misc_sourcectrl01/svnrepositories/GRCC
svnsync: Error while
I have developing on xp using TortoiseSVN ( 1.38). In my project I am
committing at the directory level and all the files in the directory have a
green icon. But icon for directory stays red. I have tried svn clean but no
changes to the color of the icon. With the red Icon – I am not sure
Hi,
On 05/05/2010 05:08 PM, Howard Davis wrote:
I have developing on xp using TortoiseSVN ( 1.38). In my project I am
committing at the directory level and all the files in the directory
have a green icon. But icon for directory stays red. I have tried svn
clean but no changes to the color of
Hi,
On 05/05/2010 05:08 PM, Howard Davis wrote:
I have developing on xp using TortoiseSVN ( 1.38). In my project I am
committing at the directory level and all the files in the directory
have a green icon. But icon for directory stays red. I have tried svn
clean but no changes to the
On 5/5/2010 10:25 AM, David Weintraub wrote:
* Don't store binary files in Subversion -- especially big ones that
change a lot. Use a Release Repository or a Build Server to store
binaries. We use Nexus and Hudson.
Side question on this topic: do you have a generic way to map the
binaries
Does anyone know of a way to backup/move/copy checked out working copies
such that you can skip all the parts that 'svn update' would
reconstruct? I'm about to copy the home directories of a machine used
mostly for checkout/build/test operations to a remote location and it
occurred to me that
On May 5, 2010, at 10:12, Les Mikesell wrote:
On 5/5/2010 8:46 AM, Brendan Farr-Gaynor wrote:
Thanks for your response! Running local copies of the environment doesn't
seem practical in this case, my guys are working on 10+ projects at a time
all of which can be in different states and
The repo in on a Unix box located at svnrepo/sandbox accessing via tortoise on
a
windows machine with the latest releases. When I try to do a commit as user
dev1, psswd dev1, I get the following error:
Command: Commit
Error: Commit failed (details follow):
Error: Authorization
Not an answer to your issue, but please see:
http://subversion.apache.org/docs/community-guide/mailing-lists.html#fresh-post
Hi,
I have checked out a project and very thing works file. However, today
after some changes, when I try to commit the changes I got:
Error Working copy 'c:\work2\test\include' locked
Erro Please execute the 'Cleanup' command.
At the dos prompt I type: svn cleanup and then I got error
I agree with the general advice already given in this thread: you
should first try to find out where the bottleneck is.
- It can be client-side (e.g. before even sending the commit the
working copy will be locked. This can be very slow with big working
copies (lots of directories), especially on
20 matches
Mail list logo
