From 2e702960abf08af1a00ba1d24ebd27de97f03af8 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 27 Jul 2020 11:33:47 -0400 Subject: [PATCH] followup and close --- ..._8.20200618_but_8.20200720.1_expected.mdwn | 2 ++ ..._adbceacb2f27d3527273686fae1b68d2._comment | 20 +++++++++++++++++++ 2 files changed, 22 insertions(+) create mode 100644 doc/bugs/kite_net_OSX__47__current__47___distribution_is_8.20200618_but_8.20200720.1_expected/comment_1_adbceacb2f27d3527273686fae1b68d2._comment diff --git a/doc/bugs/kite_net_OSX__47__current__47___distribution_is_8.20200618_but_8.20200720.1_expected.mdwn b/doc/bugs/kite_net_OSX__47__current__47___distribution_is_8.20200618_but_8.20200720.1_expected.mdwn index f3d5e8ee32..538de2fad0 100644 --- a/doc/bugs/kite_net_OSX__47__current__47___distribution_is_8.20200618_but_8.20200720.1_expected.mdwn +++ b/doc/bugs/kite_net_OSX__47__current__47___distribution_is_8.20200618_but_8.20200720.1_expected.mdwn @@ -34,3 +34,5 @@ $/usr/bin/sw_vers ### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders) Still rock solid maintaining the .dmgs and .pkgs for a 67GB [Munki](https://www.munki.org) repository. + +> [[done]] --[[Joey]] diff --git a/doc/bugs/kite_net_OSX__47__current__47___distribution_is_8.20200618_but_8.20200720.1_expected/comment_1_adbceacb2f27d3527273686fae1b68d2._comment b/doc/bugs/kite_net_OSX__47__current__47___distribution_is_8.20200618_but_8.20200720.1_expected/comment_1_adbceacb2f27d3527273686fae1b68d2._comment new file mode 100644 index 0000000000..bcb5201866 --- /dev/null +++ b/doc/bugs/kite_net_OSX__47__current__47___distribution_is_8.20200618_but_8.20200720.1_expected/comment_1_adbceacb2f27d3527273686fae1b68d2._comment @@ -0,0 +1,20 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2020-07-25T16:09:17Z" + content=""" +This is a near duplicate of a bug you filed before. I'm dubious about the +value of these bug reports. As I said before: + +The build version being a little behind is not uncommon when the +autobuilder has not been keeping up for whatever reason. I generally don't +block releases on autobuilds if it's the fault of the autobuilder and not +a bug in git-annex's build process or test suite, and just ship the latest +available build. + +But maybe I'm missing something about how problimatic the build being +slightly behind until the next release is for you? + +The autobuilder has since caught up again, so the daily +build is current. +"""]]