rustc - Debian Package Tracker

general

source: rustc (main)
version: 1.92.0+dfsg1-2
maintainer: Debian Rust Maintainers (archive) (DMD)
uploaders: Sylvestre Ledru [DMD] – Ximin Luo [DMD] – Fabian Grünbichler [DMD]
arch: all any
std-ver: 4.7.0
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 1.48.0+dfsg1-2
oldstable: 1.63.0+dfsg1-2
stable: 1.85.0+dfsg3-1
stable-bpo: 1.90.0+dfsg1-1~bpo13+2
testing: 1.92.0+dfsg1-1
unstable: 1.92.0+dfsg1-2
exp: 1.93.1+dfsg1-1~exp1

versioned links

1.48.0+dfsg1-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.63.0+dfsg1-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.85.0+dfsg3-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.86.0+dfsg1-1~bpo13+2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.87.0+dfsg1-1~bpo13+2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.88.0+dfsg1-2~bpo13+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.89.0+dfsg1-1~bpo13+2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.90.0+dfsg1-1~bpo13+2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.92.0+dfsg1-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.92.0+dfsg1-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.93.1+dfsg1-1~exp1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

cargo (1 bugs: 0, 1, 0, 0)
cargo-doc
libstd-rust-1.92
libstd-rust-dev
libstd-rust-dev-bpf
libstd-rust-dev-wasm32
libstd-rust-dev-windows
rust-all
rust-analyzer
rust-clippy
rust-doc (3 bugs: 0, 1, 2, 0)
rust-gdb (1 bugs: 0, 1, 0, 0)
rust-lldb
rust-llvm
rust-src (1 bugs: 0, 1, 0, 0)
rustc (9 bugs: 0, 9, 0, 0)
rustfmt (1 bugs: 0, 1, 0, 0)

action needed

A new upstream version is available: 1.94.1 high

A new upstream version 1.94.1 is available, you should consider packaging it.

Created: 2025-11-27 Last update: 2026-04-01 10:30

lintian reports 1 error and 17 warnings high

Lintian reports 1 error and 17 warnings about this package. You should make the package lintian clean getting rid of them.

Created: 2026-03-08 Last update: 2026-03-27 05:01

2 security issues in trixie high

There are 2 open security issues in trixie.

2 important issues:

CVE-2026-33055: tar-rs is a tar archive reading/writing library for Rust. Versions 0.4.44 and below have conditional logic that skips the PAX size header in cases where the base header size is nonzero. As part of CVE-2025-62518, the astral-tokio-tar project was changed to correctly honor PAX size headers in the case where it was different from the base header. This is almost the inverse of the astral-tokio-tar issue. Any discrepancy in how tar parsers honor file size can be used to create archives that appear differently when unpacked by different archivers. In this case, the tar-rs (Rust tar) crate is an outlier in checking for the header size - other tar parsers (including e.g. Go archive/tar) unconditionally use the PAX size override. This can affect anything that uses the tar crate to parse archives and expects to have a consistent view with other parsers. This issue has been fixed in version 0.4.45.
CVE-2026-33056: tar-rs is a tar archive reading/writing library for Rust. In versions 0.4.44 and below, when unpacking a tar archive, the tar crate's unpack_dir function uses fs::metadata() to check whether a path that already exists is a directory. Because fs::metadata() follows symbolic links, a crafted tarball containing a symlink entry followed by a directory entry with the same name causes the crate to treat the symlink target as a valid existing directory — and subsequently apply chmod to it. This allows an attacker to modify the permissions of arbitrary directories outside the extraction root. This issue has been fixed in version 0.4.45.

Created: 2026-03-26 Last update: 2026-03-27 01:00

2 security issues in forky high

There are 2 open security issues in forky.

2 important issues:

CVE-2026-33055: tar-rs is a tar archive reading/writing library for Rust. Versions 0.4.44 and below have conditional logic that skips the PAX size header in cases where the base header size is nonzero. As part of CVE-2025-62518, the astral-tokio-tar project was changed to correctly honor PAX size headers in the case where it was different from the base header. This is almost the inverse of the astral-tokio-tar issue. Any discrepancy in how tar parsers honor file size can be used to create archives that appear differently when unpacked by different archivers. In this case, the tar-rs (Rust tar) crate is an outlier in checking for the header size - other tar parsers (including e.g. Go archive/tar) unconditionally use the PAX size override. This can affect anything that uses the tar crate to parse archives and expects to have a consistent view with other parsers. This issue has been fixed in version 0.4.45.
CVE-2026-33056: tar-rs is a tar archive reading/writing library for Rust. In versions 0.4.44 and below, when unpacking a tar archive, the tar crate's unpack_dir function uses fs::metadata() to check whether a path that already exists is a directory. Because fs::metadata() follows symbolic links, a crafted tarball containing a symlink entry followed by a directory entry with the same name causes the crate to treat the symlink target as a valid existing directory — and subsequently apply chmod to it. This allows an attacker to modify the permissions of arbitrary directories outside the extraction root. This issue has been fixed in version 0.4.45.

Created: 2026-03-26 Last update: 2026-03-27 01:00

13 security issues in bullseye high

There are 13 open security issues in bullseye.

2 important issues:

CVE-2026-33055: tar-rs is a tar archive reading/writing library for Rust. Versions 0.4.44 and below have conditional logic that skips the PAX size header in cases where the base header size is nonzero. As part of CVE-2025-62518, the astral-tokio-tar project was changed to correctly honor PAX size headers in the case where it was different from the base header. This is almost the inverse of the astral-tokio-tar issue. Any discrepancy in how tar parsers honor file size can be used to create archives that appear differently when unpacked by different archivers. In this case, the tar-rs (Rust tar) crate is an outlier in checking for the header size - other tar parsers (including e.g. Go archive/tar) unconditionally use the PAX size override. This can affect anything that uses the tar crate to parse archives and expects to have a consistent view with other parsers. This issue has been fixed in version 0.4.45.
CVE-2026-33056: tar-rs is a tar archive reading/writing library for Rust. In versions 0.4.44 and below, when unpacking a tar archive, the tar crate's unpack_dir function uses fs::metadata() to check whether a path that already exists is a directory. Because fs::metadata() follows symbolic links, a crafted tarball containing a symlink entry followed by a directory entry with the same name causes the crate to treat the symlink target as a valid existing directory — and subsequently apply chmod to it. This allows an attacker to modify the permissions of arbitrary directories outside the extraction root. This issue has been fixed in version 0.4.45.

11 issues postponed or untriaged:

CVE-2020-36317: (needs triaging) In the standard library in Rust before 1.49.0, String::retain() function has a panic safety problem. It allows creation of a non-UTF-8 Rust string when the provided closure panics. This bug could result in a memory safety violation when other string APIs assume that UTF-8 encoding is used on the same string.
CVE-2020-36318: (needs triaging) In the standard library in Rust before 1.49.0, VecDeque::make_contiguous has a bug that pops the same element more than once under certain condition. This bug could result in a use-after-free or double free.
CVE-2020-36323: (needs triaging) In the standard library in Rust before 1.52.0, there is an optimization for joining strings that can cause uninitialized bytes to be exposed (or the program to crash) if the borrowed string changes after its length is checked.
CVE-2021-28875: (needs triaging) In the standard library in Rust before 1.50.0, read_to_end() does not validate the return value from Read in an unsafe context. This bug could lead to a buffer overflow.
CVE-2021-28876: (needs triaging) In the standard library in Rust before 1.52.0, the Zip implementation has a panic safety issue. It calls __iterator_get_unchecked() more than once for the same index when the underlying iterator panics (in certain conditions). This bug could lead to a memory safety violation due to an unmet safety requirement for the TrustedRandomAccess trait.
CVE-2021-28877: (needs triaging) In the standard library in Rust before 1.51.0, the Zip implementation calls __iterator_get_unchecked() for the same index more than once when nested. This bug can lead to a memory safety violation due to an unmet safety requirement for the TrustedRandomAccess trait.
CVE-2021-28878: (needs triaging) In the standard library in Rust before 1.52.0, the Zip implementation calls __iterator_get_unchecked() more than once for the same index (under certain conditions) when next_back() and next() are used together. This bug could lead to a memory safety violation due to an unmet safety requirement for the TrustedRandomAccess trait.
CVE-2021-28879: (needs triaging) In the standard library in Rust before 1.52.0, the Zip implementation can report an incorrect size due to an integer overflow. This bug can lead to a buffer overflow when a consumed Zip iterator is used again.
CVE-2021-29922: (needs triaging) library/std/src/net/parser.rs in Rust before 1.53.0 does not properly consider extraneous zero characters at the beginning of an IP address string, which (in some situations) allows attackers to bypass access control that is based on IP addresses, because of unexpected octal interpretation.
CVE-2021-31162: (needs triaging) In the standard library in Rust before 1.52.0, a double free can occur in the Vec::from_iter function if freeing the element panics.
CVE-2022-21658: (needs triaging) Rust is a multi-paradigm, general-purpose programming language designed for performance and safety, especially safe concurrency. The Rust Security Response WG was notified that the `std::fs::remove_dir_all` standard library function is vulnerable a race condition enabling symlink following (CWE-363). An attacker could use this security issue to trick a privileged program into deleting files and directories the attacker couldn't otherwise access or delete. Rust 1.0.0 through Rust 1.58.0 is affected by this vulnerability with 1.58.1 containing a patch. Note that the following build targets don't have usable APIs to properly mitigate the attack, and are thus still vulnerable even with a patched toolchain: macOS before version 10.10 (Yosemite) and REDOX. We recommend everyone to update to Rust 1.58.1 as soon as possible, especially people developing programs expected to run in privileged contexts (including system daemons and setuid binaries), as those have the highest risk of being affected by this. Note that adding checks in your codebase before calling remove_dir_all will not mitigate the vulnerability, as they would also be vulnerable to race conditions like remove_dir_all itself. The existing mitigation is working as intended outside of race conditions.

Created: 2026-03-26 Last update: 2026-03-27 01:00

2 security issues in bookworm high

There are 2 open security issues in bookworm.

2 important issues:

CVE-2026-33055: tar-rs is a tar archive reading/writing library for Rust. Versions 0.4.44 and below have conditional logic that skips the PAX size header in cases where the base header size is nonzero. As part of CVE-2025-62518, the astral-tokio-tar project was changed to correctly honor PAX size headers in the case where it was different from the base header. This is almost the inverse of the astral-tokio-tar issue. Any discrepancy in how tar parsers honor file size can be used to create archives that appear differently when unpacked by different archivers. In this case, the tar-rs (Rust tar) crate is an outlier in checking for the header size - other tar parsers (including e.g. Go archive/tar) unconditionally use the PAX size override. This can affect anything that uses the tar crate to parse archives and expects to have a consistent view with other parsers. This issue has been fixed in version 0.4.45.
CVE-2026-33056: tar-rs is a tar archive reading/writing library for Rust. In versions 0.4.44 and below, when unpacking a tar archive, the tar crate's unpack_dir function uses fs::metadata() to check whether a path that already exists is a directory. Because fs::metadata() follows symbolic links, a crafted tarball containing a symlink entry followed by a directory entry with the same name causes the crate to treat the symlink target as a valid existing directory — and subsequently apply chmod to it. This allows an attacker to modify the permissions of arbitrary directories outside the extraction root. This issue has been fixed in version 0.4.45.

Created: 2026-03-26 Last update: 2026-03-27 01:00

debian/patches: 2 patches with invalid metadata, 17 patches to forward upstream high

Among the 51 debian patches available in version 1.92.0+dfsg1-2 of the package, we noticed the following issues:

2 patches with invalid metadata that ought to be fixed.
17 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2023-02-26 Last update: 2026-03-26 21:31

The VCS repository is not up to date, push the missing commits. high

vcswatch reports that the current version of the package is not in its VCS.
Either you need to push your commits and/or your tags, or the information about the package's VCS are out of date. A common cause of the latter issue when using the Git VCS is not specifying the correct branch when the packaging is not in the default one (remote HEAD branch), which is usually "master" but can be modified in salsa.debian.org in the project's general settings with the "Default Branch" field). Alternatively the Vcs-Git field in debian/control can contain a "-b <branch-name>" suffix to indicate what branch is used for the Debian packaging.

Created: 2026-03-11 Last update: 2026-03-26 13:01

The package has not entered testing even though the delay is over normal

The package has not entered testing even though the 2-day delay is over. Check why.

Created: 2026-03-28 Last update: 2026-04-01 11:32

2 bugs tagged help in the BTS normal

The BTS contains 2 bugs tagged help, please consider helping the maintainer in dealing with them.

Created: 2020-12-10 Last update: 2026-04-01 11:30

1 bug tagged patch in the BTS normal

The BTS contains patches fixing 1 bug (2 if counting merged bugs), consider including or untagging them.

Created: 2026-03-31 Last update: 2026-04-01 11:30

Fails to build during reproducibility testing normal

A package building reproducibly enables third parties to verify that the source matches the distributed binaries. It has been identified that this source package produced different results, failed to build or had other issues in a test environment. Please read about how to improve the situation!

Created: 2025-10-24 Last update: 2026-04-01 08:01

2 open merge requests in Salsa normal

There are 2 open merge requests for this package on Salsa. You should consider reviewing and/or merging these merge requests.

Created: 2025-08-19 Last update: 2025-08-19 06:28

Multiarch hinter reports 2 issue(s) low

There are issues with the multiarch metadata for this package.

cargo-doc could be marked Multi-Arch: foreign
rust-doc could be marked Multi-Arch: foreign

Created: 2017-01-10 Last update: 2026-04-01 10:30

Issues found with some translations low

Automatic checks made by the Debian l10n team found some issues with the translations contained in this package. You should check the l10n status report for more information.

Issues can be things such as missing translations, problematic translated strings, outdated PO files, unknown languages, etc.

Created: 2024-12-06 Last update: 2025-10-26 14:32

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.4 instead of 4.7.0).

Created: 2025-02-21 Last update: 2026-03-31 15:01

testing migrations

This package will soon be part of the auto-openssl transition. You might want to ensure that your package is ready for it. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.
excuses:
- Migration status for rustc (1.92.0+dfsg1-1 to 1.92.0+dfsg1-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- ∙ ∙ Autopkgtest for libreoffice/4:26.2.1-1: amd64: Pass, arm64: Test triggered (failure will be ignored), i386: Test triggered (failure will be ignored), ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for lintian/2.132.1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
- ∙ ∙ Autopkgtest for node-source-map/0.7.0++dfsg2+really.0.6.1-15: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, riscv64: Pass, s390x: Test triggered
- ∙ ∙ Autopkgtest for rust-capstone/0.13.0-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
- ∙ ∙ Autopkgtest for rust-cargo: amd64: Test triggered (failure will be ignored), arm64: Test triggered (failure will be ignored), i386: Test triggered (failure will be ignored), ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored), s390x: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for rust-debian-watch/0.4.6-1: ppc64el: Pass ♻, s390x: Pass ♻
- ∙ ∙ Autopkgtest for rust-erbium-net/1.0.5-10: ppc64el: Pass ♻, s390x: Pass ♻
- ∙ ∙ Autopkgtest for rust-glib/0.21.5-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
- ∙ ∙ Autopkgtest for rust-gst-plugin-gtk4/0.14.4-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
- ∙ ∙ Autopkgtest for rust-gtk4/0.10.3-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
- ∙ ∙ Autopkgtest for rust-hickory-resolver/0.24.4-5: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
- ∙ ∙ Autopkgtest for rust-iptables/0.5.2-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Test triggered, riscv64: No tests, superficial or marked flaky ♻, s390x: Test triggered
- ∙ ∙ Autopkgtest for rust-libspa/0.9.2-1: ppc64el: Pass ♻, s390x: Pass ♻
- ∙ ∙ Autopkgtest for rust-nonempty-collections/1.1.0-1: ppc64el: Pass ♻, s390x: Pass ♻
- ∙ ∙ Autopkgtest for rust-ntpd/1.7.1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
- ∙ ∙ Autopkgtest for rust-prodash/28.0.0-5: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
- ∙ ∙ Autopkgtest for rust-pyo3/0.27.2-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered (failure will be ignored), s390x: Pass
- ∙ ∙ Autopkgtest for rust-rav1e/0.8.1-7: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
- ∙ ∙ Autopkgtest for rust-rocksdb/0.23.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
- ∙ ∙ Autopkgtest for rust-sequoia-keystore/0.7.1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
- ∙ ∙ Autopkgtest for rust-sqlx/0.8.3-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
- ∙ ∙ Autopkgtest for rust-sqlx-core/0.8.3-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
- ∙ ∙ Autopkgtest for rust-tokio/1.49.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
- ∙ ∙ Autopkgtest for rust-tree-magic-mini/3.2.2-1: ppc64el: Pass ♻, s390x: Pass ♻
- ∙ ∙ Autopkgtest for rust-wasmtime/29.0.1+dfsg-8: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
- ∙ ∙ Autopkgtest for rust-x11rb-protocol/0.13.2-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
- ∙ ∙ Autopkgtest for rustc/1.92.0+dfsg1-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for tree-sitter-rust-orchard/0.16.3+ds-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, riscv64: Pass, s390x: Test triggered
- ∙ ∙ Autopkgtest for unicode-segmentation-rs/0.2.1-1: ppc64el: Pass ♻, s390x: Pass ♻
- Additional info (not blocking):
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rustc.html
- ∙ ∙ Reproducibility regression on amd64: cargo-doc
- ∙ ∙ Reproducibility regression on arm64: cargo-doc
- ∙ ∙ Reproducibility regression on armhf: cargo-doc
- ∙ ∙ Reproducibility regression on i386: cargo-doc
- ∙ ∙ Reproducibility regression on ppc64el: cargo-doc
- ∙ ∙ 6 days old (needed 2 days)
- Not considered

news

[rss feed]

[2026-03-26] Accepted rustc 1.92.0+dfsg1-2 (source) into unstable (Fabian Grünbichler) (signed by: Fabian Gruenbichler)
[2026-03-20] rustc 1.92.0+dfsg1-1 MIGRATED to testing (Debian testing watch)
[2026-03-11] Accepted rustc 1.93.1+dfsg1-1~exp1 (source amd64 all) into experimental (Debian FTP Masters) (signed by: Fabian Gruenbichler)
[2026-03-08] Accepted rustc 1.92.0+dfsg1-1 (source) into unstable (Fabian Grünbichler) (signed by: Fabian Gruenbichler)
[2026-02-03] Accepted rustc 1.92.0+dfsg1-1~exp1 (source amd64 all) into experimental (Debian FTP Masters) (signed by: Fabian Gruenbichler)
[2026-01-05] rustc 1.91.1+dfsg1-1 MIGRATED to testing (Debian testing watch)
[2025-12-26] Accepted rustc 1.91.1+dfsg1-1 (source) into unstable (Fabian Grünbichler) (signed by: Fabian Gruenbichler)
[2025-12-23] Accepted rustc 1.91.1+dfsg1-1~exp3 (source) into experimental (Fabian Grünbichler) (signed by: Fabian Gruenbichler)
[2025-12-15] Accepted rustc 1.91.1+dfsg1-1~exp2 (source) into experimental (Fabian Grünbichler) (signed by: Fabian Gruenbichler)
[2025-12-15] Accepted rustc 1.91.1+dfsg1-1~exp1 (source amd64 all) into experimental (Debian FTP Masters) (signed by: Fabian Gruenbichler)
[2025-12-06] Accepted rustc 1.90.0+dfsg1-1~bpo13+2 (source) into stable-backports (Fabian Grünbichler) (signed by: Fabian Gruenbichler)
[2025-11-18] Accepted rustc 1.90.0+dfsg1-1~bpo13+1 (source amd64 all) into stable-backports (Debian FTP Masters) (signed by: Fabian Gruenbichler)
[2025-10-31] rustc 1.90.0+dfsg1-1 MIGRATED to testing (Debian testing watch)
[2025-10-26] Accepted rustc 1.89.0+dfsg1-1~bpo13+2 (source) into stable-backports (Fabian Grünbichler) (signed by: Fabian Gruenbichler)
[2025-10-26] Accepted rustc 1.89.0+dfsg1-1~bpo13+1 (source amd64 all) into stable-backports (Debian FTP Masters) (signed by: Fabian Gruenbichler)
[2025-10-25] Accepted rustc 1.90.0+dfsg1-1 (source) into unstable (Fabian Grünbichler) (signed by: Fabian Gruenbichler)
[2025-10-23] Accepted rustc 1.90.0+dfsg1-1~exp1 (source amd64 all) into experimental (Debian FTP Masters) (signed by: Fabian Gruenbichler)
[2025-10-23] rustc 1.89.0+dfsg1-1 MIGRATED to testing (Debian testing watch)
[2025-10-16] Accepted rustc 1.89.0+dfsg1-1 (source) into unstable (Fabian Grünbichler) (signed by: Fabian Gruenbichler)
[2025-10-12] Accepted rustc 1.88.0+dfsg1-2~bpo13+1 (source amd64 all) into stable-backports (Debian FTP Masters) (signed by: Fabian Gruenbichler)
[2025-10-10] Accepted rustc 1.89.0+dfsg1-1~exp1 (source amd64 all) into experimental (Debian FTP Masters) (signed by: Fabian Gruenbichler)
[2025-10-09] rustc 1.88.0+dfsg1-2 MIGRATED to testing (Debian testing watch)
[2025-10-03] Accepted rustc 1.88.0+dfsg1-2 (source) into unstable (Fabian Grünbichler) (signed by: Fabian Gruenbichler)
[2025-09-30] Accepted rustc 1.88.0+dfsg1-1 (source) into unstable (Fabian Grünbichler) (signed by: Fabian Gruenbichler)
[2025-09-29] Accepted rustc 1.87.0+dfsg1-1~bpo13+2 (source) into stable-backports (Fabian Grünbichler) (signed by: Fabian Gruenbichler)
[2025-09-28] Accepted rustc 1.87.0+dfsg1-1~bpo13+1 (source amd64 all) into stable-backports (Debian FTP Masters) (signed by: Fabian Gruenbichler)
[2025-09-27] Accepted rustc 1.88.0+dfsg1-1~exp1 (source amd64 all) into experimental (Debian FTP Masters) (signed by: Fabian Gruenbichler)
[2025-09-25] rustc 1.87.0+dfsg1-1 MIGRATED to testing (Debian testing watch)
[2025-09-20] Accepted rustc 1.87.0+dfsg1-1 (source) into unstable (Fabian Grünbichler) (signed by: Fabian Gruenbichler)
[2025-09-12] Accepted rustc 1.87.0+dfsg1-1~exp1 (source amd64 all) into experimental (Debian FTP Masters) (signed by: Fabian Gruenbichler)

bugs [bug history graph]

all: 21 22
RC: 0
I&N: 17 18
M&W: 4
F&P: 0
patch: 1 2
help: 2

links

homepage
lintian (1, 17)
buildd: logs, exp, reproducibility, cross
popcon
browse source code
edit tags
other distros
security tracker
l10n (70, -)
debian patches
debci