aboutsummaryrefslogtreecommitdiff
path: root/UPDATING
diff options
context:
space:
mode:
authorGabor Pali <pgj@FreeBSD.org>2013-05-12 19:39:00 +0000
committerGabor Pali <pgj@FreeBSD.org>2013-05-12 19:39:00 +0000
commitb4c6a782d90e4f2222ceacb4a0a6541662922ee2 (patch)
tree589762c2ee9fb1684d4a549a315156d146cb4915 /UPDATING
parentefa1d78a4664ce543d01c99a3cea78bd2f792988 (diff)
downloadports-b4c6a782d90e4f2222ceacb4a0a6541662922ee2.tar.gz
ports-b4c6a782d90e4f2222ceacb4a0a6541662922ee2.zip
- Fix a silent hashing problem for git-annex, please study the UPDATING
entry before proceeding! Submitted by: Justin Bedő <cu@cua0.org> Obtained from: FreeBSD Haskell
Notes
Notes: svn path=/head/; revision=317974
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING19
1 files changed, 19 insertions, 0 deletions
diff --git a/UPDATING b/UPDATING
index 6ab82d871403..d849fe06cf29 100644
--- a/UPDATING
+++ b/UPDATING
@@ -5,6 +5,25 @@ they are unavoidable.
You should get into the habit of checking this file for changes each time
you update your ports collection, before attempting any port upgrades.
+20130512:
+ AFFECTS: users of devel/hs-git-annex
+ AUTHOR: haskell@FreeBSD.org
+
+ On FreeBSD, git-annex incorrectly calculated SHA256 hashes for files
+ added to the annex repository due to the BSD-style output of
+ /sbin/sha256. The result of this is silent data corruption.
+
+ This problem has been fixed, but every file stored in an annex
+ repository will fail a `git annex fsck` after the upgrade. Thus,
+ before updating, it is wise to issue the command below and restore the
+ files.
+
+ $ git annex uninit
+
+ Corruptions can then be found by finding all files with the same hash.
+ Note that only files that were mishashed to the same location are a
+ problem.
+
20130511:
AFFECTS: users of TeX
AUTHOR: hrs@FreeBSD.org