GNU bug report logs - #62818
rust-analyzer broken after rustc got bumped

Previous Next

Package: guix;

Reported by: Steven Roose <steven <at> roose.io>

Date: Thu, 13 Apr 2023 18:36:02 UTC

Severity: normal

To reply to this bug, email your comments to 62818 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#62818; Package guix. (Thu, 13 Apr 2023 18:36:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Steven Roose <steven <at> roose.io>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Thu, 13 Apr 2023 18:36:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Steven Roose <steven <at> roose.io>
To: bug-guix <at> gnu.org
Subject: rust-analyzer broken after rustc got bumped
Date: Thu, 13 Apr 2023 19:35:20 +0100
The Guix version of rust-analyzer that is in rust-apps.scm is somehow 
dependent on rustc 1.60.0 and seems to use it internally to do 
compilation and checks.


Guix recently published rustc v1.65.0 to the repo and after pulling that 
in, many compilations fail with some very strange error message "this 
crate is not compiled for the right Rust version, please recompile with 
version 1.60".

One possible workaround would probably be to instruct rust-analyzer to 
use a different directory to store its artefacts, but that would mean 
building everything twice and keeping two sets of build artifacts which 
can become quite sizable.


It seems that either rust-analyzer should be make 
rustc-version-independent, no idea how that would work, or rust-analyzer 
should be updated alongside rustc whenever possible.





This bug report was last modified 1 year and 6 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.