Skip to content
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

bitvec v0.22.0 depends on funty = "~1.2 which has been yanked #1283

Closed
Georges760 opened this issue Nov 18, 2022 · 3 comments · Fixed by #1284
Closed

bitvec v0.22.0 depends on funty = "~1.2 which has been yanked #1283

Georges760 opened this issue Nov 18, 2022 · 3 comments · Fixed by #1284
Labels
bug Something isn't working

Comments

@Georges760
Copy link
Contributor

Georges760 commented Nov 18, 2022

Describe the bug

funty 1.2 has been yanked, so bitvec v0.22.0 and all the current probe-rs cannot be build.

upstream issue and issue has been reported.

some workaround may have been used by others dependant project.

To Reproduce

fresh cargo build from probe-rs directory

Expected behavior

build OK

Stacktrace

Desktop (please complete the following information):

Linux Ubuntu

Additional context

@Georges760 Georges760 added the bug Something isn't working label Nov 18, 2022
@Tiwalun
Copy link
Member

Tiwalun commented Nov 18, 2022

Seems to work fine for me. Could you please post the exact error message you get when trying to build?

@noppej
Copy link
Contributor

noppej commented Nov 18, 2022

The link posted in the OP says this ...

"This crate has been yanked, but it is still available for download for other crates that may be depending on it."

@Tiwalun
Copy link
Member

Tiwalun commented Nov 18, 2022

The issue seems to be itm-decode in our case, which depends on the old bitvec version, which in itself depends on funty. There seems to be a new version in https://github.com/rtic-scope/itm, but that's not on crates.io yet unfortunately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants