Yup. It's _only_ a problem on the actual release tarball. You don't
need that file if you're checking out from git. That's why none of the
tools caught it, but Dave did. He was testing against the proposed
release.
On Fri, Feb 21, 2020 at 3:12 PM Rawlin Peters wrote:
>
> Oh, it's probably just
Oh, it's probably just an artifact from building the tarball -- the
asf-ci build job checks out 4.0.x in git and builds from there.
- Rawlin
On Fri, Feb 21, 2020 at 3:08 PM Rawlin Peters wrote:
>
> That's strange, because the asf-ci build job for 4.0.x doesn't have
> any weasel issues:
>
That's strange, because the asf-ci build job for 4.0.x doesn't have
any weasel issues:
https://builds.apache.org/view/S-Z/view/TrafficControl/job/trafficcontrol-4.0.x-build/18/artifact/dist/weasel.txt
- Rawlin
On Fri, Feb 21, 2020 at 3:00 PM Chris Lemmons wrote:
>
> The weasel is reporting that
The weasel is reporting that BUILD_NUMBER does not have a license
header and it's not declared with a license in the dependency_license
file. Since BUILD_NUMBER is very small and not code, it can survive
without the header. I've opened up a fix here:
+1
I verified that sha512sum and signature. I was able to build all of the
components, but weasel failed for some reason. Since it's not critical to
running a CDN, I won't let that hold us up.
On Tue, Feb 11, 2020 at 9:42 AM Rawlin Peters wrote:
> Hello All,
>
> I've prepared a release for
+1
I think community silence on this means tacit approval on the basis of
"yeah, that's fine idc"
On Wed, Feb 19, 2020 at 3:43 PM Jeremy Mitchell
wrote:
> Looks good to me. I added one comment to the gist, otherwise, thanks for
> putting this together. Wow, we're actually going to see an API
