[Bug 2138519] Re: [FFE] Upgrade Rust to 1.93.1

[Graham Inggs]

I don't know that it is a policy, it just seemed obvious to me

rustc-1.93 seems to be migrating, and right now it seems to be in limbo;
removed from -proposed, but not yet published in the release

$ rmadison rustc-1.92
 rustc-1.92 | 1.92.0+dfsg-0ubuntu1 | resolute | source, amd64, amd64v3, arm64, armhf, i386, ppc64el, riscv64, s390x

$ rmadison rustc-1.93

Feel free to upload rust-defaults once rustc-1.93 appears in the release
pocket

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to rust-defaults in Ubuntu.
https://bugs.launchpad.net/bugs/2138519

Title:
  [FFE] Upgrade Rust to 1.93.1

Status in rust-defaults package in Ubuntu:
  Triaged

Bug description:
  ## FFE ##
  =========
  Rationale
  =========
  The toolchain team committed to making 1.93 the default Rust version
  for 26.04. Apart from giving users access to the most up-to-date Rust
  toolchain available, there are also the following notable changes
  specific to the Ubuntu package:
  - 1.93 ships a new binary package, rust-miri, which allows packagers to
    integrate undefined behaviour checks into their package tests.
  - 1.93 includes optional cargo-auditable functionality, which allows
    Rust packagers to opt in to generating SBOMs embedded into the
    distributed binaries.

  This change is expected to have minimal disruption on the distro itself,
  as the jump from 1.92 to 1.93 is small compared to the previous jump of
  1.88 to 1.92. The main reason for this FFe in the first place is the
  inclusion of opt-in-only features that don't affect normal toolchain
  behaviour.

  ================
  Proposed Changes
  ================
  - rust-defaults now points to rustc-1.93 instead of rustc-1.92, meaning
    that future Rust package builds will use Rust 1.93 instead of 1.92.
    * The upstream Rust team maintains a strict policy of backwards
      compatibility, meaning that any future rebuilds of packages are
      expected to work without issue.
    * Since Rust applications are statically linked, updating the default
      toolchain version won't trigger any rebuilds. It will only affect
      subsequent builds of Rust packages.
  - The rust-miri binary package has been added.
    * This is a purely additive addition; none of the other binary
      packages are affected in any way.
    * Usage of miri itself is unstable and the binary package is new, but
      since it is separate from the other packages and entirely optional,
      regression potential is minimal.

  ================
  seeded-in-ubuntu
  ================
  $ seeded-in-ubuntu rust-defaults
  cargo-doc (from rust-defaults) is seeded in:
    ubuntu-budgie: supported
  libstd-rust-dev (from rust-defaults) is seeded in:
    ubuntu-budgie: supported
    ubuntu: supported
  rust-doc (from rust-defaults) is seeded in:
    ubuntu-budgie: supported

  ==========
  PPA builds
  ==========
  This package builds for all architectures in a PPA:
  https://launchpad.net/~maxgmr/+archive/ubuntu/rust-defaults-1.93/+packages

  ============
  autopkgtests
  ============
  amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-resolute-maxgmr-rust-defaults-1.93/resolute/amd64/r/rust-defaults/20260317_225656_016c2@/log.gz
  arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-resolute-maxgmr-rust-defaults-1.93/resolute/arm64/r/rust-defaults/20260317_230551_a90b0@/log.gz
  armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-resolute-maxgmr-rust-defaults-1.93/resolute/armhf/r/rust-defaults/20260317_224824_504b1@/log.gz
  ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-resolute-maxgmr-rust-defaults-1.93/resolute/ppc64el/r/rust-defaults/20260317_230134_597bc@/log.gz
  s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-resolute-maxgmr-rust-defaults-1.93/resolute/s390x/r/rust-defaults/20260317_224845_f1a1b@/log.gz

  =======
  Lintian
  =======
  $ lintian
  [empty output; no warnings or errors]

  ==============================
  Installation and local testing
  ==============================
  (after enabling proposed)
  root at r:~# add-apt-repository -y ppa:maxgmr/rust-defaults-1.93
  [...]
  root at r:~# apt install cargo
  [...]
  root at r:~# cargo --version
  cargo 1.93.1 (083ac5135 2025-12-15) (built from a source tarball)
  root at r:~# cargo new hello && cd hello
      Creating binary (application) `hello` package
  note: see more `Cargo.toml` keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
  root at r:~/hello# cargo-unstable-miri run
  warning: invoking version-pinned Miri; this breaks Rust's usual stability guarantees
  warning: report issues to the package maintainers, not the upstream developers
  Preparing a sysroot for Miri (target: x86_64-unknown-linux-gnu)... done
     Compiling hello v0.1.0 (/root/hello)
      Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.14s
       Running `/usr/lib/rust-1.93/bin/cargo-miri runner target/miri/x86_64-unknown-linux-gnu/debug/hello`
  Hello, world!
  root at r:~/hello# cargo run
     Compiling hello v0.1.0 (/root/hello)
      Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.22s
       Running `target/debug/hello`
  Hello, world!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rust-defaults/+bug/2138519/+subscriptions