For both sasview and sasdata, there's a loader test failing due to changes in libxml2. (The code moved from sasview to sasdata upstream but there's no release removing it from sasview yet, hence the duplication)

The upstream tests fail with libxml2 from unstable (2.12).
The patched tests fail with libxml2 in testing (2.9).

The migration autopkgtests therefore fail because they are not attempted with the newer libxml2. libxml2 also doesn't look like it will migrate any time soon (#1073508).

The xsd [1] for recognising partly broken cansas files is to blame - the multiple xsd:any entries in it make it ambiguous.

[1] sasdata/dataloader/readers/schema/cansas1d_invalid_v1_0.xsd

A test to run outside of the test harness is:

xmllint --noout \
  --schema sasdata/dataloader/readers/schema/cansas1d_invalid_v1_0.xsd \
  test/sasdataloader/data/cansas1d_notitle.xml

A namespace warning is OK; a "content model is not determinist" error or a "Schemas validity error" is not.



--
Stuart Prescott   http://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer  http://www.debian.org/       stu...@debian.org
GPG fingerprint   90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7

Reply via email to