Recent comments posted to this site:
@imlew git add
runs git-annex as a filter, so it cannot output progress
displays or other messages on stdout at that point. It would have to output
to stderr, but outputting non-errors to stderr is not great either.
I tried to use Backblaze B2 using the second method, and tried different application key permissions. Hopefully I can save your time if you’re going to use this special remote.
In order to init a B2 remote, you should create a key with the ability to read & write all buckets, and you must create a new bucket using git-annex (by setting a unique name in bucket=
). If you create an empty bucket using Backblaze's web UI, then use that bucket for git annex initremote
, you will receive this error message: (InternalException (HandshakeFailed (Error_Protocol ("expecting server hello, got alert : [(AlertLevel_Fatal,IllegalParameter)]",True,HandshakeFailure))))
.
In order to enable a B2 remote, you need a key with read & write permission to the bucket you're using. If you created a key with only read permission, you can’t use git annex get
on that remote.
--includesamecontent
states that is the "same as --not --includesamecontent
", this is probably a bug in the documentation?
I have gotten as far as running git init
and git annex init
on my server. There’s a bunch of stuff there and I figure I’ll just add the things that I care about as I go.
I read the page on the webapp and it just says that it “allows easy setup of a git-annex repository, and control of the git-annex assistant”. I started the webapp on my server and I was alarmed to see a message in the webapp that it was adding things to git annex. Over on the page for the git annex assistant it says “By default, all new files in the directory will be added to the repository” which is definitely not what I expected. I’m a new user trying to learn how to use git annex and this was an unpleasant surprise. Can we amend the docs for the webapp to warn about this behavior?
I'm sure that the private information will not leak out from
.git/annex/journal-private/
into the git-annex branch
after annex.private is unset. The design ensures this because, when
making a change to the branch, it only reads the private journal file
when the repository whose information is being changed is private.
However, when git-annex does not have any private repositories configured, an optimisation makes it skip trying to read from the private journal. So information about those repositories, that were private, will no longer be read.
This effect is easy to see, for example:
joey@darkstar:~/tmp/xxx>git-annex whereis
whereis foo (1 copy)
ff1f0bbd-7be6-45ff-8c90-fd322820b717 -- joey@darkstar:~/tmp/xxx [here]
ok
joey@darkstar:~/tmp/xxx>git config annex.private false
joey@darkstar:~/tmp/xxx>git-annex whereis
whereis foo (0 copies) failed
whereis: 1 failed
I think this could be improved, eg it could check once if the private journal exists and if so read from it even when no private uuids are currently configured. A single stat to support this would be ok; the goal was to avoid checking nonexistany files on every branch read when private repositories are not used.
Configuring any remote with annex-private can be used to work around that problem, that lets it read information about all previously-private repositories as well.
git annex webapp
launches the assistant. It might even do git annex assistant --autostart
and launch the assistant in all configured repos. That is indeed an important info to know. Everyone can edit these pages (the Edit button above) btw.
Moved some comments about a bug to uninit fails when I symlink your symlink. Please do not use this man page's comment section to file bug reports.
I thought I had the same problem as lh (
git add
not respecting the largefiles config), but when I tried to make a minimal example I noticed thatgit add
does add files to the annex, it just doesn't print the progress message thatgit annex add
usually prints.Is there any way to get it to do that? It would help newbs like me know that largefiles is indeed working and for files that are actually large it can be helpful to see the progress.