From 6d4baa494357d414bda491f48db331f04d92bf57 Mon Sep 17 00:00:00 2001 From: anarcat Date: Sun, 18 Jul 2021 02:02:43 +0000 Subject: [PATCH 1/3] Added a comment: same problem on debian bullseye --- ...t_7_4da389b802a114dc18e0264a4df36dee._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/bugs/__34__failed_to_send_content_to_remote__34__/comment_7_4da389b802a114dc18e0264a4df36dee._comment diff --git a/doc/bugs/__34__failed_to_send_content_to_remote__34__/comment_7_4da389b802a114dc18e0264a4df36dee._comment b/doc/bugs/__34__failed_to_send_content_to_remote__34__/comment_7_4da389b802a114dc18e0264a4df36dee._comment new file mode 100644 index 0000000000..5b63548be3 --- /dev/null +++ b/doc/bugs/__34__failed_to_send_content_to_remote__34__/comment_7_4da389b802a114dc18e0264a4df36dee._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="anarcat" + avatar="http://cdn.libravatar.org/avatar/4ad594c1e13211c1ad9edb81ce5110b7" + subject="same problem on debian bullseye" + date="2021-07-18T02:02:42Z" + content=""" +I'm having the same problem with the latest git-annex from Debian bullseye (`8.20210223-2`). I have a flaky hardware clock on this computer, which NTP regularly adjusts by a few seconds (!): + + jui 17 21:56:27 curie ntpd[1042]: adjusting local clock by -2.525655s + jui 17 21:57:30 curie ntpd[1042]: adjusting local clock by -2.546923s + jui 17 22:01:51 curie ntpd[1042]: adjusting local clock by -2.537140s + +so maybe that's what's going on? i understand that having a working clock is kind of ... expected of computers nowadays (!) but maybe that could be the source of this problem... + + +"""]] From 6517d057a07f0a02e3798f9a80238fab72136d95 Mon Sep 17 00:00:00 2001 From: remyabel Date: Sun, 18 Jul 2021 04:25:29 +0000 Subject: [PATCH 2/3] --- doc/forum/using_--quiet_with_sync.mdwn | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/forum/using_--quiet_with_sync.mdwn diff --git a/doc/forum/using_--quiet_with_sync.mdwn b/doc/forum/using_--quiet_with_sync.mdwn new file mode 100644 index 0000000000..0e54f899a5 --- /dev/null +++ b/doc/forum/using_--quiet_with_sync.mdwn @@ -0,0 +1,9 @@ +When using `git annex sync --quiet --content --message="$(date +%F)"` I still get undesirable output in stderr even though it's not an error. Specifically, looks like: + +``` +>From /media/usb/backup-secrets + 4909d792..694d8203 git-annex -> usb/git-annex + 6c8e7713..9d5a7e62 master -> usb/master +``` + +I'd prefer not to use the approach of piping stdout/stderr to /dev/null because I still want errors to appear. Am I doing something wrong or is it not possible? From 99f136c2bc5c707d8da7aeb8204a876e48339554 Mon Sep 17 00:00:00 2001 From: Atemu Date: Sun, 18 Jul 2021 22:36:15 +0000 Subject: [PATCH 3/3] --- doc/forum/Drop__47__move_unused_files_older_than_x.mdwn | 1 + 1 file changed, 1 insertion(+) create mode 100644 doc/forum/Drop__47__move_unused_files_older_than_x.mdwn diff --git a/doc/forum/Drop__47__move_unused_files_older_than_x.mdwn b/doc/forum/Drop__47__move_unused_files_older_than_x.mdwn new file mode 100644 index 0000000000..b936217a9c --- /dev/null +++ b/doc/forum/Drop__47__move_unused_files_older_than_x.mdwn @@ -0,0 +1 @@ +I like to keep unused files around in case I need them but I probably won't need files from more than a month ago. Is there a way to drop or move just unused files that were last referenced >x days ago and keep the rest?