On 11.12.2013 21:02, Eric Todd wrote:
> The full error, that I was experiencing, was: "Delta source ended
> In order to address this, I ended up deleting all of the files with
> the white space in them. I then created new files, with a new naming
> convention, and committed successfully.
> At the time, I was desperate to get a resolution (demo). Is there
> any idea as to what could have happened.
> I am currently using the following TSVN version: TortoiseSVN 1.8.4,
> Build 24972 - 64 Bit , 2013/11/24 11:15:39 Subversion 1.8.5,
> -release apr 1.4.8 apr-util 1.5.2 serf 1.3.2 OpenSSL 1.0.1e 11 Feb
> 2013 zlib 1.2.8
> I am still waiting on the server log.
"Delta source ended unexpectedly" means (most likely) that your working
copy was slightly corrupted even before the relocate to the new url.
It's just that the corruption never surfaced before.
You can find a lot of references searching the web for "Delta source
ended unexpectedly", most of them indicating a corrupt working copy.
However it's also possible that the repository itself has a slight
corruption (or better: had) and the update to https fixed that, but the
fix prevented the files that were corrupted before from getting
committed (I assume the upgrade to https included a dump/load of the
repo data as well? If not, run 'svnadmin verify path/to/repo' on the
server to make sure your repositories are ok).
Anyway: if you encounter this problem again, you should report this on
the subversion users list since this error and problem originates in the
svn library, not TSVN directly.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest interface to (Sub)version control
/_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-12-11 21:10:29 CET