The problems encountered here were due to an unusual once-off need to add
new APIs to an old branch in order to fix a security bug. This wasn't
handled perfectly by the Subversion project - with hindsight, we should have
ensured that the emergency-fixed 1.0 API was a subset of the 1.1 API, and we
should have made very explicit mention of the conflicts/requires packages
should use.
It's quite possible that a security bug requiring new APIs to fix will never
occur again, now that the Subversion API has had more time to mature.
If such a situation does arise again, we can learn from our fumble with
1.0.9.
Since the 1.0.x series of Subversion has passed away out of current
distributions, this bug can be closed - no action is required.
Max.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
