Breaking change in v0.1.12

[stevenroose]

v0.1.12 seems to have made a breaking change:

$ cargo install cargo2junit
    Updating crates.io index
 Downloading crates ...
  Downloaded cargo2junit v0.1.12
  Installing cargo2junit v0.1.12
 Downloading crates ...
  Downloaded vte_generate_state_changes v0.1.1
  Downloaded time-macros v0.2.4
error: failed to compile `cargo2junit v0.1.12`, intermediate artifacts can be found at `/tmp/cargo-install3Oi3Lw`
Caused by:
  failed to parse manifest at `/root/.cargo/registry/src/gitpro.ttaallkk.top-1ecc6299db9ec823/time-macros-0.2.4/Cargo.toml`
Caused by:
  feature `resolver` is required
  this Cargo does not support nightly features, but if you
  switch to nightly channel you can add
  `cargo-features = ["resolver"]` to enable this feature

[stevenroose]

Hmm, it seems it's because of the time crate that is a (transitive?) dependency. So I guess you can't do much about this, maybe fix the time crate's version.

[johnterickson]

Hmm I would have thought the lockfile would pin that...

[tofay]

Hmm I would have thought the lockfile would pin that...

cargo install doesn't use the lockfile by default, you have to specify cargo install --locked for that. (I recall a discussion on Rust zulip about switching cargo install to use a lockfile by default). So presumably the OP is using cargo < 1.51 (when the new resolver stabilized) but time-macros 0.2.4 requires cargo >= 1.51.