[Bug] failed to compile `NtHiM v0.1.3`

[remonsec]

Hello
I am facing this error. used this command cargo install NtHiM

[TheBinitGhimire]

Hello @remonsec,

This issue occurs, because cargo install NtHiM ignores the Cargo.lock file in NtHiM, and tries to figure out and use newer version of the dependencies defined in the Cargo.toml file.

In this case, Cargo.toml and Cargo.lock files have defined the version v3.0.0-beta.2 for clap, however cargo tries to make use of clap v3.0.10, and this newer version appears to be using the help method instead of the about method, that leads to the issue.

You can fix this issue by using the --locked flag during installation, i.e. cargo install --locked NtHiM, which will force cargo to use the version defined in Cargo.toml and Cargo.lock files.

I will start implementing the help method from the upcoming release of NtHiM, as required by the newer releases of clap.

Failure during Installation (cargo install NtHiM)

clap v3.0.10 being used!

Failure Message!

Successful Installation (cargo install --locked NtHiM)

clap v3.0.0-beta.2 being used!

Successfully Installed!

Thank you for opening up this issue!

Thanks,
@TheBinitGhimire

[TheBinitGhimire]

Hello @remonsec,

The new release of NtHiM, i.e. v0.1.4, is published now, which includes the support for the methods available in the latest version of clap, i.e. clap v3.0.10.

The guidelines I provided earlier would help you in successfully installing NtHiM v0.1.3. With this new release, the default command would work fine as well as you did. So, if you are willing to try out this new release, you shall skip the guidelines.

I hope you would try installing the latest version of NtHiM, i.e. NtHiM v0.1.4, using the same command that you used earlier, and let me know if you are still facing any issues during the installation.

Thanks,
@TheBinitGhimire

[gprime31]

I had same problem
update rust to fix

[TheBinitGhimire]

Hello @gprime31,

Thank you for providing the information that Rust/Cargo would have helped in fixing this problem too! I will mention this issue ID as well in the commit message along with #12 and #21 for the documentation update.

Thanks,
@TheBinitGhimire