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

This commit is contained in:
Joey Hess 2018-10-25 13:16:28 -04:00
commit 0ae11e92c5
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
8 changed files with 87 additions and 0 deletions

View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="Ilya_Shlyakhter"
avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
subject="comment 2"
date="2018-10-24T16:01:53Z"
content="""
Maybe, post a new git-annex version on hackage, with the test failure fixed? I could then update the conda-forge recipe.
"""]]

View file

@ -0,0 +1,9 @@
[[!comment format=mdwn
username="marvin@3296bf3c446430c3b2ebc32b5c784ee976620847"
nickname="marvin"
avatar="http://cdn.libravatar.org/avatar/a07e2adf7ff40bdd4c3fe20ededc0a4e"
subject="comment 7"
date="2018-10-25T10:23:49Z"
content="""
i can reproduce this and struggle with it. i cant add any remote repo through the webapp.
"""]]

View file

@ -0,0 +1,6 @@
### Please describe the problem.
In recent nixpkgs the S3 special remotes have been disabled because some of the dependencies are quite old or unmaintained.
More detail here: <https://github.com/NixOS/nixpkgs/issues/45686>
### What steps will reproduce the problem?
Installing git-annex from the 18.09 nixpkgs release.

View file

@ -0,0 +1,31 @@
### Please describe the problem.
Tried to drop files that exist on s3:
git annex drop -J36 --in=ilya-s3
A few get dropped, and then it errors out with
git-annex: content is locked
(Apart from the issue here, maybe add an option to keep working in case of error with one file?)
### What version of git-annex are you using? On what operating system?
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
(master_env_py27_v28) [01:05 PM /data/ilya-work]$ uname -a
Linux ip-172-31-87-156 4.14.72-68.55.amzn1.x86_64 #1 SMP Fri Sep 28 21:14:54 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
### Please provide any additional information below.

View file

@ -0,0 +1,12 @@
### Please describe the problem.
git-annex-move does not seem to be using parallelism. i'm running
(master_env_py27_v28) [02:30 PM ~]$ ps -w -w -w -F 12231
UID PID PPID C SZ RSS PSR STIME TTY STAT TIME CMD
ilya 12231 12230 99 271873062 1018700 26 14:15 pts/2 Sl+ 506:13 /data/vngs/viral-ngs-etc/mc3/envs/master_env_py27_v28/bin/git-annex move -J48 --all --to ilya-s3
and there is only one thread with git-annex.
On what operating system?
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
(master_env_py27_v28) [01:05 PM /data/ilya-work]$ uname -a Linux ip-172-31-87-156 4.14.72-68.55.amzn1.x86_64 #1 SMP Fri Sep 28 21:14:54 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

View file

@ -0,0 +1,9 @@
hi.
first i have to say... im a huge fan and running some git-annex repos for all sort of things. i trust git-annex my whole photo archiv and my tax documents ;-)
i try to get my head around some scenarios i couldnt get working. i want a nextcloud/dropbox style sink between two boxes. i have set up my repo manually on my laptop some time ago. just like `git init && git annex init`. i cloned that on my server and ran `git annex init`; added the server repo as remote on my laptop. so `git annex sync --content` works on both ends. what i want is to run git annex assistant on both boxes... server and laptop. i add a new file on laptop and git annex assistant syncs it to my server. that works fine. but i thought that the git annex assistant notices it and does a git annex sync too, to pull changes in. i only get it working in one way. what am i doing wrong?
in the screencast for the assistant it looks like it should work that way... with the only difference that it got setup within the webapp itself and a bare transfer repository on a server. is this transfer group server needed for make it working this way?
i also found [this](https://git-annex.branchable.com/tips/making_a_remote_repo_update_when_changes_are_pushed_to_it/) in the tips. does i have to set up like that?

View file

@ -0,0 +1 @@
For which git-annex commands that take a file argument, is it safe for the file to be a named pipe (i.e. git-annex is guaranteed to only read/write the file once and without seeking)?

View file

@ -0,0 +1,11 @@
[[!comment format=mdwn
username="disteph@02005197c6b0e3d92255823d62c08dbe6d7a4d52"
nickname="disteph"
avatar="http://cdn.libravatar.org/avatar/a12e6e0852d5a1985b8684b17202561c"
subject="comment 5"
date="2018-10-24T11:42:15Z"
content="""
`findref` still displays file names, so OK, I can pipe the output with `lookupkey` to have the corresponding list of keys
Actually, that's not even true: `lookupkey` doesn't seem to work on a bare repo. So I don't see how I can get the list of keys that are going to be moved or copied when a `git annex move ...` or `git annex copy ...` is run from a bare repo.
"""]]