Created attachment 557548 [details] emerge --info Annoyingly, I didn't enable Portage build logs, and my box locked up after I had fixed the issue but before I took a capture of stdout logs, so I don't have the precise errors available. At a high level, Cargo was failing because Alacritty was using tool lints against "clippy", and apparently tool lints are a Beta feature in 1.29.1. Tool lints appear to have become stable in rust-1.31 (https://github.com/rust-lang/rust/pull/54870) and, indeed, Alacritty builds fine against rust-1.31.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=35878b063a0401f5c5b7ff4b64a2dd67c29bf875 commit 35878b063a0401f5c5b7ff4b64a2dd67c29bf875 Author: Georgy Yakovlev <gyakovlev@gentoo.org> AuthorDate: 2018-12-11 05:08:10 +0000 Commit: Georgy Yakovlev <gyakovlev@gentoo.org> CommitDate: 2018-12-11 05:08:10 +0000 x11-terms/alacritty: rust-1.31.0 is required for 0.2.4 Closes: https://bugs.gentoo.org/672896 Package-Manager: Portage-2.3.52, Repoman-2.3.12 Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org> x11-terms/alacritty/alacritty-0.2.4.ebuild | 1 + 1 file changed, 1 insertion(+)
thanks, fixed.
Thank you!