Dear all, (please Cc, I am not subscribed)
I have blogged about this [1] and both Branko Čibej and Stefan Sperling asked me to move the discussion here. [1] https://www.preining.info/blog/2017/10/inconsistent-version-numbers-in-subversion/ I describe my problem * Assume a subversion server and two checkouts * both checkout are completely clean, no out-of-vcs files, no ignored files, no mixed revisions, dead plain svn checkouts. * Furthermore, assume the following set of commits: revision A: file xxx is changed revision A+n: file xxx is changed again revision A+n+m: file xxx is changed and takes the same content as back in revision A Assume two users: User A did 'svn up' between revision A+n and A+n+m User B did 'svn up' in [A, A+n), but NOT in [A+n, A+n+m), and again after A+n+m In this case, the "last comitted revision" (according to 'svn status -v') differ: User A will get A+n+m User B will get A In practice, in our TeX Live main repository, when I do 'svn status -v' in my own checkout, I see: 45627 39121 karl Master/tlpkg/tlpsrc/collection-langgreek.tlpsrc and when I do it on our master checkout (the one that does the daily updates for TeX Live) I see: 45643 44192 karl Master/tlpkg/tlpsrc/collection-langgreek.tlpsrc (empty initial columns deleted). The second number here is -- according to 'svn status -h' -- The last committed revision and last committed author (with -v) ^^^^^^^^^^^^^^^^^^^^^^^ My assumption *was* that this is *consistent* across checkout, but it is not. Is this an intended behavior? All the best Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. + JAIST + TeX Live + Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
