Bug 1760979

Summary: EPEL7 - mingw{32,64}-qt5-qtbase won't install on RHEL 7.7
Product: [Fedora] Fedora EPEL Reporter: Troy Dawson <tdawson>
Component: mingw-qt5-qtbaseAssignee: Sandro Mani <manisandro>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel7CC: erik-fedora, manisandro
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-02-13 12:06:34 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:
Bug Depends On:    
Bug Blocks: 1647564    

Description Troy Dawson 2019-10-11 20:54:36 UTC 
Current mingw32-qt5-qtbase and mingw64-qt5-qtbase for EPEL7 (mingw32-qt5-qtbase-5.6.0-3.el7 and mingw64-qt5-qtbase-5.6.0-3.el7) requires
  mingw32-postgresql and mingw64-postgresql
These packages are no longer found in RHEL 7.7 or EPEL 7.

Please fix this package so that it can be installed in RHEL 7.7.
If you have not responded in a week, we will have a proven packager fix it.
If you know you will not be able to get to it and would like it fixed sooner, please let us know in this bug.
If you feel this package should no longer be in EPEL7, please let us know in this bug.
Comment 1 Sandro Mani 2019-10-11 20:57:16 UTC 
The MinGW stack on EPEL is in a pretty sorry state and desperately needs a maintainer which actually uses it. So far, no-one has stepped up [1]. So these packages should probably just be retired en-masse.

[1] https://lists.fedoraproject.org/archives/list/mingw@lists.fedoraproject.org/thread/SM2KIADSZRV6T2ONC3XURJ3QXE3HZWYS/
Comment 2 Richard W.M. Jones 2020-02-13 12:06:34 UTC 
All mingw-* EPEL 7 components have been retired.  Please see:

https://pagure.io/fesco/issue/2333

Therefore this bug no longer applies and is being mass closed.