[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: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Tue, 31 Oct 2017 00:58:46 +0000

Norbert Preining wrote on Tue, Oct 31, 2017 at 09:34:08 +0900:
> > Fixed in https://svn.apache.org/r1813794 and nominated for backport
> > to 1.9.8. Pizzas to stsp :-)
> Thanks a lot.
> With a fixed/updated subversion client, will I get the updates
> automatically, or do I need also an updated server, and also do some
> special svn up invocations?

You need to upgrade the server (only; the client needn't be upgraded).

As to "special svn up invocations", let me first say that the easiest
way would be to checkout a new working copy.

Having said that, the following should work in an existing working copy:
For each affected file, run an 'svn update' (to either a newer or an
older revision) that crosses a revision that modified that file.

The easiest way to determine the affected files would be to diff the
outputs of «svn info -R ./» and «svn info -R $(svn info --show-item=url)»,
specifically, the "Last Changed Rev" entries in the output. This
assumes the working copy has been updated to HEAD; if that's not the
case, the second 'info' invocation should be passed the working copy's
BASE revision for a peg revision.

Yet another approach would be to run 'svn up -r N && svn up', where N =
HEAD - 1000 or so; note, this would only be 95% correct.


Received on 2017-10-31 01:58:52 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.