[TRACKING] Updates blocked on Rust 1.65.0

[jcgruenhage]

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

New packages blocked on Rust 1.65.0

• prose (27a54bf)
• New package: cargo-semver-checks-0.19.0 #40787
• New package: fend-1.2.0 #43203
• New packages: typst, typst-lsp #43185
• New package: atuin-17.1.0 #40600

[icp1994]

rust-analyzer and qsv are two that I know of

[jcgruenhage]

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]

From the 1.64 release blog

At this time, to run the rustup-installed version, you need to invoke it this way: rustup run stable rust-analyzer
The next release of rustup will provide a built-in proxy so that running the executable rust-analyzer will launch the appropriate version.

Most users should continue to use the releases provided by the rust-analyzer team (available on the rust-analyzer releases page), which are published more frequently

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]

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]

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]

nushell

[icp1994]

pueue >= 3.0.0

[cinerea0]

bottom >= 0.7.0 requires let-else statements which were stabilized in 1.65.

[leahneukirchen]

I want to package prose but a depenency needs 1.65.

[cinerea0]

broot >= 1.19.0 requires 1.65.

[tranzystorekk]

zoxide >= 0.9.0

[cinerea0]

ouch >= 0.4.1 requires let-else statements.

[tranzystorekk]

Preliminary test on llvm15/rust 1.66.1/x86_64-glibc:

• cargo-about 0.5.2
• qsv 0.84.0
• rust-analyzer 2023.01.09
• nushell 0.74.0 (haven't yet updated system libs patch)
• pueue 3.1.1 (fails to build due to darwin-libproc: http://ix.io/4lkO)
• bottom 0.7.1
• broot 1.19.0
• zoxide 0.9.0
• cargo-deny 0.13.7
• ouch 0.4.1
• prose 0.4.0

[classabbyamp]

helvum >= 0.4.0 (let-else statements) (classabbyamp@4d1222b)

[cinerea0]

Kooha >= 2.2.3 uses let-else statements all over the place.

[tranzystorekk]

#40600 atuin >= 13.0.0, let-else statements

[cinerea0]

mdcat >= 1.1.0 requires GATs, which were stabilized in rust 1.65.

[classabbyamp]

rbw 1.6.0, let else statements

[tranzystorekk]

new package fend >= 1.1.5, let-else statements

[icp1994]

procs >= 0.14.0 [msrv 1.67]

[leahneukirchen]

I want to package typst but a dependency uses let..else.

[TinfoilSubmarine]

vaultwarden-1.28.0 needs argon2 v0.5.0 which requires rustc >= 1.65:

error: package `argon2 v0.5.0` cannot be built because it requires rustc 1.65 or newer, while the currently active rustc version is 1.64.0

[0xlua]

ncspot >= 0.12.0 uses the backtrace api which was stabilized in rust 1.65

[tranzystorekk]

helix >= 23.03, MSRV set to 1.65

[classabbyamp]

new rust merged, get em while they're fresh!