Re: svnadmin upgrade output message i18n issue

The bug found in svn 1.8.3(r1516576) again :( E:\svnmirror>D:\tools\svn-win32-1.8.3\bin\svnadmin.exe upgrade ZmccPrj 宸插��寰���搴瀹���?璇风�锛绾х�搴��介��瑕�涓�娈垫�堕�?.. 完成升级。 E:\svnmirror>D:\tools\svn-win32-1.8.0\bin\svnadmin.exe upgrade ZmccPrj 已取得版本库锁定。 请稍候；升级版本库可能需要一段时间... 完成升级

Svn merge that deletes files fails with svn: E155023: Can't set properties on x/y/z invalid status for updating properties.

Hello, While merging branch back to trunk I constantly get the error in the subject. Note that x/y/z has svn:mergeinfo property. The property was not added on the branch, but it was already there when the branch was created. Subsequently x/y/z is deleted on branch. The error is generated when

Re: Error after server upgrade to 1.8.3 - E160052: Revprop caching disabled

On 9/5/2013 6:41 PM, Gordon Moore wrote: Is this a known issue with 1.8.3? Any ideas on what is going on, how I can investigate, or what I might do to correct this? I'd start with: - How are you accessing the SVN repository? http? svn+ssh? svn? - What are the ownership and permissions on the

Re: corrupted svn repository with “serialized hash missing terminator” error

Hi Philip, Thanks for the clarification. Does the message mean either in db/revs or in db/revprops 'END' tag is missing ? Regards, Nitin On Thu, Sep 5, 2013 at 11:50 PM, Philip Martin wrote: > Nitin Bhide writes: > > > Hi Stefan, > > > > Thanks for the hint. I tried the fsfsverify and fsfixer

Re: svn 1.8 causing locks to be broken on update

Thanks for your reply. I didn't mean to rush things, only to ask on the status. We can wait for the bug to be fixed, as our OS is possibly too old to run 1.6.17 (RHEL 5.5) and repoforge contains RPM for RHEL5.5 up to 1.6.15 only. Cheers, Felipe On Fri, Sep 6, 2013 at 10:23 AM, Branko Čibej wro

Re: svn 1.8 causing locks to be broken on update

On 06.09.2013 02:06, Felipe Alvarez wrote: > I have upgraded my tortoiseSVN to 1.8.2 which includes svn version > 1.8.3 (r1516576). The problem is still there (locks broken on update). > > I have not seen any progress on the bug report > I

Re: svn 1.8 causing locks to be broken on update

I have upgraded my tortoiseSVN to 1.8.2 which includes svn version 1.8.3 (r1516576). The problem is still there (locks broken on update). I have not seen any progress on the bug report < http://subversion.tigris.org/issues/show_bug.cgi?id=4412> Cheers, Felipe On Fri, Aug 23, 2013 at 11:21 AM,

Error after server upgrade to 1.8.3 - E160052: Revprop caching disabled

I just upgraded my subversion server software from 1.7.2 to to 1.8.3, running on RedHat Linux 6.2.  Almost everything seems to be functioning correctly, however when I try to do an svnadmin dump or svnadmin verify of any of my repositories I get an error like this: svnadmin: E160052: Revprop ca

Re: corrupted svn repository with “serialized hash missing terminator” error

Hi, On Thu, Sep 05, 2013 at 07:54:51PM +0530, Nitin Bhide wrote: >Hi Stefan, > >Thanks for the hint. I tried the fsfsverify and fsfixer also. Both did not >work. Looking back I think the problem started when I upgraded to from >1.7.x to 1.8.1. > >What exactly is 'serialized h

Re: corrupted svn repository with “serialized hash missing terminator” error

Nitin Bhide writes: > Hi Stefan, > > Thanks for the hint. I tried the fsfsverify and fsfixer also. Both did not > work. Looking back I think the problem started when I upgraded to from > 1.7.x to 1.8.1. > > What exactly is 'serialized hash terminator' error ? It means one of the repository files

Re: Planning a SVN upgrade

On 05/09/13 15:46, Maureen Barger wrote: That is a great idea, Giulio. How do you then make the mirrored repo writable? On Mon, Sep 2, 2013 at 4:47 AM, Giulio Troccoli wrote: On 23/08/13 21:09, Maureen Barger wrote: Hi - I am currently planning an upgrade from SVN 1.5 (using svnserve and ssh

Re: Planning a SVN upgrade

That is a great idea, Giulio. How do you then make the mirrored repo writable? On Mon, Sep 2, 2013 at 4:47 AM, Giulio Troccoli wrote: > > On 23/08/13 21:09, Maureen Barger wrote: >> >> Hi - >> I am currently planning an upgrade from SVN 1.5 (using svnserve and >> ssh tunnel) to SVN 1.8.1 fronted

Re: corrupted svn repository with “serialized hash missing terminator” error

Hi Stefan, Thanks for the hint. I tried the fsfsverify and fsfixer also. Both did not work. Looking back I think the problem started when I upgraded to from 1.7.x to 1.8.1. What exactly is 'serialized hash terminator' error ? Regards, Nitin On Sun, Sep 1, 2013 at 4:33 PM, Stefan Sperling wrot

Re: Issue 4039

Ah yes, that was my intention but I forgot about it :-). It's closed as won't fix now. Thanks for the reminder. -- Johan On Thu, Sep 5, 2013 at 3:20 PM, Ivan Zhakov wrote: > Johan, > > I think it may be worth to close issue 4039 as "won't fix" in this case. > Since it's extremely low chance th

Re: Issue 4039

Johan, I think it may be worth to close issue 4039 as "won't fix" in this case. Since it's extremely low chance that we go back to have .svn per every directory. On Tue, Aug 20, 2013 at 3:13 PM, Angelo Tavares wrote: > Yes, I have "subst M: C:\SomeDir\Project\subdir", but thanks for the > feed

RE: SilkSVN client crashing

Hi Bjarne, Can you run the svn log https://svn.netentertainment.com/cm_games_ng/igames/blacklagoon/blacklagoon- common/trunk command. With SlikSvn 1.8.3 (which is available on