Am 07.12.20 um 15:27 schrieb Pavel Sanda: > On Mon, 23 Oct 2017 12:14:41 +0200 Philipp Klaus Krause <p...@spth.de> wrote: >> lyx tries to autodetect if a file is under verison control. When lyx >> 2.2.3 reads an input file, it recursively checks parent directories for >> .svn, .git, etc. >> >> In case it find a .svn directory, it invokes svn info to parse the >> output to see if the file is under version control. For svn, the code is >> in SVN::findFile in lines 1154ff of src/VCBackend.cpp. >> >> However, there is a bug in checking if a file is in svn. If the file is >> in a directory that is not under svn, but a parent directory is under >> svn, lyx will invoke svn info. Since the directory itself is not under >> svn, svn info will fail "svn: E155007: >> '/home/philipp/sdcc-2/build/doc/sdccman.lyx' is not a working copy"; lyx >> considers this an error. > > Looks like correct analysis. > >> This issue makes out-of-tree builds fail. Example: the sdcc manual is a >> .lyx file. When checking out sdcc from svn, and then trying to do an >> out-of-tree build in a directory build, it fails due to this bug. > > Despite the warning from svn info, lyx normally loads up the file, > exports it etc. > So I do not follow what "out-of-tree builds fail" exactly means > or what kind of problem you actually encounter.
AFAIR, when I reported the bug three years ago, it wasn't just a warning, it was an error; lyx -e would fail and not produce output. I just tried again, on my current Debian GNU/Linux system, and it now indeed is just a warning and output is produced by lyx -e. The problem I encountered when I reported the bug: I checked out sdcc from svn, created a subdirectory "build" under it, and built in that directory. That failed, since back then there was an error from lyx -e that stopped the build (the directory "build" not being under version control, but the parent directory being in svn), when I invoked "make" in build/doc to build the manual. I guess the downgrade from error to warning happened in some lyx or svn update during the three years since I reported the bug. Philipp
