Hello, Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/ Your package (rust-bcrypt) Fails To Install in Fedora 41: can't install rust-bcrypt+js-devel: - nothing provides (crate(getrandom/js) >= 0.2.0 with crate(getrandom/js) < 0.3.0~) needed by rust-bcrypt+js-devel-0.15.0-1.fc41.noarch If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem. If you don't react accordingly to the policy for FTBFS/FTI bugs (https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/), your package may be orphaned in 8+ weeks. P.S. The data was generated solely from koji buildroot, so it might be newer than the latest compose or the content on mirrors. To reproduce, use the koji/local repo only, e.g. in mock: $ mock -r fedora-41-x86_64 --config-opts mirrored=False install rust-bcrypt+js-devel P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updating-inter-dependent-packages Thanks!
Why was getrandom/js patched out?
(In reply to Sandro Mani from comment #1) > Why was getrandom/js patched out? I'm not sure what you're getting at here? The "js" feature of the "getrandom" crate has been patched out for ages. It is specific to WASM / WebAssembly targets and since we don't support those it doesn't make sense to provide it. The bug is caused by the recent update for rust-bcrypt, presumably because it added a new optional dependency. In this case, my suggested solution would be to patch out the "js" feature from the bcrypt crate. I also recommend running local mock test builds with "--postinstall" to catch issues like this *before* pushing things to rawhide.
Apologies, misdiagnosed this - I obviously didn't realize that this was related to the rust-bcrypt update last month.