Bug 474766
Summary: | TclXML reports an error when an xml-stylesheet PI is encountered | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | James Armstrong <james_armstrong> |
Component: | tclxml | Assignee: | Wart <wart> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 10 | CC: | wart |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-12-24 18:40:03 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
James Armstrong
2008-12-05 09:13:03 UTC
Note an unfortunate "line wrap" on the statement that begins: set parser [::xml::parser .... ] tclxml was released a few days ago, however it doesn't appear that this patch made it into the new release. I'm working on updating the fedora package to 3.2 and will include this patch with the updated package. tclxml-3.1-14.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/tclxml-3.1-14.fc10 tclxml-3.2 has quite a few issues that need to be fixed before it can be updated in Fedora. In the meantime, I've fixed this specific problem for tclxml 3.1. tclxml-3.1-14.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update tclxml'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2008-11595 tclxml-3.1-14.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report. |