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

Support "sparserevlog" feature #19

Open
2xsaiko opened this issue May 3, 2021 · 3 comments
Open

Support "sparserevlog" feature #19

2xsaiko opened this issue May 3, 2021 · 3 comments
Labels
bug Something isn't working

Comments

@2xsaiko
Copy link

2xsaiko commented May 3, 2021

Currently this doesn't seem to support the "sparserevlog" feature, so when trying to import a repository that uses it you get

thread 'main' panicked at 'could not parse requirement: UnknownRequirement("sparserevlog")', /home/saiko/.cargo/registry/src/github.com-1ecc6299db9ec823/hg-parser-0.5.0/src/lib.rs:381:41
stack backtrace:
   0: rust_begin_unwind
             at /rustc/2fd73fabe469357a12c2c974c140f67e7cdd76d0/library/std/src/panicking.rs:493:5
   1: core::panicking::panic_fmt
             at /rustc/2fd73fabe469357a12c2c974c140f67e7cdd76d0/library/core/src/panicking.rs:92:14
   2: core::option::expect_none_failed
             at /rustc/2fd73fabe469357a12c2c974c140f67e7cdd76d0/library/core/src/option.rs:1300:5
   3: hg_parser::MercurialRepository::load_requires
   4: hg_git_fast_import::single::hg2git
   5: hg_git_fast_import::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
@kilork
Copy link
Owner

kilork commented May 3, 2021

@2xsaiko Hi, I do not think it would support this feature, I almost stopped activity on this project, but my observation was, that probably you can just ignore this. Please, read more here: #11

I had feeling, I added this option for cli, but seems like not.

@kilork kilork added this to the 1.4 milestone May 3, 2021
@kilork kilork added the bug Something isn't working label May 3, 2021
@2xsaiko
Copy link
Author

2xsaiko commented May 3, 2021

Oh oops, I thought I looked at existing issues (I guess I just didn't look at closed ones). Thanks!

@kilork
Copy link
Owner

kilork commented May 4, 2021

I think probably closing previous bug was a mistake, so let's try to keep this one and really fix it.

@kilork kilork removed this from the 1.4 milestone May 10, 2024
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

No branches or pull requests

2 participants