Bug 1749877

Summary:	update to latest
Product:	[Fedora] Fedora EPEL	Reporter:	Brian J. Murrell <brian>
Component:	mpi4py	Assignee:	Gwyn Ciesla <gwync>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	epel7	CC:	dakingun, python-sig, tomspur, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-06-23 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 Brian J. Murrell 2019-09-06 15:58:18 UTC

Is there any technical reason why this package has lagged so far behind?  F30 has 3.0.1 for example.

The version in epel7 currently is over 3 years old.  Just wondering if there is any technical reason for that.

Comment 1 Zbigniew Jędrzejewski-Szmek 2019-09-07 06:51:59 UTC

mpi4py-2.0 had various incompatible changes from mpi4py-1.3 that is in EPEL. So we just
follow the usual policy of only updating things in EPEL if a bug is reported.

Comment 2 Fedora Admin user for bugzilla script actions 2020-06-13 14:53:13 UTC

This package has changed maintainer in the Fedora.
Reassigning to the new maintainer of this component.

Comment 3 Gwyn Ciesla 2020-06-23 19:14:54 UTC

Please reopen if there's a major security issue or other bug in the release EL-7 version.

Comment 4 Brian J. Murrell 2020-06-23 19:55:41 UTC

Maybe a piece of software in a repository gets so old that nobody even uses it any more to find bugs, or security issues, etc.

I know I'm certainly in that camp, rolling my own, newer version now.