Bug 1830693

Summary: FTI: rubygem-hiera-vault: rubygem-hiera-vault, rubygem-hiera-vault-doc
Product: [Fedora] Fedora Reporter: Igor Raits <igor.raits>
Component: rubygem-hiera-vaultAssignee: Ed Marshall <esm>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: esm
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-03 10:16:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1803235    

Description Igor Raits 2020-05-03 09:55:19 UTC 
Hello,

Your package (rubygem-hiera-vault) Fails To Install in Fedora 33:

---
can't install rubygem-hiera-vault-0.2.2-8.fc33.noarch:
  - package rubygem-hiera-vault-0.2.2-8.fc33.noarch requires (rubygem(vault) >= 0.4 with rubygem(vault) < 1), but none of the providers can be installed
  - nothing provides rubygem(aws-sigv4) = 1.1.1 needed by rubygem-vault-0.13.1-1.fc33.noarch
---
can't install rubygem-hiera-vault-doc-0.2.2-8.fc33.noarch:
  - package rubygem-hiera-vault-doc-0.2.2-8.fc33.noarch requires rubygem-hiera-vault = 0.2.2-8.fc33, but none of the providers can be installed
  - package rubygem-hiera-vault-0.2.2-8.fc33.noarch requires (rubygem(vault) >= 0.4 with rubygem(vault) < 1), but none of the providers can be installed
  - nothing provides rubygem(aws-sigv4) = 1.1.1 needed by rubygem-vault-0.13.1-1.fc33.noarch
---

According to a 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 if you won't reply to this bug.

Thanks!
Comment 1 Igor Raits 2020-05-03 10:16:07 UTC 

*** This bug has been marked as a duplicate of bug 1830632 ***