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

Re: forcing update of keyword expansions in a working copy

From: Nathan Hartman <hartman.nathan_at_gmail.com>
Date: Wed, 30 Sep 2020 22:27:47 -0400

On Wed, Sep 30, 2020 at 6:50 PM Vincent Lefevre <vincent-svn_at_vinc17.net> wrote:
> Is there a way to force the update of keyword expansions to their
> correct values in a working copy?
> "svn up" will not change anything if the file hasn't changed, but
> the file may have obsolete keyword values, probably due to some bug
> in Subversion. I noticed the issue while checking data integrity by
> comparing an up-to-date working copy with the result of "svn export"
> (some keyword expansions were different, and it appears that the
> expansions of the Id keyword were not updated after a commit that
> only changed the svn:keywords property from "Id Date" to "Id").

Hi Vincent,

Searching through the issues database, I came across issue #4585 [1]
which you filed previously and this sounds related to the same issue.

Are you still using svn 1.8.x? If not, which version are you using now?

A few svn:keywords bugs were fixed in 1.9.x, including issue #1975
[2], where svn:keywords were not being re-expanded after 'svn switch';
perhaps that fix is common to this case as well. Note that 1.9.x went
end-of-life earlier this year, so if you could try with 1.10.x or
1.14.x, that would be preferred. (And 1.8.x went end-of-life more than
2 years ago.)

If the file timestamp changes, but not the file contents ('touch' the
file and then run 'svn update'), does keyword re-expansion occur?

If the file contents change (e.g., add 1 character to the file
contents then run 'svn update') does the expected keyword expansion
take place?


[1] https://issues.apache.org/jira/browse/SVN-4585

[2] https://issues.apache.org/jira/browse/SVN-1975
Received on 2020-10-01 04:28:04 CEST

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