Subversion Exception Updating

Hi everyone. An exception just happened when I execute a regular update of my local repository: In file 'D:\Development\SVN\Releases\TortoiseSVN-1.8.7\ext\subversion\subversion\libsvn_wc\update_editor.c' line 1550: assertion failed (action == svn_wc_conflict_action_delete) The exception

Re: How to control access of a subversion repo subfolder via AD groups

I'll add that where we've deployed Subversion access controls, we use mod_authz_svn, and generate its contents from other sources. Not that hard to scan AD, and generate group information that can be stuffed into the access file. Eric On Wed, Jul 9, 2014 at 12:56 PM, Ben Reser wrote: > On 7/7/

Re: Adding [svn users] to subject

On 7/7/14 6:23 AM, Notes Jonny wrote: > Have you thought about adding [svn users] to prefix the subject of emails? > > It would make my mailbox simpler to prioritise all emails.. Currently > I need to read the subjects.. or implement some complex filtering to > folder of svn users emails.. Modify

Re: How to control access of a subversion repo subfolder via AD groups

On 7/7/14 3:56 AM, Ankush Grover wrote: > I am trying to setup Subversion authentication through Active Directory > authentication and authorization through Active Directory groups.Everything is > working fine but the issue I am facing is when I want to restrict access to > subdirectorys of a subve

SVN 1.8.8 exception

I haven't found any reports posted in the archives that are an exact match to this issue, so I'm posting this here as requested by the error message. The error message is as follows: --- Subversion Exception! --- Subversion encountered a serious p

Subversion Exception! "line 143: assertion failed (stream->read_fn != NULL)"

Hi, I send you the message I received when I was trying to commit an update on a file that I was working with. I use a VPN connection to use SVN, and, at the first two attempts of commit I was not able to connect to the VPN, therefore, I cancelled the transaction. Once I was able to connect to VPN

Re: Can't read length line in file X [500, #200002]

Hi I looked at the log of revision comments and found that the broken revision is purely adding files that are from another repository at a particular revision number. I'm in the process of get a copy of that repository. I took a dump of the repository with the corrupt revision up to that broken

Can't read length line in file X [500, #200002]

Hi I'm using Subversion 1.6.9 via the CollabNet Subversion Server. When trying to check out part of the repository I had an error and saw the following in the Apache logs: [Wed Jul 09 10:26:35 2014] [error] [client X] Provider encountered an error while streaming a REPORT response. [500, #0] [We

Re: SVN 1.8 Kerberos Client problems

Hi! Firstly, thanks for your quick answer! On 8 July 2014 21:24, Lieven Govaerts wrote: > Hi Nico, > [...] >> >> Everything ran fine so far. I then upgraded to TSVN 1.8.7 which ships >> with svn 1.8.9 binaries. >> Now, on every repository involving action I get kerberos errors in my >> apache lo

RE: Problems with subversion

If I remember correctly Subversion 1.1 used Berkeley DB (BDB) for various purposes - for example the repository format might be BDB. BDB relied upon file locking to enforce data consistency. As I mentioned not all implementations of NFS servers fully implement file locking - this is why you are

RE: Problems with subversion

Hello, I connect to a remote file system through a XVC terminal emulator. Platform: UNIX linux Subversion version: 1.1.4 Following my previous e-mail below, I was able to establish that the problem resides in my repository. Whenever I issue any subversion command to the repository like: svnlo