Bug 1687921

Summary: fedora-repos-30-0.5 requires fedora-repos-rawhide
Product: [Fedora] Fedora Reporter: Adam Williamson <awilliam>
Component: fedora-reposAssignee: Mohan Boddu <mboddu>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 30CC: dennis, kellin, kevin, mboddu, pbrobinson, thrcka
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Unspecified   
Whiteboard:
Fixed In Version: fedora-repos-30-0.6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-03-29 19:14:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Adam Williamson 2019-03-12 16:14:44 UTC 
fedora-repos-30-0.5, which was built for Branched:

https://koji.fedoraproject.org/koji/buildinfo?buildID=1213936

still Requires: fedora-repos-rawhide . That seems wrong? Previous branched/stable fedora-repos packages don't seem to require fedora-repos-rawhide.
Comment 1 Mohan Boddu 2019-03-12 16:37:58 UTC 
https://src.fedoraproject.org/rpms/fedora-repos/pull-request/30 should fix this.

Thanks.
Comment 2 Fedora Update System 2019-03-13 17:43:23 UTC 
fedora-repos-30-0.6 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-1033155add
Comment 3 Fedora Update System 2019-03-14 20:59:12 UTC 
fedora-repos-30-0.6 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-1033155add
Comment 4 Fedora Update System 2019-03-29 19:14:54 UTC 
fedora-repos-30-0.6 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.