[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: inconsistent revision numbers

From: Branko Čibej <brane_at_apache.org>
Date: Mon, 30 Oct 2017 15:11:20 +0100

On 30.10.2017 14:54, Norbert Preining wrote:
> 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.

I'm pretty sure they're not, but see below.

> * 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.

It should be.

I took a look at the TeXlive repository, specifically at that file. In
both cases, wheather the working copy revision (svn update -r X) is
45627 or 45643, that file's last changed revision should be 44192.

Here's the proof:

$ svn info --show-item=last-changed-revision svn://tug.org/texlive/trunk/Master/tlpkg/tlpsrc/collection-langgreek.tlpsrc
44192

$ svn info --show-item=last-changed-revision svn://tug.org/texlive/trunk/Master/tlpkg/tlpsrc/collection-langgreek.tlpsrc_at_45627
44192

> Is this an intended behavior?

That depends on what you did. :)

For example, what does `svnversion` say about your working copy?
Compared to the master?

Unless this is a strange artefact of git-svn, I'd recommend an "svn
update" in your working copy ("your checkout," as you call it) and let's
see what happens.

-- Brane
Received on 2017-10-30 15:11:27 CET

This is an archived mail posted to the Subversion Users mailing list.