found 339841 subversion/339841 tags 339841 + moreinfo quit Hi Karl,
A. Karl Kornel wrote: > Hello. I have some additional information to add to this bug. > > First, I tried to check out a new working copy into a different > directory > (the repository and working copy are still on the same system here). Making > the changes to the newly-checked-out copy can not be committed (the crash > still takes place, and a cleanup/recover still needs to be done). > > In addition to the local working copy, I also have access to two working > copies on remote systems. Both remote working copies use svn+ssh to connect > to the repository. One remote system has version 1.2.1 (r15230), and > another has version 1.1.4 (r13838). For each remote working copy, I updated > it to the latest revision (with no problems), made a change, and tried to > commit. Each one failed in the same place with the following: > >> svn: Commit failed (details follow): >> svn: Malformed network data > > Each one required a cleanup/recover. Sorry for the slooow response. Can you still reproduce this? If not, do you remember how it was resolved (i.e., was it fixed by an upgrade, did you abandon the repository and move on, or something else)? Curious, Jonathan -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
