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

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

Browse source
This commit is contained in:
Joey Hess 2020-06-23 16:08:53 -04:00
commit ed69f50361
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
4 changed files with 44 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
doc/forum/Dead_repo_content_is_not_considered_unused..mdwn Normal file
View file

@ -0,0 +1,15 @@
I can't get content referenced in a dead repo to be considered unused.
Setup:
1. Make repo A and B, connect them
2. Add file to A, copy to B, sync
3. Sync B
4. Mark A dead
5. Delete symlink from B
6. Run git-annex forget --drop-dead on B
7. Run git-annex unused on B
The file does not appear as unused. Am I doing something wrong or is this genuinely impossible?
I can understand the reasons for not wanting it to work this way in case the dead repo had important files, but what this means is files I genuinely want to drop will never be considered unused if they existed in the dead repo. This could create an issue for me if I lose a repo in one of my very large annexes, because that could mean gigs of wasted space. I rely on unused to safely drop content because the drop command may remove files that are still referenced somewhere else (duplicate symlinks).

8
doc/forum/Thank_you/comment_1_3be1d5e92c3abc222713c75169b43dfb._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="ghen1"
avatar="http://cdn.libravatar.org/avatar/efd0e92b6198291138f0cd7aedbf86b6"
subject="comment 1"
date="2020-06-22T20:40:08Z"
content="""
I second this. I've used it every day since discovering it to manage file storage across several locations. Would have had to hack something together on my own otherwise, and that wouldn't be easy. git-annex is one of the best ideas ever.
"""]]

10
doc/forum/Where_is_the_S3_config__63__.mdwn Normal file
View file

@ -0,0 +1,10 @@
Some time ago I created an S3 remote that uses a Digital Ocean "space", which is S3 compatible. It works fine and I've copied some content there and can get it from there. Before I trust this remote though I want to understand where the configuration is that points it to digital ocean. When I look at .git/config there is this section:
[remote "cloud"]
annex-s3 = true
annex-uuid = <a UUID>
annex-ignore = false
I've looked around and inside the annex subdirectory but haven't been able to find where the config is stored that I must have entered to create this remote. Is the annex-uuid a key to a database with the config? How do I view it?
Thanks for git-annex BTW

11
doc/forum/Where_is_the_S3_config__63__/comment_1_63009ad122cfafc9682e06f984eaefe1._comment Normal file
View file

@ -0,0 +1,11 @@
[[!comment format=mdwn
username="kyle"
avatar="http://cdn.libravatar.org/avatar/7d6e85cde1422ad60607c87fa87c63f3"
subject="comment 1"
date="2020-06-23T13:29:37Z"
content="""
Take a look at the git-annex branch, in particular remote.log.
git cat-file -p git-annex:remote.log
"""]]