Warn about unsupported core.sharedRepository=0xxx when set

This spams the user with a lot of messages, but it seems like busywork to
avoid that and only warn once, since this warning will go away when it gets
implemented.

Also fix parsing of the octal value.

Sponsored-by: Kevin Mueller on Patreon
This commit is contained in:
Joey Hess 2023-04-26 13:25:29 -04:00
parent 4881bc5a53
commit 7af75a59be
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
4 changed files with 57 additions and 18 deletions

View file

@ -0,0 +1,14 @@
[[!comment format=mdwn
username="joey"
subject="""comment 2"""
date="2023-04-26T16:50:23Z"
content="""
I don't think it would be that hard to implement, I count 6 places, all in
Annex.Perms that don't handle UmaskShared.
For now I've made all of them display a warning.
(Note that your warning patch to datalad is probably buggy,
since core.sharedrepository=1 and =2 are supported by git-annex.
(As legacy alternatives to "group" and "everybody".))
"""]]