Bug 2062299

Summary:	Revert unwanted API for parsing main metadata together that is being added
Product:	Red Hat Enterprise Linux 8	Reporter:	amatej
Component:	createrepo_c	Assignee:	Packaging Maintenance Team <packaging-team-maint>
Status:	CLOSED ERRATA	QA Contact:	Jan Blazek <jblazek>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.6	CC:	lmiksik, mdomonko, packaging-team-maint
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	createrepo_c-0.17.7-5.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2062301 2062767 (view as bug list)		Environment:
Last Closed:	2022-05-10 13:57:14 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:	2062301, 2062767
Deadline:	2022-03-21

Description amatej 2022-03-09 14:05:58 UTC

Description of problem:
createrepo_c-0.17.7-4.el8 contains a new API both for c and python cr_xml_parse_main_metadata_together() added here: https://github.com/rpm-software-management/createrepo_c/pull/279. It is part of createrepo_c since 0.17.6.

It turned out this version of the API is not working for the requester (Pulp) and we are currently working on a new version: https://github.com/rpm-software-management/createrepo_c/pull/295

It would be better not to release the current version so we don't have to support it (it can be removed from upstream), we have a cleaner interface and there is only one way to do this.


Version-Release number of selected component (if applicable): createrepo_c-0.17.7-4.el8

Comment 10 errata-xmlrpc 2022-05-10 13:57:14 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (createrepo_c bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:1866