I had exactly the same problem today.
The message occurs when I press the OK button in the commit dialog box.
Most of my changes were restructuring of a moderately sized directory,
but some of those renames had been unsuccessful (e.g. due to misspelling
where the new name already existed).
I tried to use CleanUp several times, it didn't help.
My workaround was to use the command line interface to do the commit.
I had to go several rounds: It was complaining about files that were
to be moved, but didn't exist, so I had to create dummy files, and
files that were to be committed in their old pre-move location (and
successfully moved), so I copied the files back (copy, not move), to
make the commit succeed. Then, I had to remove the committed
dummy files had to created to complete the commit, and commit these.
After that, everything seems to be working fine, both using the GUI
and the CLI.
Ketil Albertsen,
Trondheim, Norway
> -----Original Message-----
> From: Andy Levy [mailto:andy.levy_at_gmail.com]
> Sent: 7. august 2013 20:02
> To: alexandre.vion_at_cp.com
> Cc: users_at_subversion.apache.org
> Subject: Re: Subversion Exception!
>
> On Wed, Aug 7, 2013 at 1:52 PM, <alexandre.vion_at_cp.com> wrote:
> > ---------------------------
> > Subversion Exception!
> > ---------------------------
> > Subversion encountered a serious problem.
> > Please take the time to report this on the Subversion mailing list
> > with as much information as possible about what you were trying to do.
> > But please first search the mailing list archives for the error
> > message to avoid reporting the same problem repeatedly.
> > You can find the mailing list archives at
> > http://subversion.apache.org/mailing-lists.html
> >
> > Subversion reported the following
> > (you can copy the content of this dialog to the clipboard using
> > Ctrl-C):
> >
> > In file
> >
> > 'D:\Development\SVN\Releases\TortoiseSVN-
> 1.8.1\ext\subversion\subversion\libsvn_client\commit_util.c'
> > line 211: assertion failed (repos_root_url && repos_relpath)
>
> Thank you for reading the message and doing *most* of what it asked you to
> do.
>
> But you need to describe *what* you were doing to cause this error to
> occur.
Received on 2013-08-08 17:25:26 CEST