Hello everyone! Today i had nice experience with VDSM RPMs building and actually found some minor problem.
VDSM RPM building process includes call to schema_to_html.py which generates vdsm-api.html from vdsm-api.yml Internally that script parses yml file using PyYAML module. The problem is that PyYAML module could be built in two flavours: with LibYAML or without it. And schema_to_html.py (or, to be more precise, vdsmapi.api module) assumes that it always built with LibYAML support. For some reason my local PyYAML was built without it and it gave some cryptic error during RPM build process. The worst thing is that i asked few people from vdsm team about that error and it was unexpected error for them. So i had to debug it and determine what goes wrong. Fix is pretty trivial and i pushed it to the gerrit ( https://gerrit.ovirt.org/#/c/68261/) But the problem is: "should it be ever fixed"? I see several options here. First of all it could be just documented somewhere like "if you have that issue, check that you have PyYAML with LibYAML". Another one option is to fix it in my way, by checking what functionality of PyYAML we have and choose it. Third option, as this script is being used only during build phase, just switch to the built-in loader and forget about that. Final option - just ignore that issue, it is so rare problem, that we should not spend time on it. What do you think?
_______________________________________________ Devel mailing list [email protected] http://lists.phx.ovirt.org/mailman/listinfo/devel
