Bug 1673202 - EPEL7 - cppformat-devel obsoleted by fmt-devel, but still in EPEL7
Summary: EPEL7 - cppformat-devel obsoleted by fmt-devel, but still in EPEL7
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: cppformat
Version: epel7
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Dave Johansen
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: EPEL7FailsToInstall
TreeView+ depends on / blocked
Reported: 2019-02-06 22:41 UTC by Troy Dawson
Modified: 2019-02-22 21:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-02-22 21:23:14 UTC
Type: Bug

Attachments (Terms of Use)

Description Troy Dawson 2019-02-06 22:41:07 UTC
fmt-devel-3.0.2-1.el7 obsoletes cppformat-devel < 3.0.2-1.el7
It also provides cppformat-devel = 3.0.2-1.el7

Oddly enough, fmt doesn't obsolete or provide cppformat.

But, cppformat was removed from Fedora almost three years ago.

I am trying to cleanup EPEL7 packages that don't install and/or obsoleted.

I believe cppformat should be removed from EPEL7.

Please respond to this bug, letting us know if you feel this package should be in EPEL7, or not.

If you wish it removed, let us know and we can have a proven packager remove it from EPEL7.

If you have not responded in two weeks, we will assume that you do not mind it being removed and will have a proven packager remove the package from EPEL7.

Comment 1 Dave Johansen 2019-02-07 03:49:04 UTC
I'm no longer using cppformat or fmt, so whatever needs to be done in EPEL is fine by me.

Comment 2 Troy Dawson 2019-02-07 13:35:16 UTC
Thank you for your reply.
I will put cppformat on my list of packages to remove from EPEL7.
It might still be a couple of weeks, because I tend to do them in batches.

Comment 3 Troy Dawson 2019-02-15 17:00:53 UTC
cppformat has been retired from EPEL7.
I will close this ticket once I have verified that it's out of the repo.

Comment 4 Troy Dawson 2019-02-22 21:23:14 UTC
Package is not in EPEL7 anymore.

Note You need to log in before you can comment on or make changes to this bug.