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 2014-08-23 16:17:31 -07:00
commit 23592716c9
3 changed files with 74 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

35
doc/bugs/Problem_setting_up_encrypted_repository_using_the_assistant_with___40__outside_of_git-annex__41___shared_pgp_key/comment_1_c8e7be58222afff2a4c1df60f657d2ed._comment Normal file
View file

@ -0,0 +1,35 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawk7iPiqWr3BVPLWEDvJhSSvcOqheLEbLNo"
nickname="Dirk"
subject="comment 1"
date="2014-08-23T18:13:06Z"
content="""
Restarting the two git-annex instances actually now leads to an error message on computer B.
[[!format sh \"\"\"
[2014-08-23 20:02:00 CEST] main: starting assistant version 5.20140818-g10bf03a
[2014-08-23 20:02:00 CEST] Cronner: You should enable consistency checking to protect your data.
dbus failed; falling back to mtab polling (ClientError {clientErrorMessage = \"runClient: unable to determine DBUS address\", clientErrorFatal = True})
[2014-08-23 20:02:00 CEST] TransferScanner: Syncing with C_annex
No known network monitor available through dbus; falling back to polling
(scanning...) [2014-08-23 20:02:00 CEST] Watcher: Performing startup scan
gcrypt: Development version -- Repository format MAY CHANGE
(started...)
gcrypt: Decrypting manifest
gpg: Signature made Sat 23 Aug 2014 03:34:08 PM CEST using RSA key ID 0A7AA2A4
gpg: Good signature from \"dirk's git-annex encryption key\"
gcrypt: Packfile 59a8d97d3d252effb044625e020f9dc8621804649186a5c33c4e47f9e961cc1a does not match digest!
fatal: early EOF
gcrypt: Development version -- Repository format MAY CHANGE
gcrypt: Decrypting manifest
gpg: Signature made Sat 23 Aug 2014 03:34:08 PM CEST using RSA key ID 0A7AA2A4
gpg: Good signature from \"dirk's git-annex encryption key\"
gcrypt: Encrypting to: -r 7815EA570A7AA2A4
gcrypt: Requesting manifest signature
To gcrypt::ssh://dirk@git-annex-C-dirk_1022_annex/~/annex/
e1d6871..85b70d6 annex/direct/master -> synced/master
+ e68b5a9...99dc810 git-annex -> synced/git-annex (forced update)
\"\"\"]]
"""]]

12
doc/bugs/Windows_build_has_hardcoded_paths/comment_4_01096994c19b7d0df1cc6866d4f22e21._comment Normal file
View file

@ -0,0 +1,12 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawmBmv0HhwTFxkpxlf8ifTlMOHnIwHCHTYs"
nickname="y"
subject="path on windows"
date="2014-08-23T22:02:07Z"
content="""
I think I have a related problem on win7 sp1.
When first installing msys git, there's a screen asking for how to set the PATH variable. I chose the option not to update the windows PATH variable, which is the default. Then I installed git annex. Then launching the git-annex-autostart.vbs as well as the webapp one gets an object not found error (on line 2). launching git-annex from git bash with full path yielded an error about not finding git.
Then I proceeded and reinstalled git on top of itself and picked the option to only add git and bash to windows path and it worked.
"""]]

27
doc/bugs/tahoe_remote_has_no_repair.mdwn Normal file
View file

@ -0,0 +1,27 @@
### Please describe the problem.
The tahoe-lafs remote has no built-in way to perform the repair operation.
This results to data loss if expiration is enabled on the Tahoe grid.
For the current tahoe-lafs release (1.10.0), the only way storage space is freed
is via garbage collection. Garbage collection removes shares whose lease has expired.
Data loss will occur if leases are not periodically renewed via
"tahoe repair --add-lease WRITECAP".
The current implementation of the Tahoe remote in git-annex does not offer a way to
run lease renewal, and cannot be used on grids where GC is enabled. (GC is not enabled
in the default configuration, but on private grids it is a sensible option.)
One way renewal could be made easier to do is to add the uploaded files to a directory
in Tahoe, so that the leases could be easily updated if the directory writecap is known,
without needing to go through the full list of writecaps for each file stored.
### What steps will reproduce the problem?
1. Use tahoe remote on a tahoe grid where GC is enabled.
2. After GC expiration period, data loss ensues.
### What version of git-annex are you using? On what operating system?
Seems to affect current git master (as of 2014-08-24).