New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v0.4.21 patch upgrade breaks SGX builds #770
Comments
This release also introduces a cyclic dependency. The following in Cargo.toml is sufficient to reproduce:
|
Thanks for the report @nhynes and @rdeaton - and apologies for the breakage. It looks like we have a few options here:
|
Sorry for the regression! It seems like 0.4.20 would also be broken on SGX, and I don't think we're going to yank both -- and I'm guessing the audience for whom 0.4.21 improves things is much larger than the audience for whom it makes things worse. In this case I think we should just get a 0.4.22 out as soon as possible. |
We are now at 0.4.26, this can be closed? |
chrono v0.4.21
introduces a new default featureclock
which transitively pulls iniana-time-zone
, which doesn't build on SGX. This PATCH version upgrade has caused a sever-incompatible change on the SGX target (and others for which iana-time-zone doesn't work).I would suggest:
Until then, essentially all users of the SGX target via core crates such as mbedtls will need to carefully manage lockfiles, which isn't super fun.
#767 thankfully fixes the problem. Hopefully the new patch version gets through okay.
The text was updated successfully, but these errors were encountered: