Follow-up Comment #4, sr #107077 (project administration):
Does this rule out the possibility of corruption? We consider it quite
likely that bzr+ssh:// is the cause. Colin?
I'd like to recommend that bzr+ssh:// is entirely disabled untill it is clear
that it doesn't corrupt data. We had repository corruption twice and had to
reconstruct the whole repository from scratch both times. It's a terrible
waste of time, sometimes loss of data. Taking this into account, I think the
proposed measure would be reasonable.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/support/?107077>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
