mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Merge branch 'master' of ssh://git-annex.branchable.com

Browse source
This commit is contained in:
Joey Hess 2021-03-24 12:12:08 -04:00
commit 97021435de
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
7 changed files with 74 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

15
doc/bugs/borg_not_recognizing_WORM.mdwn Normal file
View file

@ -0,0 +1,15 @@
### Please describe the problem.
borg special remote is apparently ignoring WORM and URL key content (probably all content without hashes?)
### What steps will reproduce the problem?
archive a repo containing WORM or URL keys with borg and sync it with git annex like in the example https://git-annex.branchable.com/special_remotes/borg/
doing `git annex list --not -i borg` later shows all WORM and URL keys not recognized being in borg
### What version of git-annex are you using? On what operating system?
git-annex version: 8.20210310
on NixOS 20.09
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
Thank you for including borg, and for fixing gcrypt remotes! This is great!

24
doc/bugs/borg_not_recognizing_WORM/comment_1_06f4bb172180825501ffaec60c89c66b._comment Normal file
View file

@ -0,0 +1,24 @@
[[!comment format=mdwn
username="git-annex@6f13b739194f758abc0b86556b7ce966c1bf3c00"
nickname="git-annex"
avatar="http://cdn.libravatar.org/avatar/198790d74209efe4896fd4cfc37ec2a6"
subject="/ vs. % in key"
date="2021-03-24T10:07:26Z"
content="""
the substitution of path elements (\"/\" in key to \"%\" in file) seems to be related:
$ git annex whereis --key WORM-s781040400-m1574160315--cd%therootsofsepultura.cdr
whereis WORM-s781040400-m1574160315--cd%therootsofsepultura.cdr (0 copies)
The following untrusted locations may also have copies:
91fd7b0a-493b-408c-aa07-c8520210f6a6 -- [borg]
failed
git-annex: whereis: 1 failed
$ git annex whereis --key WORM-s781040400-m1574160315--cd/therootsofsepultura.cdr
whereis WORM-s781040400-m1574160315--cd/therootsofsepultura.cdr (1 copy)
3340887b-e3b3-4a88-9de4-a8b60116cc66 -- [here]
ok
The first one should be within the second one.
"""]]

12
doc/bugs/borg_not_recognizing_WORM/comment_2_47085370d1d8223be4bacb271db63b09._comment Normal file
View file

@ -0,0 +1,12 @@
[[!comment format=mdwn
username="git-annex@6f13b739194f758abc0b86556b7ce966c1bf3c00"
nickname="git-annex"
avatar="http://cdn.libravatar.org/avatar/198790d74209efe4896fd4cfc37ec2a6"
subject="borg hardlinks"
date="2021-03-24T10:29:12Z"
content="""
Also not recognized by git-annex are hardlinks in borg, which show up in `borg list` like
hr--r--r-- woffs 1000 0 Sun, 2014-08-03 23:04:27 annex-objects/jP/40/SHA256E-s698785--bbe23f87e576cd7ab3a87c0ef8d82c99044515c63a83977d1ac870d82b88f8b4.jpg/SHA256E-s698785--bbe23f87e576cd7ab3a87c0ef8d82c99044515c63a83977d1ac870d82b88f8b4.jpg link to otherdir/sdcard/dcim/Camera/2014-07-28_13-07-42_306.jpg
"""]]

1
doc/forum/git-annex-sync_and_git-annex-config.mdwn Normal file
View file

@ -0,0 +1 @@
How does [[git-annex-sync]] interact with [[git-annex-config]] settings? Does the latest-in-time setting silently take over?

8
doc/tips/setup_a_public_repository_on_a_web_site/comment_12_eb732e9c1c44942bc313aa1ab3ff56fc._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="tomdhunt"
avatar="http://cdn.libravatar.org/avatar/02694633d0fb05bb89f025cf779218a3"
subject="comment 12"
date="2021-03-23T22:59:04Z"
content="""
Okay, setting allowed-ip-addresses worked fine. Thanks much.
"""]]

10
doc/todo/Avoid_lengthy___34__Scanning_for_unlocked_files_...__34__/comment_10_41cf16d6d14d1551c43736f854da3d05._comment Normal file
View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="Ilya_Shlyakhter"
avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
subject="annex.supportunlocked=false"
date="2021-03-23T20:02:16Z"
content="""
\"annex.supportunlocked=false does prevent installing smudge/clean filters\" -- then, do I understand correctly that, if it were a `git-annex-config` setting and `annex.supportunlocked=false` implied `annex.gitaddtoannex=false`, this would prevent inadvertently adding unlocked files? Then, assuming \"typical\" repo usage, it would also prevent inadvertently merging unlocked files, since you'd
have to add them first.
"""]]

4
doc/todo/additional_git-annex-config_settings__63__.mdwn Normal file
View file

@ -0,0 +1,4 @@
Should `annex.gitaddtoannex` and `annex.addsmallfiles` be [[`git-annex-config`|git-annex-config]] settings, given that `annex.largefiles`, `annex.dotfiles` and `annex.addunlocked` already are?
Also, [maybe](https://git-annex.branchable.com/todo/Avoid_lengthy___34__Scanning_for_unlocked_files_...__34__/#comment-85cb4d3eac345df7b08a31ea4bd810f6) make `annex.supportunlocked` a `git-annex-config` setting as well.