summaryrefslogtreecommitdiff
path: root/debian/changelog
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2016-04-14 15:36:53 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2016-04-14 15:36:53 -0400
commitca1518ed7f714a725fe9811716a320f1dc0b2f22 (patch)
tree769700bb4b221f1d5275f8d82623c84fd6accd66 /debian/changelog
parent2a74e12d24a91db4e23d274a6ce8c14a3490a8fa (diff)
fsck: Warn when core.sharedRepository is set and an annex object file's write bit is not set and cannot be set due to the file being owned by a different user.
Made all Annex.Perms file mode changing functions ignore errors when core.sharedRepository is set, because the file might be owned by someone else. I don't fancy getting bug reports about crashes due to set modes in this configuration, which is a very foot-shooty configuration in the first place. The fsck warning is necessary because old repos kept files mode 444, which doesn't allow locking them, and so if the mode remains 444 due to the file being owned by someone else, the user should be told about it.
Diffstat (limited to 'debian/changelog')
-rw-r--r--debian/changelog3
1 files changed, 3 insertions, 0 deletions
diff --git a/debian/changelog b/debian/changelog
index e899ab691..588c34542 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -14,6 +14,9 @@ git-annex (6.20160413) UNRELEASED; urgency=medium
as annexed. If you have such files, run git annex init --version=6
to update the cache after upgrading to this version of git-annex.
* Preserve execute bits of unlocked files in v6 mode.
+ * fsck: Warn when core.sharedRepository is set and an annex object file's
+ write bit is not set and cannot be set due to the file being owned
+ by a different user.
-- Joey Hess <id@joeyh.name> Wed, 13 Apr 2016 13:30:32 -0400