Bug#1118490: marked as done (unblock: rustc/1.89.0+dfsg1-1)
Your message dated Wed, 22 Oct 2025 10:35:28 +0200
with message-id <045de8ea-162a-4d8f-b3a3-eff2b1b38c4a@debian.org>
and subject line Re: Bug#1118490: unblock: rustc/1.89.0+dfsg1-1
has caused the Debian Bug report #1118490,
regarding unblock: rustc/1.89.0+dfsg1-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
1118490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1118490
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
rustc is blocked from migrating to testing by
autopkgtest regressions in rust-fs4.
These are caused by test code that has broken with
the version of the standard library in the new rustc.
This test code is only built when running autopkgtests,
not when building the package, or when using the
crate as a library in a larger rust program.
The tests are fixed in sid, but unfortunately a new
upstream release was uploaded at the same time as
the fix. Said new upstream release is blocked by
a new version of tree-sitter, which in turn is blocked
by the new version of rustc.
Can you please schedule autopktests for the new version
of rust-fs4 with the new version of rustc.
--- End Message ---
--- Begin Message ---
On 21/10/2025 12:24, Peter Green wrote:
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
rustc is blocked from migrating to testing by
autopkgtest regressions in rust-fs4.
These are caused by test code that has broken with
the version of the standard library in the new rustc.
This test code is only built when running autopkgtests,
not when building the package, or when using the
crate as a library in a larger rust program.
The tests are fixed in sid, but unfortunately a new
upstream release was uploaded at the same time as
the fix. Said new upstream release is blocked by
a new version of tree-sitter, which in turn is blocked
by the new version of rustc.
Can you please schedule autopktests for the new version
of rust-fs4 with the new version of rustc.
I have instead added a hint to ignore that failure.
Cheers,
Emilio
--- End Message ---
Reply to: