Re: Blocker: svn 1.8 assertion failed

2013-06-21 Thread Rossen Totev
I get the same issue after a clean install of TortoiseSVN 1.8. We use the Unfuddle SVN hosting and it is impossible to make any additional changes on the server side. At this point TortoiseSVN 1.8 is useless for us. On Thursday, June 20, 2013 1:07:59 PM UTC+3, arrigo@exorint.it wrote: > >

Re: Blocker: svn 1.8 assertion failed

2013-06-21 Thread Stefan Sperling
On Fri, Jun 21, 2013 at 01:11:50AM -0700, Rossen Totev wrote: > I get the same issue after a clean install of TortoiseSVN 1.8. > > We use the Unfuddle SVN hosting and it is impossible to make any additional > changes on the server side. At this point TortoiseSVN 1.8 is useless for > us. The pr

Re: Blocker: svn 1.8 assertion failed

2013-06-21 Thread Stefan Sperling
On Fri, Jun 21, 2013 at 10:29:27AM +0200, Stefan Sperling wrote: > On Fri, Jun 21, 2013 at 01:11:50AM -0700, Rossen Totev wrote: > > I get the same issue after a clean install of TortoiseSVN 1.8. > > > > We use the Unfuddle SVN hosting and it is impossible to make any additional > > changes on th

Re: svnmucc installation bug in Subversion 1.8.0

2013-06-21 Thread Philip Martin
Nico Kadel-Garcia writes: > # Compatibility symlink. > # This runs after the target of the same name in build-outputs.mk. > INSTALL_EXTRA_TOOLS=\ > $(MKDIR) $(DESTDIR)$(bindir); \ > test -n "$$SVN_SVNMUCC_IS_SVNSYITF" && \ > ln -sf svnmucc$(EXEEXT) $(DESTDIR)$(bindir)/svnsyitf$(EXEEXT); \ >

Re: Blocker: svn 1.8 assertion failed

2013-06-21 Thread Philip Martin
arrigo.zane...@exorint.it writes: > Hi Philip, > are you saying that chunked trasfer encoding support is required for svn > 1.8 to work? Is there any way to workaround the requirement client-side? Yes, it's a requirement for 1.8.0 if the server claims HTTP/1.1 > HTTP/1.1 411 Length Required > S

Memory cleanup / leakage

2013-06-21 Thread Kai-Uwe . Schieser
Please add me to the answer list, cause I am not subscribed. I am using the Binary Package of Subversion library Version 1.7.9 in my software. Everything works fine so far but a little memory leak I detected in my tests. I am not shure if I use everything as I should. Maybe you can help me.

Re: vimdiff wrapper for diff-cmd not working with 1.8

2013-06-21 Thread Philip Martin
Philip Martin writes: > It's also hard to fix 1.8, how do we pass the information into the > client library without changing the API? Perhaps we could recognise a > special part of the command name or a special external parameter, so > >--diff-cmd svn:interactive:myscript Another user raise

Re: Memory cleanup / leakage

2013-06-21 Thread Ivan Zhakov
On Fri, Jun 21, 2013 at 4:48 PM, wrote: > Please add me to the answer list, cause I am not subscribed. > > > I am using the Binary Package of Subversion library Version 1.7.9 in my > software. > Everything works fine so far but a little memory leak I detected in my > tests. I am not shure if I us

Re: Memory cleanup / leakage

2013-06-21 Thread Daniel Shahaf
kai-uwe.schie...@hydrometer.de wrote on Fri, Jun 21, 2013 at 14:48:35 +0200: > Please add me to the answer list, cause I am not subscribed. > > > I am using the Binary Package of Subversion library Version 1.7.9 in my > software. > Everything works fine so far but a little memory leak I detected

Re: Memory cleanup / leakage

2013-06-21 Thread Branko Čibej
On 21.06.2013 15:48, Ivan Zhakov wrote: > On Fri, Jun 21, 2013 at 4:48 PM, wrote: >> Please add me to the answer list, cause I am not subscribed. >> >> >> I am using the Binary Package of Subversion library Version 1.7.9 in my >> software. >> Everything works fine so far but a little memory leak

[TSVN and svn 1.8.0] Cannot Digest Authenticate.

2013-06-21 Thread Camilo S. Tsumanuma
Hi Dear Subversion Users Forum, I compiled subversion 1.8.0 in CentOS 6.4 using http://comments.gman​e.org/gmane.comp.ver​sion-control.subvers​ ion.user/113594 as guideline. I just used my own previous Apache Server configuration of Digest Authentication for WebDav SVN but it failed like descr

[TSVN and svn 1.8.0] Cannot Digest Authenticate.

2013-06-21 Thread Camilo Sasuke Tsumanuma
Hi Dear Subversion Users Forum, I compiled subversion 1.8.0 in CentOS 6.4 using http://comments.gman​e.org/gmane.comp.ver​sion-control.subvers​ion.user/113594 as guideline. I just used my own previous Apache

Proxy Problem with Subversion 1.8 and Clients with Version 1.8

2013-06-21 Thread Tobias Krieg
Hello, after upgrading to Subversion 1.8 and TortoiseSVN 1.8 (x64) we get some trouble to access our repositories via a reverse proxy. Also we use the svn commandline tool to checkout! When we use the URI to checkout, an error occurs: svn co https:///​svn/repositories/​/

Re: Proxy Problem with Subversion 1.8 and Clients with Version 1.8

2013-06-21 Thread Mark Phippard
On Fri, Jun 21, 2013 at 11:29 AM, Tobias Krieg wrote: > after upgrading to Subversion 1.8 and TortoiseSVN 1.8 (x64) we get some > trouble to access our repositories via a reverse proxy. I expect someone will ask. In another forum before I directed him here he provided the information that their

sunversion 1.8.0 crash on FreeBSD when WC path is symlink (regression)

2013-06-21 Thread Lev Serebryakov
Hello, Users. Here is way to crash subversion 1.8.0 release on FreeBSD -- try to update WC which is symlink to real WC. It worked in 1.7.x. Repository and access scheme and repo's content doesn't matter, "serf" repo is used for illustration, but it crashes with any repo and any scheme (https, sv

Feature Request: revprop for "svn:client" Was: Tree conflict on Fresh checkout

2013-06-21 Thread James Hanley
After some digging into this issue - I am somewhat at a loss. I'm not sure how it happened but I can come up with a best guess that the user may have checked in the change with 1.6.13 - my suspicion is there is an issue with how the properties are stored, but unfortunately he has at lease 3 differ

Re: Feature Request: revprop for "svn:client" Was: Tree conflict on Fresh checkout

2013-06-21 Thread C. Michael Pilato
On 06/21/2013 02:22 PM, James Hanley wrote: > In hind site, if there was a revprop that included the version of the > client, if an artifact issue (such as this) is discovered in the repository, > this rev-prop can succinctly tell the administrator which version of the > client introduced the issue

Re: Advice for changing filename case in SVN on case insensitive system

2013-06-21 Thread Thomas Harold
On 6/20/2013 6:56 PM, Geoff Hoffman wrote: deleting the file from Subversion, then adding the copy with the correct case. Question: Doesn't that blow away revision history? If I didn't care about revision history I would just start over with a fresh repo. If you use "svn mv" to do the change,

Re: Blocker: svn 1.8 assertion failed

2013-06-21 Thread Günther Schabus
Dear Rossen, Exactly the same problem here. We found no solution. We went back to Tortoise SVN 1.7x and reloaded all upgraded working copies. We hope the guys from subversion will find a solution... Have a great weekend, Günther

Re: Subversion Exception! line 647: assertion failed (peg_revnum != SVN_INVALID_REVNUM)

2013-06-21 Thread Shannon
Thomas Harold nybeta.com> writes: > > On 6/20/2013 11:55 PM, Sandeepan Kundu wrote: > > > > Tried going back to 1.7, but it is telling project is in higher version : (( > > > > how to use now, my development is getting affected!!! > > I suggest renaming your old (upgraded to 1.8) working copy o

Re: Advice for changing filename case in SVN on case insensitive system

2013-06-21 Thread Johan Corveleyn
On Fri, Jun 21, 2013 at 12:56 AM, Geoff Hoffman wrote: > Yes, that helps, Dave, thanks. > > But, > > deleting the file from Subversion, then adding the copy with the correct > case. > > Question: Doesn't that blow away revision history? If I didn't care about > revision history I would just start