Re: Problem on Commit: "Commit succeeded, but other errors follow:"

Thank you for your quick response. I realized last night after I sent out
my email that I should have used the term "working copy" instead of
"repository". We've gotten into the (bad) habit of using the terms "repo"
and "repository" where we should be correctly saying "working copy".

As you suggested, I will ask my question over on the Subversion user list.

--- Steve

                                                                                                                                                 
  From: "Simon Large" <simon.tortoisesvn_at_googlemail.com>
                                                                                                                                                 
  To: users_at_tortoisesvn.tigris.org
                                                                                                                                                 
  Date: 07/18/2008 03:27 AM
                                                                                                                                                 
  Subject: Re: Problem on Commit: "Commit succeeded, but other errors follow:"
                                                                                                                                                 

2008/7/18 Steven Rosenstein <srosenst_at_us.ibm.com>:
> Gentlefolks,
>
> TortoiseSVN 1.5.0, Build 13316 - 32 Bit , 2008/06/21 07:55:29
> Subversion 1.5.0,
> apr 1.2.12
> apr-utils 1.2.12
> berkeley db 4.4.20
> neon 0.28.2
> OpenSSL 0.9.8g 19 Oct 2007
> zlib 1.2.3
>
> I recently upgraded to V1.5.0. Today I began the next phase of a
> development project, and added a new code module to an existing
repository
> using Tortoise Add. I then did a Tortoise Commit. I received the
> following error messages (note that the filespec "R:\repo\foo.php" was
used
> to reduce my typing a very long text string):
>
> Adding R:\repo\foo.php
> Sending Content R:\repo\foo.php
> Error Commit succeeded, but other errors follow:
> Error Error bumping revisions post-commit (details follow):
> Error In directory 'R:\repo'
> Error Error processing command 'committed' in 'R:\repo'
> Error Can't Move
> Error 'R:\repo\...\foo.php.svn-work'
> Error to
> Error 'R:\repo\.svn\prop-base\foo...\
> Error Access is denied.
> Finished!
>
> The "R:\" share is located on a Samba-served Linux server. There is no
> copy of Subversion installed on the Linux server. I don't think I have a
> permissions issue because Tortoise runs in the context of "root" on the
> Samba share. I have been using Tortoise with this setup for over 2 years
> without any problems. It is only after I upgraded to V1.5.0 that I
started
> receiving the error messages on Commit. FWIW, this problem seems to
happen
> only with files which have been Added to the repo. Commits of files
which
> were already in the repo before the Tortoise upgrade complete
successfully.
> When the error occurs it renders the repo useless. Cleanup does not
work,
> and I cannot Update or Commit because it says the repo is locked. My
only
> alternative is to check out another copy of the repo, which is very time
> consuming.
>
> I did research in the list archives and in the bugtracker. I saw some
> messages with a problem similar to mine, the most recent being this one:
> http://tortoisesvn.tigris.org/servlets/ReadMsg?listName=users&msgNo=10807
.
> No solution was given.
>
> There was also a bug ticket opened on May 14, 2008:
> http://subversion.tigris.org/issues/show_bug.cgi?id=3198 The ticket is
> marked as "Fixed" but I cannot tell if the fix became a part of the
> Tortoise build I am using.
>
> I have 2 questions:
>
> (1) Does anyone have a way of manually fixing this problem? I need to
do
> a bit of secondary re-configuration every time I check out a new copy of
> the repo, and it quickly becomes very frustrating.
>
> (2) If no manual fix is available, can I downgrade to an earlier version
of
> Tortoise without problems? I have the Windows installer for 1.4.8 and
will
> happily revert if someone can assure me that it will work on repos that
> have been touched by Tortoise 1.5.0. Will a removal of 1.5.0 leave any
> artifacts on disk or in the Windows registry that could corrupt
> re-installing 1.4.8?
>
> I really love the convenience and power of Tortoise, and would hate to
lose
> it to this sort of problem.
>
> Thank you in advance for any help you can provide,

You may get more joy asking on (users at subversion tigris org).

Do yourself a favour - don't use file:// access on a network share.
It's really not hard to install svnserve.

Simon

--
: ___
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org