Backports release 1.6.0 #40150
Backports release 1.6.0 #40150
Conversation
|
@nanosoldier |
|
Your package evaluation job has completed - possible new issues were detected. A full report can be found here. cc @maleadt |
|
@nanosoldier |
|
Your package evaluation job has completed - possible new issues were detected. A full report can be found here. cc @maleadt |
(cherry picked from commit 7d117dc)
This commit reorders a couple touches in deps/pcre.mkl. Those touches are intended to prevent patch application from triggering rebuild/reconf. The present ordering doesn't quite succeed in that objective; patch application triggers rebuild. On systems with compatible autotools, the rebuild succeeds and the build is nonetheless happy. On systems with incompatible versions of autotools, however, the build fails for need of a reconf. The reordering in this commit prevents the rebuild. Co-Authored-By: Rob Vermaas <rob.vermaas@gmail.com> (cherry picked from commit 068420b)
(cherry picked from commit ec78ac7)
KristofferC
force-pushed
the
backports-release-1.6
branch
from
acc7086
to
60e70d8
Compare
(cherry picked from commit cc639ec)
|
@nanosoldier |
|
Your package evaluation job has completed - possible new issues were detected. A full report can be found here. cc @maleadt |
|
It would be nice to have #40161, since it fixes |
|
That's not even merged and I don't think we should put a PR straight into 1.6.0 so close to the end of the release process. At least not something that has to do with credential handling. Imo, we can try get a slightly quicker 1.6.1 out and then that has time to get tested a bit on master. Just my opinion. |
|
Sure, makes sense. |
Backported PRs:
Non-merged PRs with backport label:
Workerstruct thread-safe. #38405 - Make Distributed.jlWorkerstruct thread-safe.