Re: Subversion Exception!
It's definitely not a unique occurrence. Colleague of mine encountered this too recently. Our repository's working copy size is ~1TB populated with files around 5MB. This exception pops up during cleanup operation (probably after an interrupted update), preventing it from finishing. As the working copy is stuck in locked state, it's no longer usable once this happens and needs to be re-downloaded. Unfortunately I don't have a copy of the corrupted working copy, so I can't provide more details. On Fri, Oct 2, 2020 at 1:28 AM Ryan Schmidt wrote: > > > On Oct 1, 2020, at 17:11, Brian Stuart wrote: > > > --- > > Subversion Exception! > > --- > > Subversion encountered a serious problem. > > Please take the time to report this on the Subversion mailing list > > with as much information as possible about what > > you were trying to do. > > What were you doing when this happened? > > > But please first search the mailing list archives for the error message > > to avoid reporting the same problem repeatedly. > > You can find the mailing list archives at > > https://subversion.apache.org/mailing-lists.html > > > > Subversion reported the following > > (you can copy the content of this dialog > > to the clipboard using Ctrl-C): > > > > In file > > > 'D:\Development\SVN\Releases\TortoiseSVN-1.14.0\ext\subversion\subversion\libsvn_wc\wc_db.c' > > line 10238: assertion failed (svn_dirent_is_absolute(local_abspath)) > > --- > > OK > > --- > > >
Upgrading visual svn server from 3.7.0 using svn 1.9.7 - how?
We are using this setup: - Main server is running on Windows Server 16 Standard using VisualSVN version 3.7.0, which apparently uses svn 1.9.7 - The server is using svnsync nightly to synchronize over the Internet to a mirror SVN server version 1.9.7 running on Ubuntu 18.04 Server on a different location entirely. No user operations are allowed on the mirror, it is just a backup. My problem is this: The VisualSVN server is seriously out of date and needs to be upgraded. In its own management console it suggests upgrading to 4.2.2 but does not say which version of svn will then be running. In fact it seems like they are intentionally hiding the svn version in their web pages.. :( And I suspect that there might be problems concerning the svnsync commands if the backup mirror server is not upgraded to the same svn version, right? But how do I do that on Ubuntu when I cannot find out which svn version they use? Or does it not matter, i.e. can the main and mirror servers be using different svn versions? -- Bo Berglund Developer in Sweden
Re: Upgrading visual svn server from 3.7.0 using svn 1.9.7 - how?
Den fre 2 okt. 2020 kl 18:24 skrev Bo Berglund : > We are using this setup: > - Main server is running on Windows Server 16 Standard using VisualSVN > version 3.7.0, which apparently uses svn 1.9.7 > > - The server is using svnsync nightly to synchronize over the Internet > to a mirror SVN server version 1.9.7 running on Ubuntu 18.04 Server on > a different location entirely. > No user operations are allowed on the mirror, it is just a backup. > > My problem is this: > The VisualSVN server is seriously out of date and needs to be > upgraded. In its own management console it suggests upgrading to 4.2.2 > but does not say which version of svn will then be running. > In fact it seems like they are intentionally hiding the svn version in > their web pages.. :( > I checked our installation of 4.2.2 and it seems to be running 1.10.6. VisualSVN Server is installing the Subversion command line tools in C:\Program Files\VisualSVN Server\bin so I simply opened cmd.exe and executed svn --version. And I suspect that there might be problems concerning the svnsync > commands if the backup mirror server is not upgraded to the same svn > version, right? > I checked quickly with a brand new Ubuntu 18.4 VM running svn 1.9.7 and svnsync works both if initiated from the Ubuntu box (connecting to VisualSVN Server using https) and if initiated from Windows (using svn+ssh and plink with public keys). Of course, YMMW. > But how do I do that on Ubuntu when I cannot find out which svn > version they use? > Or does it not matter, i.e. can the main and mirror servers be using > different svn versions? > In general use you are free to mix different versions of the server and the client so I would assume this also goes for svnsync. And it's not too far between 1.9 and 1.10. Others on the list might be able to give a more detailed answer but why not test it :-) -- > Bo Berglund > Developer in Sweden > > Kind regards Daniel
Re: Upgrading visual svn server from 3.7.0 using svn 1.9.7 - how?
On Fri, 2 Oct 2020 19:42:03 +0200, Daniel Sahlberg wrote: >Den fre 2 okt. 2020 kl 18:24 skrev Bo Berglund : > >> We are using this setup: >> - Main server is running on Windows Server 16 Standard using VisualSVN >> version 3.7.0, which apparently uses svn 1.9.7 >> >> - The server is using svnsync nightly to synchronize over the Internet >> to a mirror SVN server version 1.9.7 running on Ubuntu 18.04 Server on >> a different location entirely. >> No user operations are allowed on the mirror, it is just a backup. >> >> My problem is this: >> The VisualSVN server is seriously out of date and needs to be >> upgraded. In its own management console it suggests upgrading to 4.2.2 >> but does not say which version of svn will then be running. >> In fact it seems like they are intentionally hiding the svn version in >> their web pages.. :( >> > >I checked our installation of 4.2.2 and it seems to be running 1.10.6. >VisualSVN Server is installing the Subversion command line tools in >C:\Program Files\VisualSVN Server\bin so I simply opened cmd.exe and >executed svn --version. > >And I suspect that there might be problems concerning the svnsync >> commands if the backup mirror server is not upgraded to the same svn >> version, right? >> > >I checked quickly with a brand new Ubuntu 18.4 VM running svn 1.9.7 and >svnsync works both if initiated from the Ubuntu box (connecting to >VisualSVN Server using https) and if initiated from Windows (using svn+ssh >and plink with public keys). Of course, YMMW. > > >> But how do I do that on Ubuntu when I cannot find out which svn >> version they use? > > >> Or does it not matter, i.e. can the main and mirror servers be using >> different svn versions? >> > >In general use you are free to mix different versions of the server and the >client so I would assume this also goes for svnsync. And it's not too far >between 1.9 and 1.10. Others on the list might be able to give a more >detailed answer but why not test it :-) Thanks! I retrieved the svn version using the same way as you (svn --version on command line)... I will make a test as soon as I have fixed a broken OpenVPN channel to the office. It has stopped working even though I can ping the box. Unfortunately it sits across the ocean in Texas so it is not so easy. And I don't want to risk the upgrade unless I have an extra working OpenVPN server on the system. -- Bo Berglund Developer in Sweden
