Bug? "svn up" gets confused if repo has a property change, and the file was rm'd from the wc.

I just came across the following unfortunate problem:

A recent commit have changed the properties (svn:mime-type was removed)
on a file "foo". Meanwhile a wc that has not yet updated to that
revision had the file "foo" removed (with "svn rm --force"). Now I see
the following when doing "svn up" in that wc:

svn: In directory 'xyz'
svn: Error processing command 'set-timestamp' in 'xyz'
svn: Can't set access time of 'xyz/foo': No such file or directory

Right after this message, svn exits (with code 1), aborting the update
in the middle.

Is this a known bug? Should I file an issue?

P.S. I tried versions 1.2.3 (r15833) and 1.1.0 (r11180)

-- 
Aleksey Nogin
Home Page: http://nogin.org/
E-Mail: nogin@cs.caltech.edu (office), aleksey@nogin.org (personal)
Office: Moore 04, tel: (626) 395-2200
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org