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

Release job failed at 1.25.1 #1949

Closed
suzuki-shunsuke opened this issue Mar 10, 2024 · 4 comments
Closed

Release job failed at 1.25.1 #1949

suzuki-shunsuke opened this issue Mar 10, 2024 · 4 comments

Comments

@suzuki-shunsuke
Copy link

Release jobs failed at 1.25.1.

/~https://github.com/casey/just/releases/tag/1.25.1

image

/~https://github.com/casey/just/actions/runs/8217664170/job/22473612069

error[E0425]: cannot find value `MAP_32BIT` in crate `libc`
  --> /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/nix-0.11.1/src/sys/mman.rs:53:9
   |
53 |         MAP_32BIT;
   |         ^^^^^^^^^ not found in `libc`

For more information about this error, try `rustc --explain E0425`.
error: could not compile `nix` (lib) due to 1 previous error
warning: build failed, waiting for other jobs to finish...
Error: Process completed with exit code 101.
image
@cinerea0
Copy link

This seems to be in some way a consequence of pinning ctrlc to 3.1.1 (9d6a251) since that's the one commit that separates v1.25 from v1.25.1.

@laniakea64
Copy link
Contributor

This seems to be in some way a consequence of pinning ctrlc to 3.1.1

Looks like that was done because of #1944 , which the reporter solved by using cargo install --locked just. However, --locked install of just version 1.25.0 would've used ctrlc version 3.4.2, not 3.1.1 -

just/Cargo.lock

Lines 240 to 242 in 6228ff5

[[package]]
name = "ctrlc"
version = "3.4.2"

@casey casey mentioned this issue Mar 10, 2024
@casey
Copy link
Owner

casey commented Mar 11, 2024

Okay, take two! I just published 1.25.2, which hopefully fixes this!

@casey casey closed this as completed Mar 11, 2024
@cinerea0
Copy link

I can confirm that the issue is fixed in 1.25.2, at least in Void's CI.

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

4 participants