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

Using cargo binstall to install deno results in an error (denort-related) in 1.40.5 #22490

Closed
nth10sd opened this issue Feb 20, 2024 · 2 comments
Labels
help wanted community help requested

Comments

@nth10sd
Copy link

nth10sd commented Feb 20, 2024

Using cargo binstall to get deno now results in the following error:

ERROR resolve: When resolving deno bin denort is not found. This binary is not optional so it must be included in the archive, please contact with upstream to fix this issue.

Prior to 1.40.5, it seemed to work fine. Is this method no longer supported?

@dsherret dsherret added the bug Something isn't working correctly label Feb 20, 2024
@littledivy
Copy link
Member

cargo-binstall is likely not able to detect that denort is distributed as a seperate zip artifact in the releases. We don't want to ship it by default.

Please open an issue with https://github.com/cargo-bins/cargo-binstall, I don't think Deno can solve it without shipping denort in the same artifact or adding extra feature flags.

@littledivy littledivy added unactionable help wanted community help requested and removed bug Something isn't working correctly labels Mar 3, 2024
@littledivy littledivy removed their assignment Mar 3, 2024
@nth10sd
Copy link
Author

nth10sd commented Mar 3, 2024

I filed on their issues page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted community help requested
Projects
None yet
Development

No branches or pull requests

4 participants