Hello, thx for the quick answer!
> -----Ursprüngliche Nachricht-----
> Von: Stefan Sperling [mailto:stsp_at_elego.de]
> Gesendet: Dienstag, 18. Oktober 2011 11:20
> An: Brockamp, Peter
> Cc: users_at_subversion.apache.org
> Betreff: Re: Supposed serious(?) bug in either subversion or
> TortoiseSVN when upgrading to latest V1.7.0 version
>
> No need to panic.
Surely not! ;-)
> First, this has nothing to do with client<->server interactions.
> It is a pure client-side problem.
Dunno, I was just suppossing, as something comparable never happened
to anyone here in the past with every installed version of SVN/Tortoise we used!
> Second, there is no known case where a good 1.6 working copy
> failed to upgrade. Your errors are due to dormant problems in
> your 1.6 working copies, i.e. problems which you would have
> run into with 1.6 eventually.
Hm, maybe. But I was expecting that the recomended "Clean Up..." before
upgrading tackles exactly this. I *did* a clean up on the project and I did
get no errors about incomplete working nodes or what ever. So this lures
people into thinking they're safe to upgrade which runs them into this problem.
So with this in mind maybe the questions should be:
- Why doesn't "Clean Up..." complain about incomplete working nodes?
- Why isn't "Clean Up..." able to repair those damages?
- Why doesn't Upgrade fail when encountering those errors
and reverts back to the original state?
> The upgrade should fail in this case, but apparently it doesn't.
> So there is something we can fix here, but it's not very serious.
Yep!
> If you want to prevent your co-workers from running into
> this, just tell them to get fresh checkouts instead of upgrading.
> Especially if they have working copies which have been used
> for months or years.
I guess you get so many reports from users about this problem
Because there are so many WC out there who have been used for
Months or years.
OK, thx for your quick help!
Regards
Peter Brockamp
Received on 2011-10-18 12:07:15 CEST