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

Installing gitoxide@0.36.0 via cargo install not possible because the zip crate in the specified verision is yanked #1378

Closed
kamulos opened this issue May 25, 2024 · 1 comment · Fixed by #1379
Labels
acknowledged an issue is accepted as shortcoming to be fixed

Comments

@kamulos
Copy link

kamulos commented May 25, 2024

Current behavior 😯

As the title says: a cargo install gitoxide --force does not work because the zip crate is yanked.

This is the output:

Caused by:
  failed to select a version for the requirement `zip = "^1.3.1"`
  candidate versions found which didn't match: 2.1.0, 2.0.0, 1.1.4, ...
  location searched: crates.io index
  required by package `gix-archive v0.13.0`
      ... which satisfies dependency `gix-archive-for-configuration-only = "^0.13.0"` of package `gitoxide-core v0.38.0`
      ... which satisfies dependency `gitoxide-core = "^0.38.0"` of package `gitoxide v0.36.0`
  if you are looking for the prerelease package it needs to be specified explicitly
      zip = { version = "0.10.0-alpha.1" }
  perhaps a crate was updated and forgotten to be re-vendored?

Expected behavior 🤔

No response

Git behavior

No response

Steps to reproduce 🕹

No response

@Byron Byron added the acknowledged an issue is accepted as shortcoming to be fixed label May 25, 2024
@Byron Byron linked a pull request May 25, 2024 that will close this issue
@Byron
Copy link
Member

Byron commented May 25, 2024

Thanks for reporting, a fix is in the works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
acknowledged an issue is accepted as shortcoming to be fixed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants