Open ghost opened 10 months ago
Hi! Thanks for the inquiry! I'm not sure these issues (except #1302) would be solved on the main branch. 0.2.5
contains backports to the 0.2.4
release, as after 0.2.4
we did some breaking changes, and then discovered some things that had to be fixed with 0.2.5
.
so, the next release should be 0.3.0
, and as I've mentioned in https://github.com/cross-rs/cross/discussions/1290#discussioncomment-7388721 there's some things missing
Currently dev time is very low, as it's basically only me submitting patches, reviewing and triaging issues. I'd love to have more help :)
I'm really looking forward to a new release for #1222
Warning: using older rustc `1.67.0 (fc594f156 2023-01-24)` for the target. Current active rustc on the host is `rustc 1.75.0 (82e1608df 2023-12-21)`.
> Update with `rustup update --force-non-host stable-x86_64-unknown-linux-gnu`
error: package `clap v4.5.3` cannot be built because it requires rustc 1.74 or newer, while the currently active rustc version is 1.67.0
Either upgrade to rustc 1.74 or newer, or use
cargo update -p clap@4.5.3 --precise ver
where `ver` is the latest version of `clap` supporting rustc 1.67.0
error: Recipe `build_ksud` failed on line 5 with exit code 101
@tiann I fail to see how that is related, you just need to update the toolchain as explained in the message
rustup update --force-non-host stable-x86_64-unknown-linux-gnu
@Emilgardis Im also waiting desperately for the new release to get "docker_inspect_self_mountinfo"
I have discovered that bugs reported in the #1298, #1300, #1302, #1307, and #1344 issues are specific to version 0.2.5 of
cross
. It has come to my attention that the build from themain
branch is functioning flawlessly, which is great news.However, considering that users generally prefer the stability of a "release" (or "versioned") build over a development build, it is unfortunate that they are experiencing errors that are only present in version 0.2.5. This puts them in a difficult situation, as they are unable to benefit from the improvements and fixes introduced in the latest version.
To address this issue and ensure a smoother user experience, I suggest releasing version 0.2.6 (or something else) as soon as we could. By doing so, we can provide users with an updated version that resolves the reported bugs and offers enhanced stability. This will not only improve user satisfaction but also enable them to utilize the software without being hindered by known issues.
I kindly request the team's consideration and prompt action in releasing next version to help users overcome these errors and enjoy a more reliable software experience.