Re: Possible bug with computation of last revision and svn cp

Manuel Pégourié-Gonnard <mpg_at_elzevir.fr> writes:

> svnadmin create repo
> svn co file://$PWD/repo active
> svn co file://$PWD/repo passive
> cd active
> svn mkdir dir
> touch dir/file
> svn add dir/file
> svn ci -minitial
> svn cp dir newdir
> svn ci -m'after cp'
> cd ..
> cp -a active active-back-then-up
> (cd passive && svn up)
> (cd active && svn up)
> (cd active-back-then-up && svn up -r1 && svn up)
> svn status -v */newdir/file
>
> The output of the final svn status -v looks as follows:
>
> 2 1 mpg active-back-then-up/newdir/file
> 2 2 mpg active/newdir/file
> 2 1 mpg passive/newdir/file
>
> As you can see, only the "active" repo thinks newdir/file's last
> modification is at revision 2, other repositories compute it as 1.
>
> Thanks in advance for your comments,

Yes, that look like a bug. In 1.7 STMT_APPLY_CHANGES_TO_BASE
explicitly sets both revnum and changed_rev to the newly committed
revision.

There is a similar problem with changed_author and changed_date.

-- 
Philip