Hi Folks,
      
      An update:   After lots of fussing, it seems that the R-HEAD build
      began failing on scp because Markus' shell account was accidently
      disabled [1].
      
      Now that that's fixed, we are back to the R-HEAD build failing
      because of the original problem...i.e. an SHA-256 digest error
      like this:
      
      Waiting for jobs to end
      
      org.eclipse.core.runtime.CoreException:
      java.lang.SecurityException: SHA-256 digest error for
      org/apache/http/client/cache/HttpCacheEntry.class
      
          at
org.eclipse.buckminster.runtime.BuckminsterException.fromMessage(BuckminsterException.java:57)
          at
org.eclipse.buckminster.runtime.BuckminsterException.wrap(BuckminsterException.java:123)
          at
org.eclipse.buckminster.core.actor.AbstractActor.perform(AbstractActor.java:205)
          at
org.eclipse.buckminster.core.internal.actor.PerformManager$DirectActionInvocation.execute(PerformManager.java:143)
          at
org.eclipse.buckminster.core.internal.actor.PerformManager.internalPerform(PerformManager.java:454)
          at
org.eclipse.buckminster.core.internal.actor.PerformManager.perform(PerformMan
      
      
      It's our hypothesis that this is a problem with the pack200 that
      we are using (from Java *6* currently in the builder).    It's my
      hope that updating to either Java 7 or Java 8 will make this error
      go away, so we've asked the folks at OSU Open Source Lab to update
      the Java version on Jenkins to be Java 7 or Java 8 (it might need
      to be Java 7 based upon the OS that they are using there).
      
      In any event, it's my hope that this will solve the pack200 error
      that we are getting above.   It's possible that it will not, but
      I'd rather not think about that now.  :).
      
      Unfortunately, Neon M5 occurs on Feb 5 (3 days from now).   Since
      we can't contribute a build today (still Tuesday in US), it seems
      that we won't be able to contribute a new build for Neon M5.   
      
      I don't want to do this, but if this issue can't be resolved we
      will likely have to withdraw from the Neon simultaneous release. 
      That's because packed repos are required for the Simultaneous
      Release.
      
      Thanks,
      
      Scott
      
      [1] 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=486424
      
      
      On 1/24/2016 1:27 PM, Wim Jongman wrote: