Repository navigation
[TRACKING] Updates blocked on Rust 1.65.0 #40805
Description
We can't update to Rust 1.65.0 yet, because that requires LLVM >= 13 (see #40821), which in turn is waiting for a GCC update (see #34902, #39809, #39960).
Updates blocked on Rust 1.65.0
- cargo-about: update to 0.5.5. #43179
- qsv: update to 0.99.0. #43244
- rust-analyzer: update to 2023.03.27. #43219
- nushell: update to 0.78.0. #43188
- pueue: update to 3.1.2 #43217
- bottom: update to 0.8.0. #43212
- broot: update to 1.23.0 #43223
- zoxide: update to 0.9.0 #43175
- cargo-deny: update to 0.13.7. #43181
- ouch: update to 0.4.1. #43200
- helvum: update to 0.4.0, orphan. #43173
- mdcat: update to 1.1.1 #43218
- rbw: update to 1.7.1. #43177
- procs: update to 0.14.0 #43213
- vaultwarden: update to 1.28.1. #43240
Activity
icp1994 commentedon Nov 27, 2022
rust-analyzer and qsv are two that I know of
jcgruenhage commentedon Nov 27, 2022
Isn't rust-analyzer shipped by rustup though? Not sure whether it makes sense to ship that separately. We removed rustfmt back when it started being shipped by rustup, although that had additional reasons related to requiring nightly iirc.
icp1994 commentedon Nov 27, 2022
From the 1.64 release blog
Not exactly sure what should be done regarding the RA package after the next rustup update but okay maybe it can left from the list for now.
jcgruenhage commentedon Nov 27, 2022
Ah, okay, so we still need rust-analyzer until we get a new rustup release at least.. In that case, I think we should add it to the list here.
0x5c commentedon Nov 27, 2022
Unless we mark the rust toolchain packages as "for package building only", there will be people using the rust toolchain bits we ship instead of whatever they'd otherwise download through rustup.
The current setup allows all the toolchain to be installed through xbps without rustup involvement, no mix needed. People using packaged rust with rustup-downloaded r-a won't even get the same version unless they specifically ensure they keep the packaged rust and rustup r-a in version sync.
I don't personally use packaged rust outside of when packaging other things, and I'm not sure using packaged rust is good for development purposes, but such is the current state of what we ship.
icp1994 commentedon Nov 30, 2022
nushell
icp1994 commentedon Dec 13, 2022
pueue >= 3.0.0
cinerea0 commentedon Jan 2, 2023
bottom >= 0.7.0 requires let-else statements which were stabilized in 1.65.
leahneukirchen commentedon Jan 2, 2023
I want to package prose but a depenency needs 1.65.
cinerea0 commentedon Jan 4, 2023
broot >= 1.19.0 requires 1.65.
tranzystorekk commentedon Jan 8, 2023
zoxide>= 0.9.0cinerea0 commentedon Jan 15, 2023
ouch >= 0.4.1 requires let-else statements.
tranzystorekk commentedon Jan 15, 2023
Preliminary test on llvm15/rust 1.66.1/x86_64-glibc:
0.5.20.84.02023.01.090.74.0(haven't yet updated system libs patch)3.1.1(fails to build due to darwin-libproc: http://ix.io/4lkO)0.7.11.19.00.9.00.13.70.4.10.4.0classabbyamp commentedon Feb 17, 2023
helvum >= 0.4.0 (let-else statements) (classabbyamp@4d1222b)
cinerea0 commentedon Feb 24, 2023
Kooha >= 2.2.3 uses let-else statements all over the place.
tranzystorekk commentedon Feb 26, 2023
#40600 atuin >= 13.0.0, let-else statements
cinerea0 commentedon Feb 28, 2023
mdcat >= 1.1.0 requires GATs, which were stabilized in rust 1.65.
classabbyamp commentedon Mar 12, 2023
rbw 1.6.0, let else statements
tranzystorekk commentedon Mar 14, 2023
new package fend >= 1.1.5, let-else statements
icp1994 commentedon Mar 15, 2023
procs >= 0.14.0 [msrv 1.67]
leahneukirchen commentedon Mar 22, 2023
I want to package typst but a dependency uses let..else.
TinfoilSubmarine commentedon Mar 26, 2023
vaultwarden-1.28.0needsargon2 v0.5.0which requires rustc >= 1.65:0xlua commentedon Mar 30, 2023
ncspot >= 0.12.0 uses the backtrace api which was stabilized in rust 1.65
tranzystorekk commentedon Mar 31, 2023
helix >= 23.03, MSRV set to 1.65
classabbyamp commentedon Apr 2, 2023
new rust merged, get em while they're fresh!