mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions 1

followup and close

Browse source
This commit is contained in:
Joey Hess 2020-07-27 11:33:47 -04:00
commit 2e702960ab
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 22 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

2
doc/bugs/kite_net_OSX__47__current__47___distribution_is_8.20200618_but_8.20200720.1_expected.mdwn
View file

@ -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]]

20
doc/bugs/kite_net_OSX__47__current__47___distribution_is_8.20200618_but_8.20200720.1_expected/comment_1_adbceacb2f27d3527273686fae1b68d2._comment Normal file
View file

@ -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.
"""]]