** Changed in: rustc-1.82 (Ubuntu Noble)
Status: Confirmed => In Progress
** Changed in: rustc-1.82 (Ubuntu Jammy)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Links---
All packages built successfully in a PPA here:
https://launchpad.net/~maxgmr/+archive/ubuntu/rustc-1.85-merge/+packages
The source code can be found here:
https://git.launchpad.net/~canonical-foundations/ubuntu/+source/rustc/tree/?h=merge-1.85
Finally, the commit history can
** Changed in: rustc-1.82 (Ubuntu Focal)
Status: Confirmed => Won't Fix
** Changed in: rustc-1.82 (Ubuntu Oracular)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
** Changed in: rust-defaults (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2109761
Title:
Upgrade Rust to 1.85.1
To manage notifications about this bug go
Since Focal is now ESM only, I've removed the Focal backport from the
list of affected series.
** No longer affects: rustc-1.81 (Ubuntu Focal)
** Changed in: rustc-1.81 (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
B
** Changed in: rustc-1.81 (Ubuntu Noble)
Status: New => In Progress
** Changed in: rustc-1.81 (Ubuntu Jammy)
Status: New => In Progress
** Changed in: rustc-1.81 (Ubuntu Focal)
Status: New => In Progress
** Changed in: rustc-1.81 (Ubuntu)
Status: New => In Progress
-
** Description changed:
Rust 1.85 was released on 20 February 2025 and patched on 18 March 2025.
A great deal of packages in the Ubuntu archive rely on up-to-date
versions of Rust in order to be built.
Rust 1.85 comes with some significant additions, most notably the
stabilization of
** Changed in: rustc-1.82 (Ubuntu)
Assignee: (unassigned) => Max Gilmour (maxgmr)
** Changed in: rustc-1.82 (Ubuntu Focal)
Assignee: (unassigned) => Max Gilmour (maxgmr)
** Changed in: rustc-1.82 (Ubuntu Jammy)
Assignee: (unassigned) => Max Gilmour (maxgmr)
** Changed
)
Assignee: (unassigned) => Max Gilmour (maxgmr)
** Changed in: rustc-1.81 (Ubuntu Focal)
Assignee: (unassigned) => Max Gilmour (maxgmr)
** Changed in: rustc-1.81 (Ubuntu Jammy)
Assignee: (unassigned) => Max Gilmour (maxgmr)
** Changed in: rustc-1.81 (Ubuntu Noble)
Public bug reported:
Older supported releases of Ubuntu are missing newer rustc versions,
leading to issues such as LP: #2100492.
To remedy this, it is necessary to backport rustc to all supported
Ubuntu releases. This shall be done by starting at the newest release
missing a particular rustc ver
** Summary changed:
- Upgrade Rust to 1.85.0
+ Upgrade Rust to 1.85.1
** Description changed:
- Rust 1.85 was released on 20 February 2025. A great deal of packages in
- the Ubuntu archive rely on up-to-date versions of Rust in order to be
- built.
+ Rust 1.85 was released on 20 February 2025 an
-defaults (Ubuntu)
Importance: Undecided
Assignee: Max Gilmour (maxgmr)
Status: New
** Tags: questing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2109761
Title:
Upgrade Rust to
Public bug reported:
The `rust-lldb` binary package cannot be used on a fresh Plucky install.
Installing `rust-lldb` works fine, but upon invoking the command, the
following error message is presented:
lldb-17 not found! Please install it.
Attempting to install either `lldb-17` or `lldb` is impo
Public bug reported:
rust-forensic-adb uses the 2024 edition of Rust, which is not stabilized
as of the latest available rustc version in Plucky (1.84.1;
https://pad.lv/u/rustc-1.84).
This prevents the package from building.
** Affects: rust-forensic-adb (Ubuntu)
Importance: Undecided
** Changed in: rustc-1.82 (Ubuntu Focal)
Assignee: Max Gilmour (maxgmr) => (unassigned)
** Changed in: rustc-1.82 (Ubuntu Noble)
Assignee: Max Gilmour (maxgmr) => (unassigned)
** Changed in: rustc-1.82 (Ubuntu Jammy)
Assignee: Max Gilmour (maxgmr) => (unassigned)
** C
** Changed in: rustc-1.82 (Ubuntu Oracular)
Assignee: (unassigned) => Max Gilmour (maxgmr)
** Changed in: rustc-1.82 (Ubuntu Noble)
Assignee: (unassigned) => Max Gilmour (maxgmr)
** Changed in: rustc-1.82 (Ubuntu Jammy)
Assignee: (unassigned) => Max Gilmour (maxgmr)
** C
** Tags added: update-excuse
** Changed in: rust-safe-arch (Ubuntu)
Assignee: (unassigned) => Max Gilmour (maxgmr)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2103818
Title:
FTBFS on de
** Description changed:
Thanks to liushuyu-011 for pointing out the issue here:
https://code.launchpad.net/~maxgmr/ubuntu/+source/rust-safe-
arch/+git/rust-safe-arch/+merge/483266/comments/1310481
In all release versions of this crate, the `-Ctarget-cpu=native` flag is
- used during com
Public bug reported:
Thanks to liushuyu-011 for pointing out the issue here:
https://code.launchpad.net/~maxgmr/ubuntu/+source/rust-safe-
arch/+git/rust-safe-arch/+merge/483266/comments/1310481
In all release versions of this crate, the `-Ctarget-cpu=native` flag is
used during compilation of the
Public bug reported:
The `distutils` Python module was deprecated in Python 3.10, then
removed in Python 3.12; see here:
https://docs.python.org/3/whatsnew/3.12.html
This causes a FTBFS due to the missing module:
File "/<>/obj-x86_64-linux-gnu/python/specan_ui/setup.py", line
13, in
from
Public bug reported:
Conditional compilation is being applied to certain functions, but not
the doctests of those functions, leading to test failures when those
functions aren't compiled.
From the latest amd64 build log:
error[E0425]: cannot find function `test_mixed_ones_and_zeroes_m128i` in th
21 matches
Mail list logo
