Sounds like this issue can be resolved by re-creating the tarball without changing any code, so I will rescind my -1 and keep testing.
On Fri, Jun 2, 2017 at 11:32 AM, Dave Neuman <neu...@apache.org> wrote: > Unfortunately I have to be -1 due to https://issues.apache.org/ > jira/browse/TC-365. > The source tar ball does not extract a proper directory structure. > > Thanks, > Dave > > On Thu, Jun 1, 2017 at 9:31 AM, Jeff Elsloo <jeff.els...@gmail.com> wrote: > >> I'm +1 on this. Thanks for creating the RC Eric! >> -- >> Thanks, >> Jeff >> >> >> On Thu, Jun 1, 2017 at 9:30 AM, Eric Friedrich (efriedri) >> <efrie...@cisco.com> wrote: >> > Hello All, >> > >> > I've prepared the next candidate release for incubator-trafficcontrol >> v2.0.0 (RC2) >> > >> > Changes since 1.8.0: >> > https://github.com/apache/incubator-trafficcontrol/compare/ >> RELEASE-1.8.1-RC0...RELEASE-2.0.0-RC2 >> > >> > This corresponds to git: >> > Hash: 795ea3adf2003dd27523b6b9ff4691f23d41ce30 >> > Tag: RELEASE-2.0.0-RC2 >> > >> > Which can be verified with the following: git tag -v >> RELEASE-2.0.0-RC2 >> > >> > My code signing key is available here: >> > http://pgp.mit.edu/pks/lookup?op=get&search=0xF2200BAB9AB7BDD5 >> > >> > and here: >> > https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS >> > >> > Make sure you refresh from a key server to get all relevant signatures. >> > >> > The source .tar.gz file, pgp signature (.asc signed with my key from >> > above), and md5 and sha512 checksums are provided here: >> > https://dist.apache.org/repos/dist/dev/incubator/trafficcont >> rol/2.0.0/RC2 >> > >> > >> > The vote will remain open until Tuesday, June 6, 2017. >> > >> > Thanks! >> > Eric Friedrich >> > >> > >
