Description of problem: rust-cargo unable to install due to depencency versions inconsistency in EPEL Version-Release number of selected component (if applicable): rust-cargo-devel-0.78.1-1.el9.noarch rust-gix-devel-0.63.0-2.el9.noarch (crate(gix)) rust-gix+progress-tree-devel-0.63.0-2.el9.noarch (crate(gix/progress-tree)) rust-gix+revision-devel-0.63.0-2.el9.noarch (crate(gix/revision)) How reproducible: always Steps to Reproduce: 1. dnf install epel-release 2. LANG=C sudo dnf --enablerepo=crb install rust-cargo-devel Actual results: [kabe@rocky9 epel]$ LANG=C sudo dnf --enablerepo=crb install rust-cargo-devel Last metadata expiration check: 0:26:26 ago on Sat Sep 14 00:21:23 2024. Error: Problem: conflicting requests - nothing provides (crate(gix) >= 0.61.0 with crate(gix) < 0.62.0~) needed by rust-cargo-devel-0.78.1-1.el9.noarch from epel - nothing provides (crate(gix/blocking-http-transport-curl) >= 0.61.0 with crate(gix/blocking-http-transport-curl) < 0.62.0~) needed by rust-cargo-devel-0.78.1-1.el9.noarch from epel - nothing provides (crate(gix/progress-tree) >= 0.61.0 with crate(gix/progress-tree) < 0.62.0~) needed by rust-cargo-devel-0.78.1-1.el9.noarch from epel - nothing provides (crate(gix/revision) >= 0.61.0 with crate(gix/revision) < 0.62.0~) needed by rust-cargo-devel-0.78.1-1.el9.noarch from epel (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) Expected results: rust-cargo-devel installed, with dependencies pulled in Additional info: Current rust-cargo-devel-0.78.1-1.el9.noarch depends on crate(gix) >= 0.61.0 with crate(gix) < 0.62.0~, but currently provided rust-gix-devel-0.63.0-2.el9.noarch (crate(gix)) is not within the version limit. EIther rust-gix is proceeding too fast, or rust-cargo-devel is lagging.
This is a known problem that we can only fix with the next RHEL 9 point release. That will ship an updated Rust toolchain, which will enable us to update the "rust-cargo" package. Though I do wonder why you would attempt to install rust-cargo-devel locally?
I was trying to compile `rust-cargo-c` package for non-x86_64, which seems to generates the above dependency by %cargo_generate_buildrequires .
Are the builds available for aarch64, ppc64le, s390x not enough? https://koji.fedoraproject.org/koji/buildinfo?buildID=2451680 Or do you want to compile cargo-c with local changes? As a workaround until I can fix the broken dependencies in the epel9 repo, you could try using the buildroot based on CentOS Stream 9 + EPEL9-Next (centos-stream+epel-next-9-x86_64), which already contains the fix.
I am compiling for i686 (for i586, strictly said). I known that is not a supported architecture, but helps are greatly appreciated.
What buildroot are you even using for a build like this? 😅 Anyway, another gix update will be landing in EPEL 9 within the next few days, I'll try to fix the broken dependency in rust-cargo at the same time. Note that you might have problems building cargo-c on 32-bit x86 anyway - I've had issues in the past that the linker hit OOM when building it on 32-bit architectures.
*** Bug 2313908 has been marked as a duplicate of this bug. ***
FEDORA-EPEL-2024-680c39933a (rust-bitstream-io-2.6.0-1.el9, rust-bitvec_helpers-3.1.6-1.el9, and 11 more) has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-680c39933a
FEDORA-EPEL-2024-680c39933a 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-2024-680c39933a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2024-680c39933a (rust-bitstream-io-2.6.0-1.el9, rust-bitvec_helpers-3.1.6-1.el9, and 11 more) has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.