thanks for confirming that the additional SVN option works around that new issue for you too! i will update the LogonExtras page accordingly.<div><br></div><div>yes, by default an ’svn update‘ in a parent directory will descend into ’switch‘ed in sub-directories and request updates from their repository. so, in a sense, the LOGON tree serves as a collection of modules, some maintained in their own repository, that are configured for interoperability.<div><div><br></div><div>’<a href="http://svn.delph-in.net">svn.delph-in.net</a>‘, ’<a href="http://svn.emmtee.net">svn.emmtee.net</a>’, and ’<a href="http://logon.emmtee.net">logon.emmtee.net</a>‘ (for LOGON developers only) in fact all (currently) are prefixes to the same SVN namespace. in you list below, ’/trunk‘ is the LOGON tree, whereas ’/erg/trunk‘ is the ERG.</div><div><br></div><div>all clear now? oe</div><div><br></div><div><br>On Friday, March 15, 2019, Alexandre Rademaker <<a href="mailto:arademaker@gmail.com">arademaker@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Stephan,<br>
<br>
Thank you for your answer. Yes, it worked as you expected. Since I am not familiar with SVN, how to keep the local directory updated after this command? An svn update in the LOGONROOT will also update the terg directory? Maybe it is important to say some words about it. The command was:<br>
<br>
svn switch <a href="http://svn.emmtee.net/erg/trunk" target="_blank">http://svn.emmtee.net/erg/<wbr>trunk</a> . --ignore-ancestry<br>
<br>
So I am assuming that all 3 repositories below are in sync, right? Page <a href="http://moin.delph-in.net/LogonExtras" target="_blank">http://moin.delph-in.net/<wbr>LogonExtras</a> says that 1 and 3 is the same SVN repository, but what about 2?<br>
<br>
1. <a href="http://svn.emmtee.net/trunk" target="_blank">http://svn.emmtee.net/trunk</a><br>
2. <a href="http://svn.delph-in.net/erg/trunk" target="_blank">http://svn.delph-in.net/erg/<wbr>trunk</a><br>
3. <a href="http://logon.emmtee.net/erg/trunk" target="_blank">http://logon.emmtee.net/erg/<wbr>trunk</a><br>
<br>
All the best,<br>
<br>
--<br>
Alexandre Rademaker<br>
<a href="http://arademaker.github.io" target="_blank">http://arademaker.github.io</a><br>
<br>
<br>
> On 15 Mar 2019, at 03:39, Stephan Oepen <<a href="mailto:oe@ifi.uio.no">oe@ifi.uio.no</a>> wrote:<br>
> <br>
> hi alexandre,<br>
> <br>
> i can reproduce the issue you describe on one of my linux environments, while the instructions as published work fine on others. it appears newer versions of the SVN client enforce some testing that gets in the way. and for all i can tell right now, that is an unwarranted error report.<br>
> <br>
> either way, the problem goes away when i follow the instructions from SVN, i.e. add ‘—ignore-ancestry’ to the ‘switch’ command. could you try that too and report back? if it works for you too, i shall update the LogonExtras page.<br>
> <br>
> in general, you need to use the same base SVN address as for the original ‘checkout’, ‘<a href="http://svn.emmtee.net" target="_blank">http://svn.emmtee.net</a>’ for most people. the purpose of the LOGONSVN environment variable is to enforce such uniformity of SVN access methods.<br>
> <br>
> so please just try the command from the LogonExtras page, with the addition of the ‘—ignore-ancestry’ switch.<br>
> <br>
> cheers, oe<br>
> <br>
<br>
</blockquote></div></div></div>