cross-rs
shrink 0.3 milestone
Checklist
- [x] I've looked through the issues and pull requests for similar request
- [ ] This feature could be solved with a custom image (optional)
Describe your request
It's been years since a release. Much good work has been put into the cross 0.3 series. Can we please go ahead and release what we have now, with a small, more focused 0.3 release?
This matters, because many 0.2 bug reports currently advise unpinning cross. That is not a healthy pattern and is likely to suddenly break downstream systems without warning, as newer, incompatible changes publish.
We can always go back later to implement more enhancements in 0.3.1 and beyond.
Describe why this would be a good inclusion for cross
CI is still broken, that's the issue right now, need to fix the images so they actually build and test properly, then I'm alright with doing a release. I don't want to drop targets that are currently failing CI just to cut a release
Hi @Emilgardis, sorry to intrude in this issue but is there a way I can help you with your CI image issues? I would be more than happy to be of help. :smile:
@alexis-opolka thanks for the offer :) This is a public forum so you're not intruding ;)
The issues are that the failing jobs need to pass, you can find them for example here: https://github.com/cross-rs/cross/actions/runs/14270516937
Regarding CentOS targets, dpkg is a low level package management tool specific to the Aptitude Debian distributions, Ubuntu in this case. Perhaps rpm can provide the metadata it is trying to collect.
Regarding (Net)BSD, OS packages tend to die HTTP 404 after just a few years per OS version. Updating to the latest stable BSD versions tends to resolve these errors.
Regarding alternative architectures for (GNU) Linux, these tend to be resolved by setting up the relevant gcc... package. See snek for some older examples. https://github.com/mcandre/snek
The macOS (Darwin) CI/CD job was cancelled. Perhaps the next run will succeed.
Hi @mcandre ,
Thanks for the info, I already solved the issue with the CentOS build. I will see what I can do for the other issues once the CI on my fork has been completed.
N.B. For the macOS job issue, I think the target might be incorrect since the actions result given by @Emilgardis states that it was cancelled after one day, I don't think the CI for macOS needed to run one whole day.