Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2055686

Summary: package removal emits Failed to remove entry from /etc/sgml/catalog
Product: Red Hat Enterprise Linux 9 Reporter: Jiri Jaburek <jjaburek>
Component: docbook-dtdsAssignee: Ondřej Sloup <osloup>
Status: CLOSED WONTFIX QA Contact: CS System Management SST QE <rhel-cs-system-management-subsystem-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.0CC: hhorak, osloup
Target Milestone: rcFlags: pm-rhel: mirror+
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: 2023-08-17 07:28: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 Jiri Jaburek 2022-02-17 14:15:40 UTC
Description of problem:

When removing the docbook-dtds package, I'm getting a scriptlet error:

  Erasing          : docbook-dtds-1.0-79.el9.noarch      1/3 
  Running scriptlet: docbook-dtds-1.0-79.el9.noarch      1/3 
Failed to remove entry from /etc/sgml/catalog

  Erasing          : sgml-common-0.6.3-58.el9.noarch     2/3 
  Erasing          : xml-common-0.6.3-58.el9.noarch      3/3 


This started appearing recently (was not present in RHEL-9.0.0-20220210.0, fails in RHEL-9.0.0-20220215.4, despite no docbook-dtds version change).

Maybe it's a result of removing some docbook-* packages from AppStream between the two composes:

  docbook-style-dsssl-1.79-33.el9
  docbook-utils-0.6.14-54.el9
  docbook-utils-pdf-0.6.14-54.el9

though this removal might be unrelated.

Looking at the RPM scriptlets, I'm not seeing any obvious and the error message isn't exactly verbose either, so I'm leaving it up to you to investigate.


Version-Release number of selected component (if applicable):
docbook-dtds-1.0-79.el9

Comment 1 Ondrej Vasik 2022-03-11 08:11:04 UTC
Thanks for report. I believe this error occurs if the package is the last one which uses /etc/sgml/catalog - IOW, if you still have more such packages installed, error message will not occur upon uninstall of docbook-dtds. I have seen similar report in the past, not sure, how to fix it (probably some more complicated scriptlet). Docbook-style-dsssl rpm uses the /etc/sgml/catalog file too. so its removal from AppStream probably revealed this harmless error message.

Comment 3 RHEL Program Management 2023-08-17 07:28:43 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.