[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: 1.9.x release notes, SVN-4722

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Tue, 10 Dec 2019 03:21:59 +0000

Nathan Hartman wrote on Mon, Dec 09, 2019 at 10:42:39 -0500:
> +<div class="h3" id="svn-4722">
> +<h3>Commit can fail with an undeserved "Filesystem is corrupt" error
> + <a class="sectionlink" href="#svn-4722"
> + title="Link to this section">&para;</a>
> +</h3>
> +
> +<p>See issue 4722, "checksum fail during commit when delta is 16K".
> +</p>
> +
> +<p>When using a Subversion 1.9.7 server, a commit may fail with an
> +undeserved SHA1 collision error: "E160000: SHA1 of reps ... and ...
> +matches (...) but contents differ." For details, see
> +<a href="https://issues.apache.org/jira/browse/SVN-4722?issueNumber=4722"
> +>issue 4722, "checksum fail during commit when delta is 16K"</a>. This
> +bug affects the 1.9.7 release only. A fix for this problem has been
> +included in the 1.9.9 release (1.9.8 was not publicly released).
> +</p>
> +

Change «"Filesystem is corrupt"» in the section title to match the actual error
message?

> I know it's not terribly high priority to go back and fill in old
> release notes but it seems to me (based on discussions and questions
> we get) that many people are still using 1.9.7 on the server. Some are
> using older OS distros. Others are using Subversion packages that
> install onto a NAS. In any case, they have 1.9.7 because they haven't
> received updates. Maybe they don't see any issues in the release notes
> affecting versions later than 1.9.6 so they don't think it's important
> to update.

There were multiple security issues fixed in later 1.9 patch releases; see
https://subversion.apache.org/security/

> There are other bugs fixes in later 1.9.x as well. It's better to
> write it down than to keep it in my head.
Received on 2019-12-10 04:28:50 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.