Bug 1972945

Summary:	kf5-baloo: lmdb-devel build requirement retired
Product:	[Fedora] Fedora EPEL	Reporter:	Carl George 🤠 <carl>
Component:	kf5-baloo	Assignee:	Daniel Vrátil <me>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel8	CC:	jgrulich, kde-sig, me, rdieter, than
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:	2021-06-18 01:32:43 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 Carl George 🤠 2021-06-16 23:56:56 UTC

Description of problem:
The lmdb package had to be retired from EPEL8 due to policy [0].  RHEL8 ships lmdb-libs, but no other subpackages.  kf5-baloo has a build requirement on lmdb-devel.  It will now fail to build from source.  One of the following options must be performed on this package.

- Remove the lmdb-devel build requirement if possible.
- Convince RHEL to ship lmdb-devel in RHEL8 CRB [1].
- Create a new lmdb-devel spec file for EPEL8, derived from the RHEL8 lmdb spec file [2], taking care to remove every package and file that is shipped in RHEL8.
- Retire kf5-baloo.


Version-Release number of selected component (if applicable):
kf5-baloo-5.68.0-1.el8


[0] bug 1833564
[1] https://wiki.centos.org/FAQ/CentOS8/UnshippedPackages
[2] https://git.centos.org/rpms/lmdb/blob/c8/f/SPECS/lmdb.spec

Comment 1 Fedora Update System 2021-06-17 21:21:37 UTC

FEDORA-EPEL-2021-aee92318fa has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-aee92318fa

Comment 2 Fedora Update System 2021-06-18 01:32:43 UTC

FEDORA-EPEL-2021-aee92318fa has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.