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 2018-10-10 12:59:01 -04:00
commit fd8094cbbc
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
5 changed files with 71 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
doc/bugs/cannot_talk_with_nextcloud_server/comment_2_6be3c252fac86e58affd2910ec0f3c22._comment Normal file
View file

@ -0,0 +1,16 @@
[[!comment format=mdwn
username="anarcat"
avatar="http://cdn.libravatar.org/avatar/4ad594c1e13211c1ad9edb81ce5110b7"
subject="comment 2"
date="2018-10-09T21:49:02Z"
content="""
> So are you saying this webdav server responds with an error when a directory creation is attempted,
well, not quite. the *webserver* responds with that error because git-annex tries to create https://example.net/ - it does not hit the nextcloud webdav endpoint, which is at https://example.net/nextcloud/remote.php/webdav
> but auto-creates directories as needed for puts?
>
> Is that allowed by the webdav spec?
I don't think it autocreates directories at all. The problem is `getProps /` fails because there's no webdav server at the root of the FWDN - it's in a sub-sub-directory instead....
"""]]

10
doc/forum/Copy_modified_content_to_a_repo_that_only_wants_content_already_present/comment_1_fb09f84abeebc55df9741b059dc50674._comment Normal file
View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="andrew"
avatar="http://cdn.libravatar.org/avatar/acc0ece1eedf07dd9631e7d7d343c435"
subject="comment 1"
date="2018-10-10T11:28:39Z"
content="""
The [preferred-content](https://git-annex.branchable.com/git-annex-preferred-content/) expression `present` operates on the content of a file, not on the file name. So when you modify `test.txt` on laptop, then `test.txt` now links to the new content (say content2). When you sync, desktop sees that `test.txt` now links to content2, content2 is not present on desktop so on your desktop `test.txt` now links to content that isn't there, IE `test.txt` shows as not present on your desktop. But your old content, say content1 is still present on your laptop and desktop if you were to checkout previous versions of git. Nothing was actually dropped anywhere (I don't think) but the new content (content2) was just not wanted on your desktop since it was never present there.
I don't think what you are trying to achieve is currently possible with git-annex in the general case. But, for 2 repos you could just do: `git annex wanted . \"copies=2\"`. This will mean that anytime you create a new version of a file (new content) on one machine that content will be wanted on the other machine as well to increase the copy count to 2.
"""]]

14
doc/forum/Unlocking_files_gives_symlink_content.mdwn Normal file
View file

@ -0,0 +1,14 @@
I am just beginning to use git-annex so it is possible that the following issue was caused by my own mishap. It cropped after commiting a number of file renames.
When files are locked, I am able to view their contents. However, when I unlock certain files, their contents appear to be replaced by the contents of the symlink. Locking them again allows me to view their contents. For instance, with one unlocked file, say `test.md`, I get
$ cat test.md
/annex/objects/SHA256E-s535--d37feb3390801b601a9cee77f6467f01aaabbb293149d20d75df26172a3594fd.md
Some files still behave as expected.
My git-annex repo is in my Linux home folder on an ext4 partition. My repo uses git-annex version 6.
I did have a look at [this discussion](https://git-annex.branchable.com/forum/git_annex_file_content_replaced_with_symlink_content/) but none of the solutions there seemed to do the trick.
Any help is much appreciated.

8
doc/todo/Natively_support_s3__58____47____47___urls___40__for_addurl__44___get__44___etc__41__/comment_11_2afa6133bfa8932ea1fb02b2052e2939._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="yarikoptic"
avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4"
subject="comment 11"
date="2018-10-10T14:05:53Z"
content="""
Ilya -- what version of annex you are using? Upgrade might help since there were some fixes related to the priorities in the past month or two (initially detected when using -J setting)
"""]]

23
doc/todo/Natively_support_s3__58____47____47___urls___40__for_addurl__44___get__44___etc__41__/comment_12_6c9336be070b04d5736b943889370c13._comment Normal file
View file

@ -0,0 +1,23 @@
[[!comment format=mdwn
username="Ilya_Shlyakhter"
avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
subject="comment 12"
date="2018-10-10T16:04:38Z"
content="""
(master_env_py27_v28) [11:52 AM /data/ilya-work]$ git annex version
git-annex version: 6.20180926-gc906aaf
build flags: Assistant Webapp Pairing S3(multipartupload)(storageclasses) WebDAV Inotify ConcurrentOutput TorrentParser MagicMime Feed\
s Testsuite
dependency versions: aws-0.17.1 bloomfilter-2.0.1.0 cryptonite-0.23 DAV-1.3.1 feed-0.3.12.0 ghc-8.0.2 http-client-0.5.7.0 persistent-s\
qlite-2.6.2 torrent-10000.1.1 uuid-1.3.13 yesod-1.4.5
key/value backends: SHA256E SHA256 SHA512E SHA512 SHA224E SHA224 SHA384E SHA384 SHA3_256E SHA3_256 SHA3_512E SHA3_512 SHA3_224E SHA3_2\
24 SHA3_384E SHA3_384 SKEIN256E SKEIN256 SKEIN512E SKEIN512 BLAKE2B256E BLAKE2B256 BLAKE2B512E BLAKE2B512 BLAKE2B160E BLAKE2B160 BLAKE\
2B224E BLAKE2B224 BLAKE2B384E BLAKE2B384 BLAKE2S256E BLAKE2S256 BLAKE2S160E BLAKE2S160 BLAKE2S224E BLAKE2S224 BLAKE2SP256E BLAKE2SP256\
BLAKE2SP224E BLAKE2SP224 SHA1E SHA1 MD5E MD5 WORM URL
remote types: git gcrypt p2p S3 bup directory rsync web bittorrent webdav adb tahoe glacier ddar hook external
operating system: linux x86_64
supported repository versions: 3 5 6
upgrade supported from repository versions: 0 1 2 3 4 5
local repository version: 5
"""]]