setup
checks.x86_64-linux.system-manager
· build #9
· raw
1these 2 derivations will be built:2 /nix/store/3hx6175yi1scwinjwdsfj40h9srv95i5-system-manager-1.1.0.drv3 /nix/store/nq4x5v607h3l3xd1mnrndci0sza780pz-system-manager.drv4error: Cannot build '/nix/store/3hx6175yi1scwinjwdsfj40h9srv95i5-system-manager-1.1.0.drv'.5 Reason: builder failed with exit code 101.6 Output paths:7 /nix/store/frjzl3dsp9dna40443al5pzbwqrzs12m-system-manager-1.1.08 Last 18 log lines:9 > Running phase: unpackPhase10 > unpacking source archive /nix/store/aa653awhcmrlklf7ndk9y99sq9f8zqvd-source11 > source root is source12 > Executing cargoSetupPostUnpackHook13 > Finished cargoSetupPostUnpackHook14 > Running phase: patchPhase15 > Running phase: updateAutotoolsGnuConfigScriptsPhase16 > Running phase: configurePhase17 > Running phase: buildPhase18 > Executing cargoBuildHook19 > cargoBuildHook flags: -j 48 --target x86_64-unknown-linux-gnu --offline --profile release20 > error: failed to select a version for the requirement `anyhow = "^1.0.68"` (locked to 1.0.104)21 > candidate versions found which didn't match: 1.0.10222 > location searched: directory source `/build/source/vendor` (which is replacing registry `crates-io`)23 > required by package `system-manager-engine v1.1.0 (/build/source/crates/system-manager-engine)`24 > note: perhaps a crate was updated and forgotten to be re-vendored?25 > note: offline mode (via `--offline`) can sometimes cause surprising resolution failures26 > help: if this error is too confusing you may wish to retry without `--offline`27 For full logs, run:28 nix log /nix/store/3hx6175yi1scwinjwdsfj40h9srv95i5-system-manager-1.1.0.drv29error: Cannot build '/nix/store/nq4x5v607h3l3xd1mnrndci0sza780pz-system-manager.drv'.30 Reason: 1 dependency failed.31 Output paths:32 /nix/store/6xh1cpakyy9bf3a1i97jhrb5skgb0yag-system-manager