RE: SVN errors with junction points

2011-08-03 Thread Cooke, Mark
> -Original Message- > From: Stefan Sperling [mailto:s...@elego.de] > Sent: 03 August 2011 22:11 > To: Joost van Dongen > Cc: users@subversion.apache.org > Subject: Re: SVN errors with junction points > > On Wed, Aug 03, 2011 at 06:18:11PM +0200, Joost van Dongen wrote: > > Our SVN checko

RE: TortoiseSVN crashes

2011-08-03 Thread Cooke, Mark
Hello, First: TortoiseSVN has its own mailing list (see http://tortoisesvn.net/community.html), if your problem is specifically with Tortoise then that should be your first point of contact. However... > -Original Message- > From: Georgiy Osipov [mailto:gaosi...@gmail.com] > Sent: 03

Issue: Folders with space not getting commited in a write-through-proxy environment

2011-08-03 Thread Ajith Thampi
Hi, I have setup a write-through-proxy setup. I am able to created and commit folders with space into my Master URI from local. When i try to commit a folder with space from the Slave/Mirror repo, the commit falls into failure. Part of error shown. svn ci -m "updated" Sending this is a long f

Re: SVN errors with junction points

2011-08-03 Thread Stefan Sperling
On Wed, Aug 03, 2011 at 06:18:11PM +0200, Joost van Dongen wrote: > Our SVN checkout is too big to fit on my small SSD harddisk, so I have > spread it over two harddisks using Windows 7 junction points. Sorry, Subversion doesn't support NTFS junctions. See http://subversion.tigris.org/issues/show_

assertion failed (svn_dirent_is_absolute(local_abspath)) in SVN 1.7 beta

2011-08-03 Thread Dave Huang
Using TortoiseSVN 1.7.0 beta 2 on WinXP SP3: TortoiseSVN 1.6.99, Build 21735 - 32 Bit , 2011/07/28 20:35:52 Subversion 1.7.0, -dev apr 1.4.5 apr-utils 1.3.12 neon 0.29.6 OpenSSL 1.0.0d 8 Feb 2011 zlib 1.2.5) I was in the middle of merging a few revisions from trunk to a branch (using the "Merge

Re: 1.7 check-swig-py failure

2011-08-03 Thread tsteven four
Thanks for your consideration of this issue. Unfortunately I have to apologize, this is not an issue with r878293. The issue arises when you are building subversion against apr/apu that has already been installed in a special location, was built with the internal expat, and there is another incom

Re: Subversion transactions within post-commit

2011-08-03 Thread David Weintraub
On Wed, Aug 3, 2011 at 2:31 PM, Ray Rashif wrote: > On 4 August 2011 01:59, David Weintraub wrote: > Thanks guys. I'm just stupid. I've been going on and on about what we > want to do, but I haven't even stated the obvious: > > * It's just about removing stale files from being tracked by > Subve

Re: Subversion transactions within post-commit

2011-08-03 Thread Ray Rashif
On 4 August 2011 01:59, David Weintraub wrote: > ... > SNIP > ... > I have what I call my Kitchen Sink pre-commit trigger that does all > sorts of stuff. One of the tasks it can do is "ban" files based upon > their name (either regular expression or Ant glob). If a user adds a > file with a forbid

Re: Subversion transactions within post-commit

2011-08-03 Thread David Weintraub
On Tue, Aug 2, 2011 at 5:00 PM, Ray Rashif wrote: > OK, looks like I have to explain a bit further to clear this up and > hopefully get some solutions. > > We use the repository to directly serve some files (so Subversion > updates are immediately reflected). Something like > http://subversion.apa

TortoiseSVN crashes

2011-08-03 Thread Georgiy Osipov
Hi, After updating to TortoiseSVN 1.6.99, Build 21709 - 32 Bit , 2011/07/22 16:21:33, a crash follows each operations with repository (some operations works fine, some fails, but crash report after each). Crash message is about memory 0x0200ad24 reading. System is Windows XP professional. When I

SVN errors with junction points

2011-08-03 Thread Joost van Dongen
Our SVN checkout is too big to fit on my small SSD harddisk, so I have spread it over two harddisks using Windows 7 junction points. However, this gives me weird SVN errors. These folders are my situation: E:\SVN\BigFolder D:\SVN\SmallFolder D:\SVN\BigFolder >> junction point towards E:\SVN\BigFol

Re: svn docx missing mime type workaround?

2011-08-03 Thread Daniel Shahaf
I'm not sure how that interacts with the internal URL svn uses --- e.g., those /repos/!svn/* URLs that sometime appear in error messages. kmra...@rockwellcollins.com wrote on Wed, Aug 03, 2011 at 11:14:18 -0500: > IE7/8 do not like to correctly "open" MS office .docx files served > directly > fro

svn docx missing mime type workaround?

2011-08-03 Thread kmradke
IE7/8 do not like to correctly "open" MS office .docx files served directly from a svn repo with the default svn mime type. They will only allow you to save them since it determines they are zip files. The obvious solution is to just add the correct svn:mime-type, which works fine, although it r

svnlook changed - howto see all deleted files in pre-/post-commit hooks

2011-08-03 Thread Jan Ciesko (GMAIL)
Dear SVN-experts, I'd like to ask if there is a way to see which particular files have been deleted when a directory deletion has been commited. Example: I add to a repository BAR/Apps the folder Jacobi. With "svnlook changed "$REPOS"" in the post-commit hook I get the output: A BAR/Apps/

svnlook changed - howto see all deleted files in pre-/post-commit hooks

2011-08-03 Thread Jan Ciesko (GMAIL)
Dear SVN-experts, I'd like to ask if there is a way to see which particular files have been deleted when a directory deletion has been commited. Example: I add to a repository BAR/Apps the folder Jacobi. With "svnlook changed "$REPOS"" in the post-commit hook I get the output: A BAR/Apps/

Re: cannot create directory in /db/transactions/

2011-08-03 Thread Michael Chen
just double checked /etc/selinux/config and found SELinux is disabled on my CentOS 5 by default. It seems the system does not has Apparmor. Reboot the system, and the problem went away. Now I can create directory in ../db/transaction. Not sure what's the reason behind the scene. -- All the

RE: Proactive Question on setting up SVN repo

2011-08-03 Thread Brenden Walker
Can you install SVN on the NAS? I'm running a QNAP NAS at home with subversion on it. Just an idea. From: David White [mailto:dwr...@gmail.com] Sent: Wednesday, August 03, 2011 7:56 AM To: users@subversion.apache.org Subject: Proactive Question on setting up SVN repo We have a Blade Center do

Re: Proactive Question on setting up SVN repo

2011-08-03 Thread Stefan Sperling
On Wed, Aug 03, 2011 at 07:56:15AM -0400, David White wrote: > I have SVN 1.6.11 installed on a fresh install of CentOS 6 (on the Blade > Center). I have mounted the NAS running NFS to be used as the repository > storage location on /var/svn/. When I run "svnadmin create > /var/svn/new-repo", it ha

Re: Proactive Question on setting up SVN repo

2011-08-03 Thread Daniel Shahaf
That message probably comes from SQLite. SQLite uses the same locks FSFS uses internally. FSFS depends on locks to ensure consistency with multiple writers. FSFS does not guarantee correctness without locks. (Concretely: without locks, if you run 'svnadmin pack' twice concurrently, you can lose

Proactive Question on setting up SVN repo

2011-08-03 Thread David White
We have a Blade Center downstairs with a NAS mounted to it for additional storage. I'm in the process of setting up a SVN server for folks in our company umbrella to use. My boss wants a folder on the NAS to be used as the repo storage location, due to the extra space and redundancy we have on it.

SVN Export

2011-08-03 Thread Bhat, Ashish
Hello All, I wanted to export the file from a location in branch to my local machine. However, I am getting the following error message. M:\Releases\20110805>svn export -r 186 http://unity-prod.csfb.net:8081/essbase/branches/test_branch/Essbase/EPM /Batch/EPMPBT1/app/psfsprod/dct/rules/dcts

Re: Strange behavior on directory delete/commit

2011-08-03 Thread Stefan Sperling
On Wed, Aug 03, 2011 at 11:27:48AM +0200, Dominik Psenner wrote: > > You must still use svn commands instead of OS > >commands in 1.7. That won't change. I don't think it will ever change. > >The reason is that Subversion tracks operations explicitly, rather than > >implicitly. In other words, Subv

RE: Strange behavior on directory delete/commit

2011-08-03 Thread Dominik Psenner
>[snip] >> Subversion is still an observer and whatever a user does, he must tell >> Subversion what he did in cases where subversion can't >> understand it by >> itself (i.e. file/folder rename/move that preserve history across the >> revisions). Every VCS I know works like this. Maybe one invents

RE: Strange behavior on directory delete/commit

2011-08-03 Thread Andreas Tscharner
[snip] > Subversion is still an observer and whatever a user does, he must tell > Subversion what he did in cases where subversion can't > understand it by > itself (i.e. file/folder rename/move that preserve history across the > revisions). Every VCS I know works like this. Maybe one invents a VC

RE: Strange behavior on directory delete/commit

2011-08-03 Thread Dominik Psenner
>I'm not sure you understand the kinds problems the new working copy >format is settling. For me it settles the major problem of multiple .svn folders in a checkout. > You must still use svn commands instead of OS >commands in 1.7. That won't change. I don't think it will ever change. >The reason

Re: Strange behavior on directory delete/commit

2011-08-03 Thread Stefan Sperling
On Wed, Aug 03, 2011 at 10:25:07AM +0200, Dominik Psenner wrote: > >Then you must explain it to them. :) To move or delete items in a working > >copy, you must use svn commands. You must not use OS commands. That's just > >how it is. > > This is going to be a long journey. *jokingly* > > Thanks f

Re: svn-crash-log20110801153746, svn-crash-log20110802202337

2011-08-03 Thread Stefan Sperling
On Tue, Aug 02, 2011 at 08:38:47PM +0400, Alexander Gushchin wrote: > Process info: > Cmd line: svn merge -r 12265:13078 svn://ekb.developonbox.ru:3690/DOB2PE/tr > Version: 1.6.12 (SlikSvn/1.6.12) WIN32, compiled Jun 22 2010, 20:45:23 Version 1.6.12 of SlikSvn has known crash problems. Please upd

RE: Strange behavior on directory delete/commit

2011-08-03 Thread Dominik Psenner
>Then you must explain it to them. :) To move or delete items in a working >copy, you must use svn commands. You must not use OS commands. That's just >how it is. This is going to be a long journey. *jokingly* Thanks for the insights and incredibly fast answers! It's awesome that you're working o

Re: Strange behavior on directory delete/commit

2011-08-03 Thread Ryan Schmidt
On Aug 3, 2011, at 03:17, Dominik Psenner wrote: >> I doubt it. Or rather, the behavior is not broken. The user is broken. As I >> said: "svn commit foo" should have worked fine if you had not run "rmdir >> foo" beforehand. Don't run "rmdir foo". Just run "svn rm foo" followed by >> "svn commit f

RE: Strange behavior on directory delete/commit

2011-08-03 Thread Dominik Psenner
>I doubt it. Or rather, the behavior is not broken. The user is broken. As I >said: "svn commit foo" should have worked fine if you had not run "rmdir >foo" beforehand. Don't run "rmdir foo". Just run "svn rm foo" followed by >"svn commit foo" and everything should work. True - it's nothing totall

Re: Strange behavior on directory delete/commit

2011-08-03 Thread Ryan Schmidt
On Aug 3, 2011, at 03:04, Dominik Psenner wrote: >> I think "svn commit foo" would work fine, provided you do not "rmdir foo" >> first; that was your error. >> >> I also have a feeling Subversion 1.7's new working copy arrangement will >> fix or at least change this behavior. > > So there's sti

RE: Strange behavior on directory delete/commit

2011-08-03 Thread Dominik Psenner
>> I think SVN is behaving correctly. When you do svn commit foo you're >telling Subversion to commit changes made in foo. There are no changes in >foo because it's been deleted. The changes, instead, are in its parent >directory, the one from where you issued your commands. That's why svn >commi w

RE: Strange behavior on directory delete/commit

2011-08-03 Thread Dominik Psenner
>You could also delete the directory directly in the repository using "svn >delete -m ". This way you would avoid the problem of >committing partial changes of your working copy. .. which is just another workaround.