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

This commit is contained in:
Joey Hess 2020-11-18 12:53:41 -04:00
commit 9c448c877b
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
5 changed files with 125 additions and 0 deletions

View file

@ -0,0 +1,11 @@
[[!comment format=mdwn
username="kyle"
avatar="http://cdn.libravatar.org/avatar/7d6e85cde1422ad60607c87fa87c63f3"
subject="comment 4"
date="2020-11-18T15:30:06Z"
content="""
Thanks for the analysis. (I wish I had some sort of intelligent input
to give rather than just being the reporter of several of these ssh
issues :/)
"""]]

View file

@ -0,0 +1,39 @@
### Please describe the problem.
I get the following **warning** on my git-annex dashboard
```
Upgrader crashed: C:\Users\alexasus\.config\git-annex\program: openFile: does not exist (No such file or directory)
```
### What steps will reproduce the problem?
- Install git-annex with the Windows 10 installer.
- Create a repository with the default path.
### What version of git-annex are you using? On what operating system?
- git-annex version: git-annex-installer_8.20201007+git171-g7e24b2587 (this is the Windows 10 installer filename)
- Windows 10 Version 2004 (OS Build 19041.630)
### Please provide any additional information below.
[[!format sh """
# If you can, paste a complete transcript of the problem occurring here.
# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
[2020-11-18 11:29:22.6950775] main: starting assistant version 8.20201008-g7e24b2587
Launching web browser on file://C:\Users\alexasus\Desktop\annex\.git\annex\webapp.html
[2020-11-18 11:29:22.7940807] Cronner: You should enable consistency checking to protect your data.
(scanning...) [2020-11-18 11:29:23.278062] Watcher: Performing startup scan
(started...)
Upgrader crashed: C:\Users\alexasus\.config\git-annex\program: openFile: does not exist (No such file or directory)
[2020-11-18 11:29:24.1010593] Upgrader: warning Upgrader crashed: C:\Users\alexasus\.config\git-annex\program: openFile: does not exist (No such file or directory)
# End of transcript or log.
"""]]
### 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)
I've barely just installed. So I'm gonna get going these days. That warning doesn't seem to be an issue so far. I've looked it up but couldn't find any other reports for that warning.

View file

@ -0,0 +1,43 @@
### Please describe the problem.
addurl fails with the following message:
% git annex addurl --file=episodes/rtq-proteomics1.mp3 https://test.bioinformatics.chat/episodes/rtq-proteomics.mp3
addurl https://test.bioinformatics.chat/episodes/rtq-proteomics.mp3
download failed: Requested Range Not Satisfiable
download failed: Requested Range Not Satisfiable
failed
git-annex: addurl: 1 failed
I configured the server to log the Range header as the last field, and this is what I observe:
x.x.x.x - - [18/Nov/2020:13:32:19 +0000] "GET /episodes/rtq-proteomics.mp3 HTTP/1.1" 416 197 "-" "-" "bytes=30343208-"
So the start of the range is exactly the file size, and the 416 response is warranted. It looks like git annex does not handle this edge case.
### What steps will reproduce the problem?
I'm not sure tbh — I think this happened because I interrupted a previous download of this file.
### What version of git-annex are you using? On what operating system?
Stock git-annex on Fedora 32:
git-annex version: 8.20200330
build flags: Assistant Webapp Pairing S3 WebDAV Inotify DBus DesktopNotify TorrentParser MagicMime Feeds Testsuite
dependency versions: aws-0.21.1 bloomfilter-2.0.1.0 cryptonite-0.25 DAV-1.3.4 feed-1.1.0.0 ghc-8.6.5 http-client-0.6.4 persistent-sqlite-2.9.3 torrent-10000.1.1 uuid-1.3.13 yesod-1.6.0.1
key/value backends: SHA256E SHA256 SHA512E SHA512 SHA224E SHA224 SHA384E SHA384 SHA3_256E SHA3_256 SHA3_512E SHA3_512 SHA3_224E SHA3_224 SHA3_384E SHA3_384 SKEIN256E SKEIN256 SKEIN512E SKEIN512 BLAKE2B256E BLAKE2B256 BLAKE2B512E BLAKE2B512 BLAKE2B160E BLAKE2B160 BLAKE2B224E BLAKE2B224 BLAKE2B384E BLAKE2B384 BLAKE2BP512E BLAKE2BP512 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 git-lfs hook external
operating system: linux x86_64
supported repository versions: 8
upgrade supported from repository versions: 0 1 2 3 4 5 6 7
local repository version: 8
### 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)
Yes! git-annex has been working great for me so far, and is powering the bioinformatics chat podcast (https://bioinformatics.chat/). Thanks!

View file

@ -0,0 +1,14 @@
[[!comment format=mdwn
username="gueux"
avatar="http://cdn.libravatar.org/avatar/47e44a21505727b2d6bb5d88f0468f34"
subject="comment 1"
date="2020-11-18T10:54:56Z"
content="""
Thanks for the fix! I've manually updated the permissions of the hooks to 755 but unfortunately they are still not executed in a repo mounted via sshfs. There seems to be a kind of protection feature (which I can understand, as we're not sure of what's inside a remote executable).
$ ls -l .git/hooks/post-checkout
.rwxr-xr-x 76 gueux 27 Feb 20:33 .git/hooks/post-checkout
$ .git/hooks/post-checkout
bash: .git/hooks/post-checkout: Permission denied
"""]]

View file

@ -0,0 +1,18 @@
Hello everyone,
I would like to make a repository readable and writable over ssh for all users of a given group.
A [quick search](https://stackoverflow.com/a/29646155) led me to the following procedure :
```bash
cd <project_dir>/ # Enter inside the project directory
git config core.sharedRepository group # Update the git's config
chgrp -R <group-name> . # Change files and directories' group
chmod -R g+w . # Change permissions
chmod g-w .git/objects/pack/* # Git pack files should be immutable
find -type d -exec chmod g+s {} + # New files get directory's group id
```
My question is simple : is it safe to apply it to a git-annex repository as well ?
Thank you for your help.