Closed heiher closed 1 year ago
If our version requirements are compatible with LoongArch but local development of env_logger
isn't due to an older lock file, does it matter?
This issue was discovered during our automated building of packages from the crates.io source. It appears that even if env_logger
's dependencies are not updated, it does not affect a project's ability to lock onto compatible version. However, it would be preferable if env_logger
could compile successfully as well.
However, it would be preferable if env_logger could compile successfully as well.
Why?
Thanks for your response. I believe that by doing so, we can avoid encountering this issue again in future automation testing. If you find this unacceptable, please ignore my request.
In my case, this changes a direct dependency and I try to have the lock file and manfiest in-sync with each other for direct dependencies and I try to avoid bumping direct dependencies unless there is a needed feature or a new version out.
In light of that, I think I'll close this.
This PR aims to fix a compile issue for LoongArch by updating
linux-raw-sys
.