On 06/13/2017 08:30 AM, Kevin Kane via iotivity-dev wrote: > We've explored splitting the patch into multiple chunks before, and decided > it was a bad idea. The only value it appears to add is making the patch files > more human-readable, but it complicates the process to create or update the > patch files in order to make a change or update mbedTLS, and then adds more > patch apply steps to the build. This has already been an unreliable build > step and I oppose making it moreso. > > Our intention was always that these patches would eventually be taken by the > upstream, and our additions to ocf.patch would eventually be taken back out > as part of updating to a newer version of mbedTLS with our additions. We > didn't expect it'd be this difficult to get any attention to our pull > requests!
What we have now, after the patch (5456220c850bd580b9bafdb82c356e9fb9c34f02), seems to be back to as good as before... except on the Mac builder, which is not automatically pulling the new revision... not sure how this happens, hopefully someone can kick it. 07:08:30 *********************************** Error: ************************************ 07:08:30 * Your mbedTLS repo is not up to date with the version required by iotivity. 07:08:30 * Please update with the following commands: 07:08:30 * $ cd extlibs/mbedtls/mbedtls 07:08:30 * $ git fetch 07:08:30 ******************************************************************************* The other builders got past this point, so something in the scripts driving the process on jenkins is different here?
