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

Deno installation failing via cargo-binstall #1638

Open
nth10sd opened this issue Mar 3, 2024 · 5 comments
Open

Deno installation failing via cargo-binstall #1638

nth10sd opened this issue Mar 3, 2024 · 5 comments

Comments

@nth10sd
Copy link

nth10sd commented Mar 3, 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?

See also this deno issue, they say to file here instead.

@NobodyXu
Copy link
Member

NobodyXu commented Mar 3, 2024

Thanks, I would investigate this

@wiiznokes
Copy link

I've got the same problem since i added a bin target to my project

@cosmoswafer
Copy link

Since binstall will fall back to using quickinstall source, the Deno binary can be installed now.

@nth10sd
Copy link
Author

nth10sd commented Nov 2, 2024

I still get:

$ cargo binstall -y --locked deno
 INFO resolve: Resolving package: 'deno'
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.

Although it then proceeds to compile successfully (deno version 2.0.4).

@NobodyXu
Copy link
Member

NobodyXu commented Nov 3, 2024

Thanks for update!

So the other binary is stored separately , this would require some change in the resolver.

I'm happy to add support for this, but it would take some time to work on this.

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

No branches or pull requests

4 participants