You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Dawid Ireno <al...@gmail.com> on 2026/03/16 06:47:44 UTC

Tortoise SVN bugs

Good evening,

 

I came across one ugly bug in Tortoise SVN. In my scenario I have a big repo with binaries and I tried pulling it in serveral rounds part by part. So I downloaded some of binaries, aborted pulling rest of binaries. Than the other day I performed cleanup and continued pulling further binaries. This I have repeated few days in a row. But one day cleanup action exploaded and broke my local repo copy. Attaching screenshot.

 

Best regards,

Dawid



RE: Tortoise SVN bugs

Posted by Dawid Ireno <al...@gmail.com>.
Hi Daniel,

 

That is a no-manual-change-type-folder. Deleting it and re-pulling end with same result. I have to be again pulling it in several rounds part by part and on random day I end up with same error and broken repo.

 

Can we try to understand this error and propose a fix for upcoming Tortoise SVN builds?

 

Best regards,

Dawid

 

From: Daniel Sahlberg [mailto:daniel.l.sahlberg@gmail.com] 
Sent: Sunday, April 12, 2026 7:44 PM
To: Dawid Ireno <al...@gmail.com>
Cc: users@subversion.apache.org
Subject: Re: Tortoise SVN bugs

 

Hi,

 

I believe the best option is to delete your working copy and check out a new one. If you have changes, you can probably get away with deleting just the .svn directory and checking out into the existing directory - changes should be kept and you can continue to work. Of course, make sure to take backups first.

 

Kind regards,

Daniel

 

 

Den ons 8 apr. 2026 kl 15:37 skrev Dawid Ireno <alamandra007@gmail.com <ma...@gmail.com> >:

Hi Daniel,

 

It’s a local drive copy, not a network drive.

 

Synchronized folder is a sub-folder under “C:\My Projects\”.

 

Command line cleanup give me “svn: E155016: The working copy database at 'C:\My Projects\Libs' is corrupt.”

 

What should I do..?

 

Best regards,

Dawid

 

From: Daniel Sahlberg [mailto:daniel.l.sahlberg@gmail.com <ma...@gmail.com> ] 
Sent: Monday, April 6, 2026 5:53 PM
To: users@subversion.apache.org <ma...@subversion.apache.org> ; alamandra007@gmail.com <ma...@gmail.com> 
Subject: Re: Tortoise SVN bugs

 

Dear Dawid,

 

This is usually caused by TortoiseSVN sending an invalid path to the Subversion libraries. Some questions that may help you along

 

Do you have your working copy on a local disk or on a network drive?

Is it stored in the drive root or in another folder?

Can you run repair using the command line client? (You can select to install the command line tools when you install TortoiseSVN). The correct command would be svn cleanup C:\[path]\[to]\[working]\[copy]

 

If you can run the repair using the command line client, you should probably report your findings to the TortoiseSVN Google group: https://groups.google.com/g/tortoisesvn

 

Hope this helps!

Daniel Sahlberg

 

 

Den mån 16 mars 2026 kl 07:49 skrev Dawid Ireno <alamandra007@gmail.com <ma...@gmail.com> >:

Good evening,

 

I came across one ugly bug in Tortoise SVN. In my scenario I have a big repo with binaries and I tried pulling it in serveral rounds part by part. So I downloaded some of binaries, aborted pulling rest of binaries. Than the other day I performed cleanup and continued pulling further binaries. This I have repeated few days in a row. But one day cleanup action exploaded and broke my local repo copy. Attaching screenshot.

 

Best regards,

Dawid



Re: Tortoise SVN bugs

Posted by Daniel Sahlberg <da...@gmail.com>.
Hi,

I believe the best option is to delete your working copy and check out a
new one. If you have changes, you can probably get away with deleting just
the .svn directory and checking out into the existing directory - changes
should be kept and you can continue to work. Of course, make sure to take
backups first.

Kind regards,
Daniel


Den ons 8 apr. 2026 kl 15:37 skrev Dawid Ireno <al...@gmail.com>:

> Hi Daniel,
>
>
>
> It’s a local drive copy, not a network drive.
>
>
>
> Synchronized folder is a sub-folder under “C:\My Projects\”.
>
>
>
> Command line cleanup give me “svn: E155016: The working copy database at
> 'C:\My Projects\Libs' is corrupt.”
>
>
>
> What should I do..?
>
>
>
> Best regards,
>
> Dawid
>
>
>
> *From:* Daniel Sahlberg [mailto:daniel.l.sahlberg@gmail.com]
> *Sent:* Monday, April 6, 2026 5:53 PM
> *To:* users@subversion.apache.org; alamandra007@gmail.com
> *Subject:* Re: Tortoise SVN bugs
>
>
>
> Dear Dawid,
>
>
>
> This is usually caused by TortoiseSVN sending an invalid path to the
> Subversion libraries. Some questions that may help you along
>
>
>
> Do you have your working copy on a local disk or on a network drive?
>
> Is it stored in the drive root or in another folder?
>
> Can you run repair using the command line client? (You can select to
> install the command line tools when you install TortoiseSVN). The correct
> command would be svn cleanup C:\[path]\[to]\[working]\[copy]
>
>
>
> If you can run the repair using the command line client, you should
> probably report your findings to the TortoiseSVN Google group:
> https://groups.google.com/g/tortoisesvn
>
>
>
> Hope this helps!
>
> Daniel Sahlberg
>
>
>
>
>
> Den mån 16 mars 2026 kl 07:49 skrev Dawid Ireno <al...@gmail.com>:
>
> Good evening,
>
>
>
> I came across one ugly bug in Tortoise SVN. In my scenario I have a big
> repo with binaries and I tried pulling it in serveral rounds part by part.
> So I downloaded some of binaries, aborted pulling rest of binaries. Than
> the other day I performed cleanup and continued pulling further binaries.
> This I have repeated few days in a row. But one day cleanup action
> exploaded and broke my local repo copy. Attaching screenshot.
>
>
>
> Best regards,
>
> Dawid
>
>

RE: Tortoise SVN bugs

Posted by Dawid Ireno <al...@gmail.com>.
Hi Daniel,

 

It’s a local drive copy, not a network drive.

 

Synchronized folder is a sub-folder under “C:\My Projects\”.

 

Command line cleanup give me “svn: E155016: The working copy database at 'C:\My Projects\Libs' is corrupt.”

 

What should I do..?

 

Best regards,

Dawid

 

From: Daniel Sahlberg [mailto:daniel.l.sahlberg@gmail.com] 
Sent: Monday, April 6, 2026 5:53 PM
To: users@subversion.apache.org; alamandra007@gmail.com
Subject: Re: Tortoise SVN bugs

 

Dear Dawid,

 

This is usually caused by TortoiseSVN sending an invalid path to the Subversion libraries. Some questions that may help you along

 

Do you have your working copy on a local disk or on a network drive?

Is it stored in the drive root or in another folder?

Can you run repair using the command line client? (You can select to install the command line tools when you install TortoiseSVN). The correct command would be svn cleanup C:\[path]\[to]\[working]\[copy]

 

If you can run the repair using the command line client, you should probably report your findings to the TortoiseSVN Google group: https://groups.google.com/g/tortoisesvn

 

Hope this helps!

Daniel Sahlberg

 

 

Den mån 16 mars 2026 kl 07:49 skrev Dawid Ireno <alamandra007@gmail.com <ma...@gmail.com> >:

Good evening,

 

I came across one ugly bug in Tortoise SVN. In my scenario I have a big repo with binaries and I tried pulling it in serveral rounds part by part. So I downloaded some of binaries, aborted pulling rest of binaries. Than the other day I performed cleanup and continued pulling further binaries. This I have repeated few days in a row. But one day cleanup action exploaded and broke my local repo copy. Attaching screenshot.

 

Best regards,

Dawid



Re: Tortoise SVN bugs

Posted by Daniel Sahlberg <da...@gmail.com>.
Dear Dawid,

This is usually caused by TortoiseSVN sending an invalid path to the
Subversion libraries. Some questions that may help you along

Do you have your working copy on a local disk or on a network drive?
Is it stored in the drive root or in another folder?
Can you run repair using the command line client? (You can select to
install the command line tools when you install TortoiseSVN). The correct
command would be svn cleanup C:\[path]\[to]\[working]\[copy]

If you can run the repair using the command line client, you should
probably report your findings to the TortoiseSVN Google group:
https://groups.google.com/g/tortoisesvn

Hope this helps!
Daniel Sahlberg


Den mån 16 mars 2026 kl 07:49 skrev Dawid Ireno <al...@gmail.com>:

> Good evening,
>
>
>
> I came across one ugly bug in Tortoise SVN. In my scenario I have a big
> repo with binaries and I tried pulling it in serveral rounds part by part.
> So I downloaded some of binaries, aborted pulling rest of binaries. Than
> the other day I performed cleanup and continued pulling further binaries.
> This I have repeated few days in a row. But one day cleanup action
> exploaded and broke my local repo copy. Attaching screenshot.
>
>
>
> Best regards,
>
> Dawid
>