Bug 2047326

Summary:	Fix rpminspect XML failure
Product:	Red Hat Enterprise Linux 9	Reporter:	David King <dking>
Component:	libxslt	Assignee:	David King <dking>
Status:	CLOSED ERRATA	QA Contact:	Tomas Pelka <tpelka>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.0	CC:	tpelka, tpopela
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	libxslt-1.1.34-9.el9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-17 13:52:06 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:

Comment 3 David King 2022-01-28 09:44:18 UTC

The XML check in rpminspect is two-fold; a check for whether the document is well-formed (with a failure leading to a VERIFY result, in other words, an error) and a check for whether the document is valid (which leads to an INFO result). The new build fixes the well-formedness of the tutorial document, as I verified locally with "xmllint --noout --xinclude --postvalid --noent doc/tutorial2/libxslt_pipes.xml". However, it is pretty easy to fix the validity too, so I will get my fixes into a new build, hopefully solving the problem entirely. If that does not work, I can ignore the failure using rpminspect.yaml. The validity error in /usr/share/doc/libxslt-devel/tutorial/libxslttutorial.xml seems bogus, as that validates locally (but a source file is included with a system entity, and that may trip up rpminspect, in which case ignoring just that file would be appropriate).

Comment 9 errata-xmlrpc 2022-05-17 13:52:06 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 (new packages: libxslt), 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:2604