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

Re: keywords not updated after an update that doesn't change the file due to local changes

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: Tue, 23 Jun 2015 11:04:24 +0200

Here's the revision

On 23 June 2015 at 10:45, Julian Foad <julianfoad_at_btopenworld.com> wrote:
> Vincent Lefevre wrote:
>> I have the following problem under Debian with the subversion 1.8.13-1
>> Debian package, but I don't think that this is Debian specific.
>> It seems that "svn update" doesn't update keywords when the local
>> modifications on the concerned file are the same as in the repository.
> [...]
> Thank you, Vincent.

Please feel free to file an issue to track this if you wish.
(Generally I think it's a good idea to file issues for bugs that are
found in released versions.)

> I can reproduce this in trunk_at_head and have added a regression test in r1686988.

The commit:

The test:
  XFAIL: update_tests.py 81: update_keywords_on_shortcut

BTW, I imagine fixing it should not be very difficult, but I am not
currently working on it. Does anyone else want to take it?

- Julian

> I noticed that the keywords are correctly updated if I run "svn switch
> ^/FILE FILE" instead of "svn update FILE". I discussed with philipm
> and stsp.This is (we suppose) because a previous, similar bug in
> 'switch' was fixed by making switch run a full WC crawl (after the
> incoming changes have been processed) to update any keywords (URL
> keywords, especially) in files that were not touched by the incoming
> changes. That fix probably has the unintended side effect of masking
> this present bug. I haven't checked to see if that is definitely the
> reason why 'switch' works.
> - Julian
Received on 2015-06-23 12:50:03 CEST

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