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 568059 [details]
testcase

Description of problem:
See attached large XML file (complete Czech study translation of Bible in OSIS XML language).

Version-Release number of selected component (if applicable):
libxml2-2.7.6-4.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1.run xmllint --noout --schema http://www.bibletechnologies.net/osisCore.2.1.1.xsd bible.xml
2.
3.
  
Actual results:
bible.xml:65535: element q: Schemas validity error : Element '{http://www.bibletechnologies.net/2003/OSIS/namespace}q': This element is not expected. Expected is one of ( {http://www.bibletechnologies.net/2003/OSIS/namespace}a, {http://www.bibletechnologies.net/2003/OSIS/namespace}abbr, {http://www.bibletechnologies.net/2003/OSIS/namespace}date, {http://www.bibletechnologies.net/2003/OSIS/namespace}divineName, {http://www.bibletechnologies.net/2003/OSIS/namespace}foreign, {http://www.bibletechnologies.net/2003/OSIS/namespace}hi, {http://www.bibletechnologies.net/2003/OSIS/namespace}index, {http://www.bibletechnologies.net/2003/OSIS/namespace}lb, {http://www.bibletechnologies.net/2003/OSIS/namespace}milestone, {http://www.bibletechnologies.net/2003/OSIS/namespace}milestoneEnd ).


Expected results:
correct line number ... there is no <q> element on line 65535

Additional info:

  Sorry the internal tree model has room to keep lines
only on a 16 bits integer and I can't change that without breaking the
API.
The validation error is right I would guess, except for the line number.

Getting that line number would be hard, even in the streaming case

 xmllint --stream --schema http://www.bibletechnologies.net/osisCore.2.1.1.xsd bible.xml

this was raised upstream and I dropped the request due to the ABI stability
issue. I could try to be inventive and attempt a solution in the case of
streaming, but that's not a simple problem. My first take is WONTFIX as
this is the upstream status-quo, but if you can come with convincing
arguments on reopen of the bug, I may try to spend some time on it :-)

Daniel