these 2 derivations will be built:
  /nix/store/3hx6175yi1scwinjwdsfj40h9srv95i5-system-manager-1.1.0.drv
  /nix/store/nq4x5v607h3l3xd1mnrndci0sza780pz-system-manager.drv
building '/nix/store/3hx6175yi1scwinjwdsfj40h9srv95i5-system-manager-1.1.0.drv'
system-manager-1.1.0> Running phase: unpackPhase
system-manager-1.1.0> unpacking source archive /nix/store/aa653awhcmrlklf7ndk9y99sq9f8zqvd-source
system-manager-1.1.0> source root is source
system-manager-1.1.0> Executing cargoSetupPostUnpackHook
system-manager-1.1.0> Finished cargoSetupPostUnpackHook
system-manager-1.1.0> Running phase: patchPhase
system-manager-1.1.0> Running phase: updateAutotoolsGnuConfigScriptsPhase
system-manager-1.1.0> Running phase: configurePhase
system-manager-1.1.0> Running phase: buildPhase
system-manager-1.1.0> Executing cargoBuildHook
system-manager-1.1.0> cargoBuildHook flags: -j 48 --target x86_64-unknown-linux-gnu --offline --profile release
system-manager-1.1.0> error: failed to select a version for the requirement `anyhow = "^1.0.68"` (locked to 1.0.104)
system-manager-1.1.0> candidate versions found which didn't match: 1.0.102
system-manager-1.1.0> location searched: directory source `/build/source/vendor` (which is replacing registry `crates-io`)
system-manager-1.1.0> required by package `system-manager-engine v1.1.0 (/build/source/crates/system-manager-engine)`
system-manager-1.1.0> note: perhaps a crate was updated and forgotten to be re-vendored?
system-manager-1.1.0> note: offline mode (via `--offline`) can sometimes cause surprising resolution failures
system-manager-1.1.0> help: if this error is too confusing you may wish to retry without `--offline`
error: Cannot build '/nix/store/3hx6175yi1scwinjwdsfj40h9srv95i5-system-manager-1.1.0.drv'.
       Reason: builder failed with exit code 101.
       Output paths:
         /nix/store/frjzl3dsp9dna40443al5pzbwqrzs12m-system-manager-1.1.0
       Last 18 log lines:
       > Running phase: unpackPhase
       > unpacking source archive /nix/store/aa653awhcmrlklf7ndk9y99sq9f8zqvd-source
       > source root is source
       > Executing cargoSetupPostUnpackHook
       > Finished cargoSetupPostUnpackHook
       > Running phase: patchPhase
       > Running phase: updateAutotoolsGnuConfigScriptsPhase
       > Running phase: configurePhase
       > Running phase: buildPhase
       > Executing cargoBuildHook
       > cargoBuildHook flags: -j 48 --target x86_64-unknown-linux-gnu --offline --profile release
       > error: failed to select a version for the requirement `anyhow = "^1.0.68"` (locked to 1.0.104)
       > candidate versions found which didn't match: 1.0.102
       > location searched: directory source `/build/source/vendor` (which is replacing registry `crates-io`)
       > required by package `system-manager-engine v1.1.0 (/build/source/crates/system-manager-engine)`
       > note: perhaps a crate was updated and forgotten to be re-vendored?
       > note: offline mode (via `--offline`) can sometimes cause surprising resolution failures
       > help: if this error is too confusing you may wish to retry without `--offline`
       For full logs, run:
         nix log /nix/store/3hx6175yi1scwinjwdsfj40h9srv95i5-system-manager-1.1.0.drv
error: Cannot build '/nix/store/nq4x5v607h3l3xd1mnrndci0sza780pz-system-manager.drv'.
       Reason: 1 dependency failed.
       Output paths:
         /nix/store/6xh1cpakyy9bf3a1i97jhrb5skgb0yag-system-manager