Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Package rust-resctl-bench fails to build from source in Fedora Rawhide. Version-Release number of selected component (if applicable): 2.2.5-10.fc45 Steps to Reproduce: koji build --scratch f45 rust-resctl-bench-2.2.5-10.fc45.src.rpm Additional info: This package is tracked by Koschei. See: https://koschei.fedoraproject.org/package/rust-resctl-bench error[E0283]: type annotations needed --> src/base.rs:503:43 | 503 | match af.report.data.sysloads.get(INODESTEAL_TEST.into()) { | ^^^ ---------------------- type must be known at this point | | | cannot infer type of the type parameter `Q` declared on the method `get` | = note: multiple `impl`s satisfying `std::string::String: Borrow<_>` found in the following crates: `alloc`, `core`: - impl Borrow<str> for std::string::String; - impl<T> Borrow<T> for T where T: ?Sized; note: required by a bound in `BTreeMap::<K, V, A>::get` --> library/alloc/src/collections/btree/map.rs:718:4 help: consider specifying the generic argument | 503 | match af.report.data.sysloads.get::<Q>(INODESTEAL_TEST.into()) { | +++++ I used "fedpkg --release f44 mockbuild --enablerepo=updates-testing" to verify that whichever update is responsible is in fact in updates-testing, and you can expect that this package will soon FTBFS in all branches.
I believe the interesting error is actually further down in the build.log: error[E0283]: type annotations needed --> src/base.rs:503:63 | 503 | match af.report.data.sysloads.get(INODESTEAL_TEST.into()) { | ^^^^ | = note: multiple `impl`s satisfying `&_: From<&str>` found in the following crates: `core`, `zerocopy`: - impl<'a, T> From<&'a T> for &'a zerocopy::wrappers::read_only_def::ReadOnly<T> where T: zerocopy::Immutable, T: ?Sized; - impl<T> From<T> for T; = note: required for `&str` to implement `Into<&_>` Indeed, the "zerocopy" crate was updates in rawhide and is in "testing" for other branches right now. It looks like somewhere betweeen v0.8.31 and v0.8.47, new implementationi for `From<&str>` was added for types. This is not necessarily a breaking change, but can cause type inference failures like in this case. The compiler error even says what to do here: help: try using a fully qualified path to specify the expected types | 503 - match af.report.data.sysloads.get(INODESTEAL_TEST.into()) { 503 + match af.report.data.sysloads.get(<&str as Into<&Q>>::into(INODESTEAL_TEST)) { |
Hmm, I tried that and got a further error: error[E0425]: cannot find type `Q` in this scope --> src/base.rs:507:37 | 507 | .get(<&str as Into<&Q>>::into(INODESTEAL_TEST)) | ^ not found in this scope | help: you might be missing a type parameter | 50 | impl<'a, Q> Base<'a> { | +++ If I try that, I get: error[E0425]: cannot find type `Q` in this scope --> src/base.rs:507:41 | 507 | .get(<&str as Into<'a, &Q>>::into(INODESTEAL_TEST)) | ^ not found in this scope | help: you might be missing a type parameter | 50 | impl<'a, Q> Base<'a> { | +++ It doesn’t help that I can’t seem to reproduce this easily in a git checkout, but I do run into other build issues with the path dependencies there. Rather than either activating my brain and trying to reason about this on the one hand, or listening to the compiler and following the will-o’-the-wisp deeper into the bog on the other hand, I’m just going to leave this for a regular maintainer of the package to investigate.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 45 development cycle. Changing version to 45.
FEDORA-2026-a89a8dd5ed (rust-resctl-bench-2.2.5-14.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-a89a8dd5ed
FEDORA-EPEL-2026-3fd7822b43 (rust-resctl-bench-2.2.5-14.el9) has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-3fd7822b43
FEDORA-2026-8a5026e14b (rust-resctl-bench-2.2.5-14.fc45) has been submitted as an update to Fedora 45. https://bodhi.fedoraproject.org/updates/FEDORA-2026-8a5026e14b
Turns out, fixing this issue was much, much less involved that initially assumed. Just dropping the ".into()" did the trick.
FEDORA-2026-8a5026e14b has been pushed to the Fedora 45 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-8a5026e14b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-8a5026e14b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2026-3fd7822b43 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-3fd7822b43 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-83bc243165 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-83bc243165` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-83bc243165 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-a89a8dd5ed has been pushed to the Fedora 44 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-a89a8dd5ed` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-a89a8dd5ed See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-6809b4143f has been pushed to the Fedora 45 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-6809b4143f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-6809b4143f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2026-d8c3ea49ea has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-d8c3ea49ea See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-1af426cc3c has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-1af426cc3c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-1af426cc3c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-7327b9945e has been pushed to the Fedora 44 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-7327b9945e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-7327b9945e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-6809b4143f (rust-resctl-bench-2.2.5-16.fc45) has been pushed to the Fedora 45 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-1af426cc3c (rust-resctl-bench-2.2.5-16.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2026-d8c3ea49ea (rust-resctl-bench-2.2.5-16.el9) has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-7327b9945e (rust-resctl-bench-2.2.5-16.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.