[I] If we can upgrade version of bitflags in optee-utee [incubator-teaclave-trustzone-sdk]

[via GitHub]

ivila opened a new issue, #148:
URL: https://github.com/apache/incubator-teaclave-trustzone-sdk/issues/148

   In 
[cargo.toml](https://github.com/apache/incubator-teaclave-trustzone-sdk/blob/b5143c627de2ee128732fcf798c41516ffbc13f7/optee-utee/Cargo.toml#L30)
 of optee-utee crate, it lock the version of bitflags(set it must to 1.0.4):
   
![image](https://github.com/user-attachments/assets/32147a40-4306-45b3-982c-9c51d2a7f805)
   
   However, in some other crates will require a newer version, for example, the 
[raw-cpuid](https://crates.io/crates/raw-cpuid) require version upper 1.2, and 
result in confliction:
   
![image](https://github.com/user-attachments/assets/9e2fbe33-2c4b-4efc-8748-fffb90df7256)
   So I wonder why optee-utee lock the version of bitflags and if it can 
upgrade the version of bitflags


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org
For additional commands, e-mail: dev-h...@teaclave.apache.org