From 215c02f0a5d7abc1a33424dbaef152f00bda7330 Mon Sep 17 00:00:00 2001 From: "https://me.yahoo.com/a/FHnTlSBo1eCGJRwueeKeB6.RCaPbGMPr5jxx8A--#ce0d8" Date: Sat, 18 Jan 2014 22:08:15 +0000 Subject: [PATCH 1/7] --- doc/forum/Can_not_drop_unused_file.mdwn | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/forum/Can_not_drop_unused_file.mdwn diff --git a/doc/forum/Can_not_drop_unused_file.mdwn b/doc/forum/Can_not_drop_unused_file.mdwn new file mode 100644 index 0000000000..8ec48eb14f --- /dev/null +++ b/doc/forum/Can_not_drop_unused_file.mdwn @@ -0,0 +1,14 @@ +I have encrypted directory remote on a usb drive over time it accumulated some unused files. I would like to drop them running, + + git annex --unused --from external + +returns a list of unused files when I try to drop them with, + + + git annex dropunused --force --from external 1-XX + +I get, + + dropunused XX (from external...) failed + +I can not seem to get rid of these files. From c5c339e87e3629d79aea2b9735a4d783b7c491eb Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Sat, 18 Jan 2014 22:39:37 +0000 Subject: [PATCH 2/7] Added a comment --- ...t_1_cea83dfdf4cdb4f6efb3f2b33a39a51f._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/forum/Can_not_drop_unused_file/comment_1_cea83dfdf4cdb4f6efb3f2b33a39a51f._comment diff --git a/doc/forum/Can_not_drop_unused_file/comment_1_cea83dfdf4cdb4f6efb3f2b33a39a51f._comment b/doc/forum/Can_not_drop_unused_file/comment_1_cea83dfdf4cdb4f6efb3f2b33a39a51f._comment new file mode 100644 index 0000000000..4a6eacc510 --- /dev/null +++ b/doc/forum/Can_not_drop_unused_file/comment_1_cea83dfdf4cdb4f6efb3f2b33a39a51f._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.68" + subject="comment 1" + date="2014-01-18T22:39:37Z" + content=""" +One reason it might fail (especially if it's not printing any useful message beyond \"(failed)\") is if it thought the file was present in the repositort, but something has happened to it. + +So, I suggest you try: + +git annex fsck --from external + +Followed by dropping again. + +If that doesn't help, I'd recommend stracing the dropping of one of the unused files, and see what's going wrong toward the end. +"""]] From 8c027c5ced6865397901a2e50c319b670505a16e Mon Sep 17 00:00:00 2001 From: "https://arthur.lutz.im/" Date: Sun, 19 Jan 2014 10:53:10 +0000 Subject: [PATCH 3/7] added bug about .local adresses --- ...e_.local_adresses_using_avahi_or_bonjour.mdwn | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/bugs/Resolve_.local_adresses_using_avahi_or_bonjour.mdwn diff --git a/doc/bugs/Resolve_.local_adresses_using_avahi_or_bonjour.mdwn b/doc/bugs/Resolve_.local_adresses_using_avahi_or_bonjour.mdwn new file mode 100644 index 0000000000..74966415eb --- /dev/null +++ b/doc/bugs/Resolve_.local_adresses_using_avahi_or_bonjour.mdwn @@ -0,0 +1,16 @@ +### Please describe the problem. + +trying to add a remote host using its avahi local name : nas.local (for example). + +### What steps will reproduce the problem? + +add remote server, use nas.local > cannot resolve nas.local + +### What version of git-annex are you using? On what operating system? + +Version: 5.20140116-g2d9ec29 +Ubuntu + +### Please provide any additional information below. + + From f6c45f8ba44d3d2b14445a52ac877af43f190f92 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawkq2cjugiSvKWiWmcah3CPBqviQV_cin9I" Date: Sun, 19 Jan 2014 14:13:55 +0000 Subject: [PATCH 4/7] Added a comment: The world of Mac --- ...comment_1_b871bf0606dc29be9b8c2e5dc150f708._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/devblog/day_99__catching_up_again/comment_1_b871bf0606dc29be9b8c2e5dc150f708._comment diff --git a/doc/devblog/day_99__catching_up_again/comment_1_b871bf0606dc29be9b8c2e5dc150f708._comment b/doc/devblog/day_99__catching_up_again/comment_1_b871bf0606dc29be9b8c2e5dc150f708._comment new file mode 100644 index 0000000000..933de78737 --- /dev/null +++ b/doc/devblog/day_99__catching_up_again/comment_1_b871bf0606dc29be9b8c2e5dc150f708._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawkq2cjugiSvKWiWmcah3CPBqviQV_cin9I" + nickname="Yury" + subject="The world of Mac" + date="2014-01-19T14:13:55Z" + content=""" +I think that there is nothing fundamental about Mac OS X, which would prevent one from making a clean chroot that would work for non-root users. For instance, I believe that jailkit has been reported to work just fine. The problem is that you'll have to rebuild most of the stuff you need from scratch, which is very tedious. Might be easier to find instances where Homebrew has something like -march=native added to the $CFLAGS (not that I particularly fancy Homebrew of all 'missing' package managers on OS X). + +Anyways, it sounds like I'm going to get a Mac Mini donated sometime soon and I'm curious as to what would be the best way to make use of it for the CI system... +"""]] From eee3540e2d606278e53c316478685e299d620a6c Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawniCRkhl_W87gOK5eElfsef3FoUsUFpAr4" Date: Sun, 19 Jan 2014 19:17:55 +0000 Subject: [PATCH 5/7] create --- ...ing_DCIM__47__Camera_not_being_configurable.mdwn | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/bugs/Android_:_handling_DCIM__47__Camera_not_being_configurable.mdwn diff --git a/doc/bugs/Android_:_handling_DCIM__47__Camera_not_being_configurable.mdwn b/doc/bugs/Android_:_handling_DCIM__47__Camera_not_being_configurable.mdwn new file mode 100644 index 0000000000..45475f7400 --- /dev/null +++ b/doc/bugs/Android_:_handling_DCIM__47__Camera_not_being_configurable.mdwn @@ -0,0 +1,13 @@ +### Please describe the problem. + +In order to handle the fact that the directory where pictures are saved is not configurable on my phone, I set up a second git annex repository with the Repository group "file source". + +### What version of git-annex are you using? On what operating system? + +5.20140108-gce9652 + +### Please provide any additional information below. + +In the log, there are many "too many open files" errors like these : + +git:createProcess: runInteractiveProcess: pipe: resource exhausted (Too many open files) From 83562fccbc1538f99542040ff1ef631c63fcf854 Mon Sep 17 00:00:00 2001 From: Richard Hartmann Date: Sun, 19 Jan 2014 22:41:36 +0100 Subject: [PATCH 6/7] Typo --- doc/devblog/day_99__catching_up_again.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/devblog/day_99__catching_up_again.mdwn b/doc/devblog/day_99__catching_up_again.mdwn index e82c436bff..118a21f8d2 100644 --- a/doc/devblog/day_99__catching_up_again.mdwn +++ b/doc/devblog/day_99__catching_up_again.mdwn @@ -7,7 +7,7 @@ fixes to make it build on all architectures again, and then the backport can be updated again too. I have been struggling with a problem with the OSX builds, which fail with -a SIGILL on some machines. It seems that homebrew likes to agressively +a SIGKILL on some machines. It seems that homebrew likes to agressively optimise things it builds, and while I have had some success with its `--build-bottle` option, something in the gnutls stack used for XMPP is still over-optimised. Waiting to hear back from Kevin on cleaning up some From 348a270cfe08082981ec7132ca0444bb32704bb2 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Sun, 19 Jan 2014 22:43:11 +0000 Subject: [PATCH 7/7] Added a comment --- .../comment_1_71cfedf4328eab224c7fb797c420ad0a._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/Resolve_.local_adresses_using_avahi_or_bonjour/comment_1_71cfedf4328eab224c7fb797c420ad0a._comment diff --git a/doc/bugs/Resolve_.local_adresses_using_avahi_or_bonjour/comment_1_71cfedf4328eab224c7fb797c420ad0a._comment b/doc/bugs/Resolve_.local_adresses_using_avahi_or_bonjour/comment_1_71cfedf4328eab224c7fb797c420ad0a._comment new file mode 100644 index 0000000000..17fae5a3b1 --- /dev/null +++ b/doc/bugs/Resolve_.local_adresses_using_avahi_or_bonjour/comment_1_71cfedf4328eab224c7fb797c420ad0a._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.68" + subject="comment 1" + date="2014-01-19T22:43:10Z" + content=""" +AFAIK, this will work fine if your OS is able to resolve those addresses using its regular resolver. Works fine here. Is `libnss-mdns` installed? +"""]]