Bug 1397994

Summary:	gmime has been orphaned and removed from the EPEL 6 Repository
Product:	[Fedora] Fedora EPEL	Reporter:	Luke <lhebert>
Component:	gmime	Assignee:	Pete Walter <walter.pete>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	el6	CC:	walter.pete
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-23 19:48:13 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:

Description Luke 2016-11-23 18:37:07 UTC

Description of problem:

There are applications which have dependencies on gmime however it appears as though the epel 6 package has been orphaned and subsequently removed from the epel 6 repository. Please restore the package to the repository.

https://admin.fedoraproject.org/pkgdb/package/rpms/gmime/
https://apps.fedoraproject.org/packages/gmime

 till retired gmime in el6 3 days ago
 till pushed to gmime (el6). "2016-11-20: Retired orphaned package, because it was orphaned for (..more)" 3 days ago
 till retired gmime in el5 3 days ago
 till pushed to gmime (el5). "2016-11-20: Retired orphaned package, because it was orphaned for (..more)" 3 days

Comment 1 Jason Tibbitts 2016-11-23 18:44:40 UTC

The package was removed because it has no maintainer.  It can't be re-added to the repository until it has a maintainer.  Filing a bugzilla ticket to the attention of the maintainer who does not exist sadly doesn't change that basic fact.  (I only happened to notice this ticket in an IRC log.)

If there are packages in EPEL6 which require this package then they will be removed from EPEL6 as well.  Generally that all happens automatically but it might not have happened in this instance.

If you require this package, I can only suggest that you volunteer to maintain it.  Come to the epel-devel mailing list or #epel on freenode and I'm sure someone would be willing to assist you.

Comment 2 Luke 2016-11-23 19:48:13 UTC

(In reply to Jason Tibbitts from comment #1)
> The package was removed because it has no maintainer.  It can't be re-added
> to the repository until it has a maintainer.  Filing a bugzilla ticket to
> the attention of the maintainer who does not exist sadly doesn't change that
> basic fact.  (I only happened to notice this ticket in an IRC log.)
> 
> If there are packages in EPEL6 which require this package then they will be
> removed from EPEL6 as well.  Generally that all happens automatically but it
> might not have happened in this instance.
> 
> If you require this package, I can only suggest that you volunteer to
> maintain it.  Come to the epel-devel mailing list or #epel on freenode and
> I'm sure someone would be willing to assist you.

Thank you for responding here Jason. Reviewing the code base it appears as though the developer hasn't issued any new releases since 2014. It doesn't appear as though the source has changed since the last release. I'm not sure I am the right person to maintain a package but I'll consider it. I suppose this can be closed for now.