On 15/01/2018 19:38, Mark Thomas wrote: > On 15/01/18 17:39, Mark Thomas wrote: >> Hi all, >> >> The Javadoc failure in the first release build has triggered further >> issues. The code signing service had already signed 8.5.25 and it won't >> sign another file with the same version. >> >> I've tried various ways to work around this without success. >> >> Therefore I intend to do the following: >> - reinstate the original 8.0.25 tag from r1821166 >> - mark 8.5.25 as not released >> - update the version to 8.5.26 >> - re-tag >> - generate the release > > Groan. > > Looks like something has temporarily disabled the code signing service. > Probably something I have done given the timing but I can't figure out > what it might be. > > I have a support call in to Symantec. It it doesn't get resolved fairly > quickly, I'll release 8.5.26 without signing.
Yah! Our friendly Symantec (well, Digicert now) contact has got the issue fixed. I'll have the 8.5.26 RC out later today. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
