From: anarcat Date: Sun, 18 Jul 2021 02:02:43 +0000 (+0000) Subject: Added a comment: same problem on debian bullseye X-Git-Tag: archive/raspbian/10.20250416-2+rpi1~2^2^2~69^2~54^2~2 X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=6d4baa494357d414bda491f48db331f04d92bf57;p=git-annex.git Added a comment: same problem on debian bullseye --- 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... + + +"""]]