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

2015-07-19 Thread Julian Foad
Vincent Lefevre wrote: > On 2015-06-23 11:04:24 +0200, Julian Foad wrote: > > On 23 June 2015 at 10:45, Julian Foad > 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 spec

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

2015-07-19 Thread Vincent Lefevre
On 2015-06-23 11:04:24 +0200, Julian Foad wrote: > On 23 June 2015 at 10:45, Julian Foad 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 u

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

2015-06-23 Thread Julian Foad
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 reposi

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

2015-06-23 Thread Julian Foad
Here's the revision On 23 June 2015 at 10:45, Julian Foad 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

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

2015-06-17 Thread Vincent Lefevre
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. The problem occurs on som