Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 725130 - media-libs/opencollada-1.6.63-r1: DAEValidator fails to parse schema file
Summary: media-libs/opencollada-1.6.63-r1: DAEValidator fails to parse schema file
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Paul Zander
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-05-25 01:42 UTC by Adrian
Modified: 2024-03-16 08:54 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adrian 2020-05-25 01:42:02 UTC
DAEValidator expects the schema files to be in the executable or current directory. Once they are decompressed and placed in position, running the DAE validator fails to validate a sample dae file. The file is valid when using OpenCOLLADAValidator.

Reproducible: Always

Steps to Reproduce:
1. # bzcat /usr/share/doc/opencollada-1.6.63-r1/usr/bin/collada_schema_1_4_1.xsd.bz2 > /usr/bin/collada_schema_1_4_1.xsd
2. $ DAEValidator bamboo\ shark.dae
Actual Results:  
Processing /home/adrian/Downloads/bamboo shark.dae (255kB)
Checking schema...
/usr/bin/collada_schema_1_4_1.xsd:1: parser error : Document is empty

^
Schemas parser error : Failed to parse the XML resource '/usr/bin/collada_schema_1_4_1.xsd'.
I/O error : No such file or directory
file:///etc/xml/catalog:1: parser error : Document is empty

^
I/O warning : failed to load external entity "/home/adrian/Downloads/collada_schema_1_4_1.xsd"
Schemas parser error : Failed to locate the main schema resource at '/home/adrian/Downloads/collada_schema_1_4_1.xsd'.
/home/adrian/Downloads/bamboo%20shark.dae:2: element COLLADA: Schemas validity error : Element '{http://www.collada.org/2005/11/COLLADASchema}COLLADA': No matching global declaration available for the validation root.
Checking unique ids...
Checking unique sids...
Checking links...
file:///home/adrian/Downloads/bamboo%20shark.dae:14: Can't resolve preset://studio.lib4d/Example%20Scenes/Render%20Examples/01%20Scenes/tex/Glow%20(Kitchen%20HDR).HDR
file:///home/adrian/Downloads/bamboo%20shark.dae:17: Can't resolve file:///home/adrian/Downloads/tex.jpg
Processed 1 documents in 0.001s
Validation FAILED.


Expected Results:  
"bamboo shark.dae" is valid against the COLLADA 1.4.1 schema.


The call to xmlSchemaParse() in DAEValidator/library/src/XmlSchema.cpp:28 returns null, indicating that libxml2 is unable to parse the schema file.
Comment 1 Jonas Stein gentoo-dev 2020-05-25 20:06:35 UTC
does this mean the program is unusable now?

https://github.com/KhronosGroup/OpenCOLLADA/wiki/OpenCOLLADA-Tools

Was your problem already described in one of the upstream tickets?
https://github.com/KhronosGroup/OpenCOLLADA/issues
Comment 2 Adrian 2020-05-25 23:34:29 UTC
The package is still useful as the library functions for opencollada still work, and it can be used successfully by clients such as blender. The opencolladavalidator also works, so dae files can still be validated if it is used.

DAEValidator was touted as a replacement for opencolladavalidator, but the version in the tree is not able to check the schemas for dae files. The other functions it has for checking the links and unique ids and sids still work.

The official upstream has had no commits for the last two years, and there is a more recent release at https://github.com/RemiArnaud/OpenCOLLADA/releases by one of the main authors, but the DAEValidator there has not been touched there either.

I searched both but could not find the problem upstream, searching for DAEValidator and parser did not return any similar issues. I am tring to modify http://xmlsoft.org/examples/index.html#parse2.c to determine whether it is the collada schema file that has an error, or libxml2 itself, and then post a bug upstream with the appropriate package.

I don't see this as a blocking bug, because it has likely been present for over a year and nobody has noticed. I suspect most clients only link against the other opencollada libraries and use them to read and write to dae files, and do not use either validator.