LyX ⇒ Problems with SVN features in Lyx 2.0 and Windows 7 64bit

[tjosgood]

Hello everyone, I have spent hours on Google trying to find information relating to the problems im having but it doesn't seem like Lyx is mainstream enough to come up so I thought I would tap the knowledge of the Lyx forums!

Basically I want to have my documents under SVN version control using the integrated File>Version Control menu. I have done:

Installed CollabNet SVN tools
Installed Tortoise SVN which i already use for Matlab and its all working fine
put all my Lyx files into a working directory,
Made a repo by importing the directory and then Checking it out

I have the hidden .svn folder in my working directory now and all the Lyx files exist on my SVN server.

However when I open Lyx and goto File>Version control it still offers me "Register..." only and not the check(in/out) commands as described in the Additional features manual.

If I try to do register anyway it fails saying there was some problem (very useful error message btw) if I run the same command manually from command line it turns out the error is of course that the file is already versioned and added.

If I make a new Lyx file and click Register... the command succeeds and TortoiseSVN marks the file with a + but the file does not end up in my repo. Lyx then reloads the file but after doing so it thinks the file is still not registered as the file menu still shows the same "Register.." command and nothing else.

So essentially there apprears to be an issue with Lyx detecting the existence of a file on the REPO or in the local .svn folder.

Im using Lyx 2.0 and Windows 7 64bit with 64bit CollabNet SVN package.

Any help would be greatly appreciated!

Thanks, Tom.

[tjosgood]

Nobody has any idea whatsoever? Was the question not stated clearly enough?

[Chris_P]

Hello.

I believe the issue stems from the fact that LyX doesn't support SVN 1.7[1]. I'm currently fighting through this same issue, and have resigned myself to update LyX from 2.0.3 to 2.0.5.1, as this is less disruptive than pulling SVN and reinstalling, etc. at this time.

[1] From this terrible, terrible email chain.

[scottkosty]

Hello.

I believe the issue stems from the fact that LyX doesn't support SVN 1.7[1]. I'm currently fighting through this same issue, and have resigned myself to update LyX from 2.0.3 to 2.0.5.1, as this is less disruptive than pulling SVN and reinstalling, etc. at this time.

[1] From this terrible, terrible email chain.

Yes, LyX still does not support SVN 1.7 and I don't know if there are plans to do so. It supports SVN 1.5 and 1.6. Note that there is now support in the development version for Git (tested with version 1.7). If you happen to use Ubuntu, it's very easy to install the development version (alongside your current stable version without messing anything up) with the PPA:
http://wiki.lyx.org/LyX/LyXOnUbuntu#toc3

[Chris_P]

Hello.

I believe the issue stems from the fact that LyX doesn't support SVN 1.7[1]. I'm currently fighting through this same issue, and have resigned myself to update LyX from 2.0.3 to 2.0.5.1, as this is less disruptive than pulling SVN and reinstalling, etc. at this time.

[1] From this terrible, terrible email chain.

Yes, LyX still does not support SVN 1.7 and I don't know if there are plans to do so. It supports SVN 1.5 and 1.6. Note that there is now support in the development version for Git (tested with version 1.7). If you happen to use Ubuntu, it's very easy to install the development version (alongside your current stable version without messing anything up) with the PPA:
http://wiki.lyx.org/LyX/LyXOnUbuntu#toc3

Well, it would appear that this is at least in the works. So all hope is not lost. OP, if you ever come back, this may well be the issue, especially if things were working and then ... weren't. (That's what happened with me; I updated my TortoiseSVN build and that seems to have broken SVN & LyX. Installing Slik-Subversion 1.69 and then 1.60 didn't fix things.)

It doesn't look like this will be addressed in LyX 2.1.

(This isn't a bash against LyX; rather, it is BECAUSE I enjoy writing with it so much that makes this frustrating for me!)

[scottkosty]

(This isn't a bash against LyX; rather, it is BECAUSE I enjoy writing with it so much that makes this frustrating for me!)

Your frustration is definitely understandable. I hope it gets fixed for you someday.