mod_dav_svn SVNUseUTF8 option not working

my subversion server is apache-2.4.34/event-MPM and subversion-1.9.7/mod_dav_svn configuration based on example from https://subversion.apache.org/docs/release-notes/1.8.html#hooks cat httpd.conf: SVNHooksEnv /etc/subversion/svnserve.conf SVNUseUTF8 On #not "yes" as example say cat

Re: error

On Oct 24, 2018, at 13:00, Keith Wentworth wrote: > I got this error when I was updating my working copy: > > > D:\Development\SVN\Releases\TortoiseSVN-1.8.7\ext\subversion\subversion\libsvn_wc\wc_db_update_move.c' > line 1039: assertion failed (move_dst_revision == expected_move_dst_revision

Re: Coredump when javahl SVNClient::diff() called with diff-cmd set

On 25.10.2018 12:41, BURT, Matthew J wrote: > > Hi, > >   > > We’ve got a number of developers using the javahl bindings from Eclipse > > via subclipse. > >   > > One of them recently reported a coredump against 1.10.3. I’ve also > > reproduced it with 1.9.7. > >   > > The problem occurs when

Coredump when javahl SVNClient::diff() called with diff-cmd set

Hi, We've got a number of developers using the javahl bindings from Eclipse via subclipse. One of them recently reported a coredump against 1.10.3. I've also reproduced it with 1.9.7. The problem occurs when SVNClient::diff() is called with a diff-cmd defined in the user's ~/.subversion/config

Re: Repository became corrupt on commit

Hi Daniel, > Odd. My first assumption is that the subshell on line 39 isn't behaving > as expected. If you run `svnlook tree --full-paths --show-ids -r 719 > /path/to/repository /trunk/scripts/script.py`, does print a path and a > node-rev id string (which looks like "a.b.c/d-e")? Here is the