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 2022-07-28 12:01:33 -04:00
commit 868db3fdc6
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
4 changed files with 79 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

34
doc/bugs/Android_unable_to_use_external_special_remote.mdwn Normal file
View file

@ -0,0 +1,34 @@
### Please describe the problem.
I'm trying to set up the rclone special remote from [here](https://github.com/Craeckie/git-annex-remote-rclone) (a fork of the recommended that works with newer versions of rclone), for syncing across my laptop and tablet. So far, I've managed to sync everything from my laptop to the remote perfectly well, and I'm now trying to get it to work in Termux.
Having added `git-annex-remote-rclone` to my `$PATH` in Termux, and having installed git-annex itself (which seems to work fine), I tried running `git annex initremote mega type=external externaltype=rclone target=mega-encrypted prefix=git-annex chunk=1MiB encryption=none rclone_layout=lower`, and was greeted (among several linker errors, which are said to be harmless) with the following:
```
Cannot run /data/data/com.termux/files/home/.git-annex/git-annex.linux/bin/git-annex-remote-rclone -- Make sure it's executable and that its dependencies are installed.
```
This is after trying to put the `git-annex-remote-rclone` shell script into a git annex internal binaries folder, though it works nowhere else in my $PATH either. I suspect this is an issue with `proot` not copying in my `$PATH` correctly, though I'm not sure how I would fix this, seeing as I can't find any documentation on how to moify the PRoot flags `git-annex` uses.
### What steps will reproduce the problem?
1. Download `git-annex` into Termux on Android as documented [here](https://git-annex.branchable.com/Android).
2. Download the `git-annex-remote-rclone` folder from [here]() and place it anywhere in your `$PATH`.
3. Run `git init && git annex init` in some directory.
4. Run `git annex initremote test type=external externaltype=rclone target=thisdoesnotexist prefix=git-annex chunk=1MiB encryption=none rclone_layout=lower`. This should print an rclone-related error, but it prints a `git-annex` error as above.
### What version of git-annex are you using? On what operating system?
10.20220121-g0bcb94487 on Android 12 on a Samsung Galaxy Tab S6.
### 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/anne
# 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'm very new to the program, but so far I've found it excellently effective on my laptop! Thanks for a great tool!

2
doc/contribute/comment_3_e7219514f52207fcfb97aeec03241e8d._comment
View file

@ -7,4 +7,6 @@
Is it possible to edit comments on the branchable wiki? I realized there was a sentence I failed to finish when posting [this comment](https://git-annex.branchable.com/todo/sync_--branches__to_sync_only_specified_branches___40__e.g._git-annex__41__/#comment-19feab1afb2e0b33315a8368a7cdebf7) and I'd love to go back and finish the thought. The \"Edit\" button at the top of the page lets me edit the content of the page, but not any of the comments.
I tried cloning the wiki, editing the file corresponding to my comment, and then pushing, but the push was rejected (the changes were in doc tree so I expected it to be accepted, but perhaps comments are more locked down).
Update: It seems I am able to edit comments by cloning the wiki, editing (comments are located in a folder with the same name as the associated page), committing, and then pushing. Yay!
"""]]

26
doc/git-annex-find/comment_9_d7ea718f3a898bf9f3e1514802b99fec._comment Normal file
View file

@ -0,0 +1,26 @@
[[!comment format=mdwn
username="Dan"
avatar="http://cdn.libravatar.org/avatar/986de9e060699ae70ff7c31342393adc"
subject="Confirming all annexed files exist elsewhere?"
date="2022-07-27T16:35:21Z"
content="""
I'm preparing to recycle an aging laptop that has a few git-annex repos on it. I'd like to confirm that anything in its annex(es) exist in at least one other place and want to confirm what I'm doing to check this makes sense.
At first glance, it seems like the appropriate way to do this is with `git annex find --in here --not --copies=2` (where the latter predicate should be equal to testing for copies strictly less than 2).
Since I have recently `git annex sync`-ed, this doesn't turn up anything.
However, if I understand everything correctly, this *only* checks files that are reachable from my current working tree.
Thus, if there are a bunch of files in my (not currently checked out) `dev` branch that are *not* in my worktree, then this query will not discover them.
I can get them to be considered with `git annex find --in here --not --copies=2 --branch dev`.
I could manually (or via script) loop over all of my branches and repeat `git annex find --in here --not --copies=2 --branch ${branch}` to check all of my branches.
However, this will only check the tips.
Suppose there's a file that previously existed (solely) in my master branch, but at some point it was `git rm`-ed. Then unless I specify using `--branch` a TREEISH that has that file, it will not be considered.
So, I need to use some sort of query tool that supports both the `--all` flag as well as all of the matching options.
The only thing I was able to find was `whereis`, so I can run `git annex whereis --all --in here --not --copies=2` in order to identify keys corresponding to files that are (a) locally available but where (b) the number of copies is not 2 or greater (i.e., it is here and only here).
I suppose I could also just plunge ahead with `git annex copy --to ${remote} --all --in here --not --copies=2`, but it's reassuring to be able to run the query and see what would need to get moved (as well as to see the query come back empty before I wipe the hard drive).
Is this an appropriate use of `git annex whereis`, or is there a way that I can use `git annex find` to accomplish this, or perhaps some other query tool?
In essence, I just want a way of querying "all" of the objects that git annex has ever known about using all of the standard matching options.
I see discussion above regarding the lack of `--all` support for `git annex find`, which at the time suggested using `findref` instead but it seems like that has been deprecated in favor of `find`.
"""]]

17
doc/todo/wishlist__58___--dry-run_option_for_all_commands/comment_5_e139434d88638d05c84b721abdbb406c._comment Normal file
View file

@ -0,0 +1,17 @@
[[!comment format=mdwn
username="kdm9"
avatar="http://cdn.libravatar.org/avatar/b7b736335a0e9944a8169a582eb4c43d"
subject="Bump for --want-get/drop-by"
date="2022-07-26T18:19:36Z"
content="""
Hi Joey,
A million thanks for a fantastic tool.
I came across the need today for the aforementioned --want-get-by/ --want-drop-by REMOTE options. Is this something that has since been developed/worked around, or is it still in the infinite TODO?
In the mean time, some more explicit documentation that --want-get/want-drop only ever applies to . would be good. I'll see if I can make a PR for this since I can write docs (but alas Haskell not so much).
best,
Kevin
"""]]