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.
Created attachment 1561657[details]
custom validation script
Description of problem:
Based on the discussion with cgarnch. the file org.gnome.nautilus.gschema.xml,
located in /usr/share/glib-2.0/schemas should be valid againt this DTD schema:
https://gitlab.gnome.org/GNOME/glib/blob/master/gio/gschema.dtd
which is not a case.
Version-Release number of selected component (if applicable):
nautilus-3.28.1-5.el8.x86_64
How reproducible:
always
Actual results:
/usr/share/glib-2.0/schemas/org.gnome.nautilus.gschema.xml:77:0:ERROR:VALID:DTD_UNKNOWN_ATTRIBUTE: No declaration for attribute target of element alias
/usr/share/glib-2.0/schemas/org.gnome.nautilus.gschema.xml:114:0:ERROR:VALID:DTD_UNKNOWN_ATTRIBUTE: No declaration for attribute target of element alias
/usr/share/glib-2.0/schemas/org.gnome.nautilus.gschema.xml:155:0:ERROR:VALID:DTD_UNKNOWN_ATTRIBUTE: No declaration for attribute target of element alias
/usr/share/glib-2.0/schemas/org.gnome.nautilus.gschema.xml:167:0:ERROR:VALID:DTD_UNKNOWN_ATTRIBUTE: No declaration for attribute target of element alias
/usr/share/glib-2.0/schemas/org.gnome.nautilus.gschema.xml:180:0:ERROR:VALID:DTD_UNKNOWN_ATTRIBUTE: No declaration for attribute target of element alias
/usr/share/glib-2.0/schemas/org.gnome.nautilus.gschema.xml:181:0:ERROR:VALID:DTD_UNKNOWN_ATTRIBUTE: No declaration for attribute target of element alias
/usr/share/glib-2.0/schemas/org.gnome.nautilus.gschema.xml:182:0:ERROR:VALID:DTD_UNKNOWN_ATTRIBUTE: No declaration for attribute target of element alias
/usr/share/glib-2.0/schemas/org.gnome.nautilus.gschema.xml:183:0:ERROR:VALID:DTD_UNKNOWN_ATTRIBUTE: No declaration for attribute target of element alias
Expected results:
There should be no errors
Additional info:
I am attaching custom script in python3 I used for validation.
To be honest, it's not causing issues but I was tasked to make a gating test for glib, the devel suggested this solution (validation against DTD)
and I discovered several of those xmls aren't valid, therefore, we come to the agreement that this should be fixed, and I reported bugs for those components.
Since the gating had to be done a while ago I've revorked the test completely without the DTD verificaton, hoping that we might be able to enable it in future releases.
That's the motivation behind the bug....
Comment 4Michael Catanzaro
2020-08-04 21:48:56 UTC
Looks like this is fixed upstream. It's not serious enough to warrant fixing in RHEL, so closing.