Subject: Re: bug#53448: alacrity 0.9.0 build fails on guix 2b6af630d61dd5b16424be55088de2b079e9fbaf

From: Oleg Pykhalov <[email-masked]>
Date: Sat, 22 Jan 2022 20:18:44 +0300

Hi Andrew,

Thank you for the report.

Andrew Zhurov <[email-masked]> writes:

[…]

> phase `patch-cargo-checksums' succeeded after 40.4 seconds
> starting phase `build'
> error: failed to select a version for the requirement bitflags =
> ">=1.1.0, <1.3.0"
> candidate versions found which didn't match: 1.3.2
> location searched: directory source
> /tmp/guix-build-alacritty-0.9.0.drv-0/source/guix-vendor (which is
> replacing registry crates-io)
> required by package nix v0.22.1
>     ... which satisfies dependency nix = "^0.22.0" of package
> alacritty_terminal v0.15.0
> (/tmp/guix-build-alacritty-0.9.0.drv-0/source/alacritty_terminal)
>     ... which satisfies path dependency alacritty_terminal of package
> alacritty v0.9.0
> (/tmp/guix-build-alacritty-0.9.0.drv-0/source/alacritty)
> perhaps a crate was updated and forgotten to be re-vendored?
> error: in phase 'build': uncaught exception:
> %exception #<&invoke-error program: "cargo" arguments: ("build"
> "--release") exit-status: 101 term-signal: #f stop-signal: #f>
> phase `build' failed after 0.9 seconds
> command "cargo" "build" "--release" failed with status 101

[…]

Fixed in master since 41f41c0f220c435518c87ff6e28e45a00b23da6f (today).

Try to pull and then reconfigure.

Oleg.