Ah, I didn't see that in the issue tracker. Looks like the same
root-of-drive issue, but in my case there was no abort, use of a
network share, or partial commit. What are the odds of the 1.7.x fix
being backported to 1.6.x? We ran into this during a dry run of moving
our source control to Subversion from another SCM system, but given
the way our developers work on their code this is a nuisance. At least
there's a workaround (commit from the "real" path, not the subst-ed
drive letter).
If I've hosed my working copy by doing this, is there a graceful way
to clean it up? 'svn cleanup' quits with the same message; the only
way I've found to get it unstuck is to clear the "log" files from the
.svn folder in the root directory, svn up, and hope for the best.
-- Anthony
On Tue, Jul 14, 2009 at 10:13 AM, Bert Huijben<bert_at_qqmail.nl> wrote:
>
>
>> -----Original Message-----
>> From: Anthony Bellissimo [mailto:twon33_at_gmail.com]
>> Sent: maandag 13 juli 2009 22:09
>> To: users_at_subversion.tigris.org
>> Subject: RE: Re: svn 1.6.x regression: svn commit damages 'root of
>> drive working copies' under windows
>>
>> I get the same thing here, with version 1.6.3 (r38063) over https.
>>
>> K:\>notepad foo.txt
>>
>> K:\>svn add foo.txt
>> A foo.txt
>>
>> K:\>svn ci -m ""
>> Adding k://foo.txt
>> Transmitting file data .svn: Commit succeeded, but other errors follow:
>> svn: Error bumping revisions post-commit (details follow):
>> svn: In directory 'K:'
>> svn: Log entry missing 'name' attribute (entry 'rm' for directory 'K:')
>
> See also issue 3346:
> http://subversion.tigris.org/issues/show_bug.cgi?id=3346
>
> Bert
>
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2371240
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-14 16:38:37 CEST