On Sun, Jun 26, 2016 at 10:28 PM, Stefan <luke1410_at_posteo.de> wrote:
> On 6/26/2016 05:48, Nico Kadel-Garcia wrote:
>> On Sat, Jun 25, 2016 at 8:24 PM, Johan Corveleyn <jcorvel_at_gmail.com> wrote:
>>>> Last: one of the most pernicious sources of bugs in Subversion's
>>>> history, one that I've encountered personally, has been the upgrade
>>>> process between releases of Subversion for the repository itself If
>>>> you don't need to have the dataqbase and fileysstem baggage of a full
>>>> history, then the bugs of upgrading become much more avoidable.
>>> Can you be more specific? What bug has broken your repository during
>>> upgrade? Were you careful enough yourself, as an administrator, while
>>> performing such a critical operation to the "crown jewels" of some
>>> developer team?
>> This one.
>>
>> http://stackoverflow.com/questions/10279222/how-can-i-fix-the-svn-import-line-endings-error
> I remember the old discussions relating to this issue only very faintly,
> but the same thread suggests the issue was "resolved" in SVN 1.7 and if
> I'm not mistaken this was done by adding the --bypass-prop-validation
> command line option to svnadmin load.
Agreed, that was an annoying problem (caused by adding the "no longer
accepts CR's in svn:* property values", without offering a way to
repair it or ignore it while loading a dumpfile).
It's not a data corruption bug though, which was what it sounded like
to me. It sounded like Nico ran into an upgrade bug that caused
irreparable corruption to the upgraded repository. The worst that can
happen is that you cannot dump+load your old repository into the new
format.
Anyway, point taken, that bug was / is an annoying problem.
--
Johan
Received on 2016-06-26 23:34:13 CEST