Well, just in case:
Verified sha1, md5 and asc signatures for binary and source tarballs:
gpg: Signature made Mon 19 Mar 2018 03:38:42 PM EDT
gpg:                using RSA key 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D
gpg: Good signature from "Christopher L Tubbs II (Christopher) <
ctubb...@gmail.com>" [unknown]
gpg:                 aka "Christopher L Tubbs II (Developer) <
ctubb...@apache.org>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the
owner.
Primary key fingerprint: 8CC4 F8A2 B29C 2B04 0F2B  835D 6F0C DAE7 00B6 899D


On Tue, Mar 20, 2018 at 2:32 PM, Christopher <ctubb...@apache.org> wrote:

> I'm currently looking at the KerberosRenewalIT failures that seem to be
> persisting across branches. From the logs, it looks like the accumulo
> services are trying to do ticket-cache based login renewals, instead of
> keytab-based renewals. This has been a problematic test for me before, and
> as such, I've gotten into the habit of ignoring it, but since I've not been
> able to get it to work on reruns, and it fails nearly 100% of the time (if
> not 100%) for me now, I decided to take a closer look. If it is doing
> ticket-cache based renewals, that could indicate a bug in the Kerberos
> authentication, and that would probably warrant a -1 from me... but I will
> continue to investigate first.
>
> Josh, you know more about the Kerberos stuff than anyone here, so if you
> have time/interest, I wouldn't mind getting your feedback on why this test
> might be failing for me.
>
> On Mon, Mar 19, 2018 at 3:44 PM Christopher <ctubb...@apache.org> wrote:
>
> > Accumulo Developers,
> >
> > Please consider the following candidate for Accumulo 1.7.4.
> >
> > Git Commit:
> >     b2a59189108d736729432e81b3d5717000c6b891
> > Branch:
> >     1.7.4-rc1
> >
> > If this vote passes, a gpg-signed tag will be created using:
> >     git tag -f -m 'Apache Accumulo 1.7.4' -s rel/1.7.4 \
> >     b2a59189108d736729432e81b3d5717000c6b891
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/
> orgapacheaccumulo-1068
> > Source (official release artifact):
> > https://repository.apache.org/content/repositories/
> orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
> 4/accumulo-1.7.4-src.tar.gz
> > Binary:
> > https://repository.apache.org/content/repositories/
> orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
> 4/accumulo-1.7.4-bin.tar.gz
> > (Append ".sha1", ".md5", or ".asc" to download the signature/hash for a
> > given artifact.)
> >
> > All artifacts were built and staged with:
> >     mvn release:prepare && mvn release:perform
> >
> > Signing keys are available at https://www.apache.org/dist/accumulo/KEYS
> > (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
> >
> > Release notes (in progress) can be found at:
> > https://accumulo.apache.org/release/accumulo-1.7.4/
> >
> > Please vote one of:
> > [ ] +1 - I have verified and accept...
> > [ ] +0 - I have reservations, but not strong enough to vote against...
> > [ ] -1 - Because..., I do not accept...
> > ... these artifacts as the 1.7.4 release of Apache Accumulo.
> >
> > This vote will remain open until at least Thu Mar 22 20:00:00 UTC 2018
> > (Thu Mar 22 16:00:00 EDT 2018 / Thu Mar 22 13:00:00 PDT 2018).
> > Voting continues until the release manager sends an email closing the
> vote.
> >
> > Thanks!
> >
> > P.S. Hint: download the whole staging repo with
> >     wget -erobots=off -r -l inf -np -nH \
> >
> > https://repository.apache.org/content/repositories/
> orgapacheaccumulo-1068/
> >     # note the trailing slash is needed
> >
> >
>

Reply via email to