Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at

Bug 1892945

Summary: F34FailsToInstall: rust-hashbrown+alloc-devel, rust-hashbrown+compiler_builtins-devel, rust-hashbrown+core-devel, rust-hashbrown+rustc-dep-of-std-devel
Product: [Fedora] Fedora Reporter: Miro Hrončok <mhroncok>
Component: rust-hashbrownAssignee: Rust SIG <rust-sig>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: decathorpe, jistone, rust-sig
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-09 23:25:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1868279    

Description Miro Hrončok 2020-10-29 19:30:57 UTC

Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (mhroncok).

Your package (rust-hashbrown) Fails To Install in Fedora 34:

can't install rust-hashbrown+alloc-devel:
  - nothing provides (crate(rustc-std-workspace-alloc/default) >= 1.0.0 with crate(rustc-std-workspace-alloc/default) < 2.0.0) needed by rust-hashbrown+alloc-devel-0.9.1-1.fc34.noarch
can't install rust-hashbrown+compiler_builtins-devel:
  - nothing provides (crate(compiler_builtins/default) >= 0.1.2 with crate(compiler_builtins/default) < 0.2.0) needed by rust-hashbrown+compiler_builtins-devel-0.9.1-1.fc34.noarch
can't install rust-hashbrown+core-devel:
  - nothing provides (crate(rustc-std-workspace-core/default) >= 1.0.0 with crate(rustc-std-workspace-core/default) < 2.0.0) needed by rust-hashbrown+core-devel-0.9.1-1.fc34.noarch
can't install rust-hashbrown+rustc-dep-of-std-devel:
  - nothing provides (crate(compiler_builtins/default) >= 0.1.2 with crate(compiler_builtins/default) < 0.2.0) needed by rust-hashbrown+rustc-dep-of-std-devel-0.9.1-1.fc34.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 (, 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.

P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags:


Comment 1 Josh Stone 2020-10-29 20:25:14 UTC
Fabio, you added these subpackages in your last update. I had been keeping them out because those features only make sense in the context of hashbrown's inclusion in std (backing the standard HashMap). Do we have any mechanism to get rust2rpm to avoid "bad" features yet?

Comment 2 Fabio Valentini 2020-10-30 15:32:19 UTC
Sorry about that, those additional features have slipped through. I'll clean this up this weekend.

As for having a mechanism to avoid features, there's a discussion I had with zbyszek today:

Basically we think we can extend .rust2rpm.conf files to also specify unwanted-features, which then don't get generated subpackages in the .spec file.

Comment 3 Josh Stone 2020-10-30 16:22:07 UTC
Sounds great -- the more we can automate this, the better!

Comment 4 Miro Hrončok 2020-11-09 23:25:03 UTC

Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (mhroncok).

All subpackages of a package against which this bug was filled are now installable or removed from Fedora 34.

Thanks for taking care of it!