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

issue with build using env_logger = "0.11.0" #1898

Closed
jhheider opened this issue Feb 11, 2024 · 5 comments
Closed

issue with build using env_logger = "0.11.0" #1898

jhheider opened this issue Feb 11, 2024 · 5 comments

Comments

@jhheider
Copy link

jhheider commented Feb 11, 2024

changed in a2ff42e

building with rust 1.76/cargo 0.65 (or 0.66) give the following:

cargo install --path=. --root=/opt/just.systems/v1.24.0+brewing
  Installing just v1.24.0 (/__w/pantry/pantry/builds/just.systems-1.24.0)
    Updating crates.io index
error: failed to compile `just v1.24.0 (/__w/pantry/pantry/builds/just.systems-1.24.0)`, intermediate artifacts can be found at `/__w/pantry/pantry/builds/just.systems-1.24.0/target`

Caused by:
  failed to select a version for `env_logger`.
      ... required by package `just v1.24.0 (/__w/pantry/pantry/builds/just.systems-1.24.0)`
  versions that meet the requirements `^0.11.0` are: 0.11.1, 0.11.0

  the package `just` depends on `env_logger`, with features: `anstream` but `env_logger` does not have these features.
   It has an optional dependency with that name, but that dependency uses the "dep:" syntax in the features table, so it does not have an implicit feature with that name.


  failed to select a version for `env_logger` which could resolve this conflict

reverting the version of env_logger to "0.10.0" fixes the build.

failed build: https://github.com/pkgxdev/pantry/actions/runs/7864327681/job/21455948535
successful build: https://github.com/pkgxdev/pantry/actions/runs/7864885532

jhheider added a commit to pkgxdev/pantry that referenced this issue Feb 11, 2024
@casey
Copy link
Owner

casey commented Feb 11, 2024

I tried to reproduce this with cargo install --path ., and it seems to have worked. Is there something else which might be contributing to the issue?

@jhheider
Copy link
Author

it's certainly always possible. this was rust 1.76 and cargo 0.66 and 0.65. i can't tell which rust/cargo versions are running in your CD without breaking out rustup, but what versions are you running locally that work?

it almost has to be cargo, since it's failing during package resolution.

@jhheider
Copy link
Author

oh, wait. no, cargo is up to 0.77. i bet it's cargo version. let me test a few more.

@jhheider
Copy link
Author

yup, old cargo versions. apologies for the noise!

@casey
Copy link
Owner

casey commented Feb 11, 2024

Awesome, no worries, glad it works!

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

No branches or pull requests

2 participants