diff options
author | Joey Hess <joey@kitenet.net> | 2014-06-09 14:43:49 -0400 |
---|---|---|
committer | Joey Hess <joey@kitenet.net> | 2014-06-09 14:43:49 -0400 |
commit | b29694b2e61d5f0ca36a3709eb7f76fdf3a739a5 (patch) | |
tree | 4b0548bd8c313e73e21a41b4662b6a57ceef964e /doc | |
parent | c9e8ad671de1da7e75d45973109d223c9d4e8e81 (diff) | |
parent | ce9cccb1f571028f3b697380422d07426803efb8 (diff) |
Merge branch 'master' of ssh://git-annex.branchable.com
Diffstat (limited to 'doc')
14 files changed, 251 insertions, 1 deletions
diff --git a/doc/bugs/Auto-repair_greatly_slows_down_the_machine/comment_10_d46c6314bff75a0ae679bc2358b28c2b._comment b/doc/bugs/Auto-repair_greatly_slows_down_the_machine/comment_10_d46c6314bff75a0ae679bc2358b28c2b._comment new file mode 100644 index 000000000..5fb031e25 --- /dev/null +++ b/doc/bugs/Auto-repair_greatly_slows_down_the_machine/comment_10_d46c6314bff75a0ae679bc2358b28c2b._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="EskildHustvedt" + ip="80.202.103.55" + subject="comment 10" + date="2014-06-07T05:47:25Z" + content=""" +Given that it's ususally the same repo, I'm going to try to create a completely fresh repository instead and see if the frequent auto-repairs are stopped by that. +"""]] diff --git a/doc/bugs/FAT:_Date_resolution_for_mtime_2s--__62___implications/comment_6_650d950da065eeac966c2498418c668d._comment b/doc/bugs/FAT:_Date_resolution_for_mtime_2s--__62___implications/comment_6_650d950da065eeac966c2498418c668d._comment new file mode 100644 index 000000000..94cbad0e6 --- /dev/null +++ b/doc/bugs/FAT:_Date_resolution_for_mtime_2s--__62___implications/comment_6_650d950da065eeac966c2498418c668d._comment @@ -0,0 +1,22 @@ +[[!comment format=mdwn + username="martin" + ip="89.183.56.177" + subject="use case and answer to joey's question "...then when..."" + date="2014-06-08T04:59:42Z" + content=""" +Hi joey, + +i really think we should repair the timestamp instead of force the user to `git-annex add` possibly corrupted files/content (see your comment above) git-annex checksums are excellent for data integrity but they are useless if we bypass them in case of adding and propagating +potentially corrupted content with `git-annex add` + +So here's for example a useful use case: + +1. user fills his transfer repo in town A. He checks (`git annex fsck`) that everything is fine. He unmounts the drive and travels to town B. + +2. In town B user mounts the drive and sees, that he suddenly doesn't have \"access\" to those \"crippled files\" on his transfer repo (the files seems modified for the user without a reason - why should he `git-annex add` them again?? - he'd rather think about data corruption) . He wonders whats going on and thats why he does a + +3. `git-annex fsck` . `git annex fsck` should checksum also such crippled files, should report correct checksums if they are correct (so that the users knows their usb drive is working properly) and should give a message like this: \"checksum ok - crippled timestamp - repair with git-annex fsck --repair-timestamp or define a modify window \"- (to be implemented - in rsync the problem is already solved with this option \"--modify-window=NUM compare mod-times with reduced accuracy\") + +In my case distance between town B and town A was approx 400km and in town B i didnt know what was going on. So i went back to town A without success for further investigation of my usb drive... :-(( + +"""]] diff --git a/doc/bugs/On_Ubuntu_14.04_assistant_fails_to_create_new_setup.mdwn b/doc/bugs/On_Ubuntu_14.04_assistant_fails_to_create_new_setup.mdwn new file mode 100644 index 000000000..14d9242d1 --- /dev/null +++ b/doc/bugs/On_Ubuntu_14.04_assistant_fails_to_create_new_setup.mdwn @@ -0,0 +1,91 @@ +### Please describe the problem. + +Following steps from http://git-annex.branchable.com/assistant/quickstart/ does not get past the first screen. + +### What steps will reproduce the problem? + +* On a nearly fresh Lubuntu system, nearly fresh account, Lubuntu session, run `git-annex` from the start menu. +* Opens firefox, in `Create a git-annex repository` select my `~/Documents` folder, press `Make Repository`. + +* Expected: a new, different page opens. +* Observed: the same page opens, only difference the path displayed is `/home/mylogin/Documents`. Pressing `Make Repository` again shows the same page again. + +I couldn't find any logs at the time. Now I see that they are in .git/annex/daemon.log but content from that time is already gone. + +### What version of git-annex are you using? On what operating system? + +A fresh Ubuntu 14.04 (actually Lubuntu but this shouldn't change anything, right ?), create a user, login. + + + LC_ALL=C apt-cache policy git-annex + git-annex: + Installed: 5.20140412ubuntu1 + Candidate: 5.20140412ubuntu1 + Version table: + *** 5.20140412ubuntu1 0 + 500 http://fr.archive.ubuntu.com/ubuntu/ trusty/universe i386 Packages + 100 /var/lib/dpkg/status + + +### Please provide any additional information below. + +[[!format sh """ +# No command line in bug occurrence. This is the transcript of the workaround I found. +# Actually, the PC was rebooted then I went command line. +cd ~/Documents +git status +fatal: This operation must be run in a work tree +# oh I see it's a bare repo +git annex add . +add (my file names... one line for each) ok +(Recording state in git...) + +Now the webapp seems to run okay, I can see many pages, schedule checks, etc. + +# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log +-> Ok but log shows only events after I manually dit git annex add. + +[2014-06-08 14:28:46 CEST] main: starting assistant version 5.20140412ubuntu1 +[2014-06-08 14:28:46 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}) +(scanning...) [2014-06-08 14:28:46 CEST] Watcher: Performing startup scan +(started...) [2014-06-08 14:28:47 CEST] Committer: Adding (myfiles) + +add (my files...) ok +[2014-06-08 14:32:51 CEST] Committer: Committing changes to git +[2014-06-08 14:34:12 CEST] Committer: Committing changes to git +[2014-06-08 14:34:13 CEST] Committer: Adding (myfiles) +ok +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +(Recording state in git...) +add (myfile) ok +add (myfile) [2014-06-08 14:34:13 CEST] Committer: Committing changes to git +[2014-06-08 14:42:48 CEST] Cronner: Consistency check in progress +fsck (myfile) (checksum...) +ok + +# End of transcript or log. +"""]] + + + +# Question: + +cat /etc/xdg/autostart/git-annex.desktop +[Desktop Entry] +Type=Application +Version=1.0 +Name=Git Annex Assistant +Comment=Autostart +Terminal=false +Exec=/usr/bin/git-annex assistant --autostart +Categories= + +Should there be a git-annex process whenever I log in even if I don't launch the webapp ? +I can check that on next login. + +At the moment there is "git-annex webapp" and several child processes. diff --git a/doc/bugs/error_compiling_network-info_when_compiling_git-annex/comment_2_4e5ffd0d5b965b9429b937610b7998d5._comment b/doc/bugs/error_compiling_network-info_when_compiling_git-annex/comment_2_4e5ffd0d5b965b9429b937610b7998d5._comment new file mode 100644 index 000000000..8e631a115 --- /dev/null +++ b/doc/bugs/error_compiling_network-info_when_compiling_git-annex/comment_2_4e5ffd0d5b965b9429b937610b7998d5._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawm5WyknJirJJridJjiPNgrlYxGG9xrZBvA" + nickname="Daniel" + subject="a different fix" + date="2014-06-07T04:27:47Z" + content=""" +Thanks. I also went back and took a closer look at the error; it looks like fixing network-info is pretty easy as well. <https://github.com/jystic/network-info/pull/10> +"""]] diff --git a/doc/bugs/git-annex:_createSession:_permission_denied___40__Operation_not_permitted__41__.mdwn b/doc/bugs/git-annex:_createSession:_permission_denied___40__Operation_not_permitted__41__.mdwn new file mode 100644 index 000000000..72499ffa3 --- /dev/null +++ b/doc/bugs/git-annex:_createSession:_permission_denied___40__Operation_not_permitted__41__.mdwn @@ -0,0 +1,31 @@ +### Please describe the problem. +git-annex crashes with "git-annex: createSession: permission denied (Operation not permitted)" when creating the first repository. Trying to start git-annex webapp after that crashes again. + +### What steps will reproduce the problem? +* Download standalone tarball +* Unpack +* Go to new folder, call "git-annex webapp" +* Click Make repository + +### What version of git-annex are you using? On what operating system? +git-annex version: 5.20140606-g48793b6 +build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA CryptoHash +key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL +remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier ddar hook external + +Ubuntu 14.04 LTS + +Linux eee 3.13.0-29-generic #53-Ubuntu SMP Wed Jun 4 21:02:19 UTC 2014 i686 i686 i686 GNU/Linux + +### 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 +$ git-annex webapp +Launching web browser on file:///tmp/webapp3414.html +git-annex: createSession: permission denied (Operation not permitted) +WebApp crashed: createSession: permission denied (Operation not permitted) +$ +# End of transcript or log. +"""]] diff --git a/doc/devblog/day_178-179__screencast_and_what_next/comment_1_eeba788fed45cb22f9cc2a738ceaa074._comment b/doc/devblog/day_178-179__screencast_and_what_next/comment_1_eeba788fed45cb22f9cc2a738ceaa074._comment new file mode 100644 index 000000000..d5bb0a183 --- /dev/null +++ b/doc/devblog/day_178-179__screencast_and_what_next/comment_1_eeba788fed45cb22f9cc2a738ceaa074._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawm8BAEUyzYhORZmMuocRTk4M-3IumDm5VU" + nickname="luciusf0" + subject="Windows Support +1" + date="2014-06-06T21:54:38Z" + content=""" +I just also (like others) wanna state my strong interest in a windows port. Actually it's the only thing which is holding me back of using git-annex for real, as I live and work in a mixed-OS environment. The git-annex features would be the answers to an awful lot of our day-to-day problems, and I cannot wait to have it ready for a production environment. So -> Windows Port +1 +"""]] diff --git a/doc/devblog/day_178-179__screencast_and_what_next/comment_2_d44e67e34615c7b00e29f307556cdd06._comment b/doc/devblog/day_178-179__screencast_and_what_next/comment_2_d44e67e34615c7b00e29f307556cdd06._comment new file mode 100644 index 000000000..defb4a80f --- /dev/null +++ b/doc/devblog/day_178-179__screencast_and_what_next/comment_2_d44e67e34615c7b00e29f307556cdd06._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawnBJ6Dv1glxzzi4qIzGFNa6F-mfHIvv9Ck" + nickname="Jim" + subject="Android" + date="2014-06-08T02:44:45Z" + content=""" +As I don't use Windows and git-annex is already fitting my Linux use cases perfectly, I'd have to vote for Android. FWIW, I have previously posted some thoughts on what would I see as lacking on Android [here](http://git-annex.branchable.com/forum/Controlling_content_on_mobile_device/). +"""]] diff --git a/doc/devblog/day_180__porting.mdwn b/doc/devblog/day_180__porting.mdwn index c0e56406b..27b4eaca1 100644 --- a/doc/devblog/day_180__porting.mdwn +++ b/doc/devblog/day_180__porting.mdwn @@ -9,5 +9,5 @@ security holes-of-the-week. (git-annex uses gnutls only for XMPP, and does not use openssl itself, but a few programs bundled with it, like curl, do use openssl.) -A nice peice of news: OSX Homebrew now contains git-annex, so it can be +A nice piece of news: OSX Homebrew now contains git-annex, so it can be easily installed with `brew install git-annex` diff --git a/doc/devblog/day_180__porting/comment_1_133875f4435a298b85ddfb8a2cc11a7a._comment b/doc/devblog/day_180__porting/comment_1_133875f4435a298b85ddfb8a2cc11a7a._comment new file mode 100644 index 000000000..2aa67e823 --- /dev/null +++ b/doc/devblog/day_180__porting/comment_1_133875f4435a298b85ddfb8a2cc11a7a._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="Tamschi" + ip="178.27.213.202" + subject="It's still impossible to use the git-annex repository on Windows." + date="2014-06-09T14:44:07Z" + content=""" +Since the bug tracker is in the same repository and branch as the main program (why?), any bugs submitted with a colon in the title will prevent access on NTFS file systems. +There is at least one such instance, I assume it potentially affects blog posts too. +"""]] diff --git a/doc/forum/Need_to_recover_unused_files_because_of_bad_sync__63__/comment_1_af0ed0730645c1e3c9a4946acd48c18a._comment b/doc/forum/Need_to_recover_unused_files_because_of_bad_sync__63__/comment_1_af0ed0730645c1e3c9a4946acd48c18a._comment new file mode 100644 index 000000000..8f2905c6f --- /dev/null +++ b/doc/forum/Need_to_recover_unused_files_because_of_bad_sync__63__/comment_1_af0ed0730645c1e3c9a4946acd48c18a._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="108.236.230.124" + subject="comment 1" + date="2014-06-06T18:18:36Z" + content=""" +It's not clear from your description when the files got deleted or why, but you can use `git log --stat` to find out. Then you can `git revert` the problem commit. +"""]] diff --git a/doc/forum/Need_to_recover_unused_files_because_of_bad_sync__63__/comment_2_12f3c2bb2458b69e6355c8f94bab868f._comment b/doc/forum/Need_to_recover_unused_files_because_of_bad_sync__63__/comment_2_12f3c2bb2458b69e6355c8f94bab868f._comment new file mode 100644 index 000000000..4c30d0f4c --- /dev/null +++ b/doc/forum/Need_to_recover_unused_files_because_of_bad_sync__63__/comment_2_12f3c2bb2458b69e6355c8f94bab868f._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="feulif" + ip="151.27.145.89" + subject="Thank you" + date="2014-06-08T08:36:40Z" + content=""" +Thank you so much! +That solved my problem and restored my precious photos! + +Now I see there are similar issues in the forum already, but I was searching for the bad keywords (like \"restore unused\") and I could not find them. + +By the way, your software is outstanding. +"""]] diff --git a/doc/install/NixOS/comment_1_4e487ddd2654a8a992c1538b9c3bf003._comment b/doc/install/NixOS/comment_1_4e487ddd2654a8a992c1538b9c3bf003._comment new file mode 100644 index 000000000..8424b632d --- /dev/null +++ b/doc/install/NixOS/comment_1_4e487ddd2654a8a992c1538b9c3bf003._comment @@ -0,0 +1,21 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawn3p4i4lk_zMilvjnJ9sS6g2nerpgz0Fjc" + nickname="Matthias" + subject="build failure" + date="2014-06-09T15:13:18Z" + content=""" +Building git-annex with Nix 1.7 fails for me. Error: + + trying https://git.samba.org/?p=rsync.git;a=commitdiff_plain;h=0dedfbce2c1b851684ba658861fe9d620636c56a + % Total % Received % Xferd Average Speed Time Time Time Current + Dload Upload Total Spent Left Speed + 100 2277 0 2277 0 0 2805 0 --:--:-- --:--:-- --:--:-- 5735 + output path `/nix/store/w6l1c3cdr52arymv3zgwly7razwnsdll-CVE-2014-2855.patch' should have sha256 hash `1jpwwdf07naqxc8fv1lspc95jgk50j5j3wvf037bjay2qzpwjmvf', instead has `0j1pqmwsqc5mh815x28izi4baki2y2r5q8k7ma1sgs4xsgjc4rk8' + building path(s) `/nix/store/85v7c8b3ygpfj8m8bk98kcygf29qcbq7-cacert-20131205.pem.bz2' + cannot build derivation `/nix/store/im9p1y2xbh08yrwp5yggj1ii884wv3ql-rsync-3.1.0.drv': 1 dependencies couldn't be built + killing process 2599 + cannot build derivation `/nix/store/sl48cnm06m7mcqxjfj2b0yv8am3blqr3-git-annex-5.20140517.drv': 1 dependencies couldn't be built + error: build of `/nix/store/sl48cnm06m7mcqxjfj2b0yv8am3blqr3-git-annex-5.20140517.drv' failed + +Someone has an idea what Nix expects me to do in this situation? +"""]] diff --git a/doc/tips/metadata_driven_views/comment_2_13ae4e3668b693c0eefaca23b88515cf._comment b/doc/tips/metadata_driven_views/comment_2_13ae4e3668b693c0eefaca23b88515cf._comment new file mode 100644 index 000000000..3ec563311 --- /dev/null +++ b/doc/tips/metadata_driven_views/comment_2_13ae4e3668b693c0eefaca23b88515cf._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawln3ckqKx0x_xDZMYwa9Q1bn4I06oWjkog" + nickname="Michael" + subject="possible to have a view based on file location info?" + date="2014-06-08T03:55:24Z" + content=""" +For example, I'd like to have a view that only contains files present in this git-annex repository (no dangling symlinks). + +"""]] diff --git a/doc/todo/wishlist:_Add_--byte-limit_option.mdwn b/doc/todo/wishlist:_Add_--byte-limit_option.mdwn new file mode 100644 index 000000000..28642b50d --- /dev/null +++ b/doc/todo/wishlist:_Add_--byte-limit_option.mdwn @@ -0,0 +1,14 @@ +This option is related to `--time-limit`, but stops after processing X +bytes. For example, I often need to free up a certain amount of space on +a disk and want `git-annex move` to stop after it has copied a specified +amount of data: + + git annex move --to otherdisk --byte-limit 3G + git annex drop --auto --byte-limit 500m + git annex get --byte-limit 500m + +I've been using some `annex.diskreserve` trickery now and then to +accomplish this, but it's a bit cumbersome and also not a very precise +way to specify the amount I want to copy/move/get. The last example +would also be a useful command to limit the traffic when I'm connecting +via mobile – get as much as possible, but don't blow the mobile quota. |