Andreas Schultz <firstname.lastname@example.org> writes:
> After upgrading a svn server from 1.1.4 to 1.2, doing a svnversion in
> a working copy that has svn:externals, reports as mixed version based
> on the versions of the working copy and the external, e.g. 352:422M.
> This very same problem that had been discussed and solved almost two
> years ago here:
> Any ideas how to get the old behavior back?
In other words, you want the pre-0.27 behavior? It looks like the
sequence has been:
* Up to and including 0.27, svnversion ignored svn:externals.
* From 0.28, until sometime before 0.32.1, it payed attention to
* Sometime between 0.32.1 and 1.1.4, it started ignoring
* Sometime between 1.1.4 and 1.2.0, it started paying attention to
That's pretty amazing :-).
The "M" on the end of your example, "352:422M", is extraneous, by the
way, right? The real issue here is the presence of the ":422", and
whether the external happens to be locally modified ("M") or not is
Current head of trunk (r15159) still has the buggy behavior:
$ svn up
Fetching external item into 'svntest'
External at revision 15159.
At revision 1428.
$ svn st -q
Performing status on external item at 'svntest'
I agree that this is a bug, or at least a suboptimal behavior. An
acceptable solution would be to just ignore svn:externals entirely.
An even better solution might be to print "E" at the end to indicate
that externals are present in the working copy, thus:
Would you mind opening an issue for this bug, and pointing to this
mail thread from the issue? If you don't have time, that's fine, just
let me know either way. (And of course, if you have time to make a
patch to fix the bug, that's always great!)
Thanks for the report,
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Jun 24 19:14:22 2005