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

panic failure with "could not parse requirement: ... share-safe" #27

Closed
markgalassi opened this issue Jul 9, 2022 · 2 comments · Fixed by #32
Closed

panic failure with "could not parse requirement: ... share-safe" #27

markgalassi opened this issue Jul 9, 2022 · 2 comments · Fixed by #32
Assignees

Comments

@markgalassi
Copy link

markgalassi commented Jul 9, 2022

I'm getting the error:

thread 'main' panicked at 'could not parse requirement: UnknownRequirement("share-safe")', /home/markgalassi/.cargo/registry/src/github.jparrowsec.cn-1ecc6299db9ec823/hg-parser-0.6.0/src/lib.rs:381:41

when I operate on fresh repos cloned from sourceforge. If I operate on the same repo that I cloned a year ago, I have no problem.

To reproduce:

hg clone http://hg.code.sf.net/p/math-science-working-groups/code math-science-working-groups
# [... output ...]
hg-git-fast-import single math-science-working-groups > math-science-working-groups.git_bare

thread 'main' panicked at 'could not parse requirement: UnknownRequirement("share-safe")', /home/markgalassi/.cargo/registry/src/github.jparrowsec.cn-1ecc6299db9ec823/hg-parser-0.6.0/src/lib.rs:381:41
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
@kilork
Copy link
Owner

kilork commented Jul 9, 2022

Usually you can safely remove this requirement from file you mentioned on stackoverflow :) I think mercurial is for long time has large part of it implemented in Rust. Just the license they have a kind of poisonous. Would not close this bug, but do not think you should expect quick solution.

@kilork
Copy link
Owner

kilork commented Oct 1, 2024

As kilork/hg-parser#4 is implemented (with no real changes actually) this could be also fixed. I am going to bump dep to version, which supports the share-safe requirement and also add another option to allow to ignore unknown requirements.

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