Date: prev next · Thread: first prev next last
2019 Archives by date, by thread · List index


On 12.08.19 18:03, Paul Menzel wrote:

Dear Michael,


On 12.08.19 17:55, Michael Stahl wrote:
On 12.08.19 17:50, Paul Menzel wrote:
On 12.08.19 11:07, Michael Stahl wrote:

The file is indeed not there.

```
$ find . -name "*.rng"
./build/workdir/UnpackedTarball/liborcus/misc/OpenDocument-v1.2-os-schema.rng
./build/workdir/UnpackedTarball/raptor/tests/feeds/atom.rng
./build/workdir/UnpackedTarball/beanshell/docs/manual/foo.rng
./source/writerfilter/documentation/ooxml/model.rng
./source/xmloff/dtd/openoffice-2.0-schema.rng
```

are you using tarballs to build?

Yes, of course. ;-)

i believe the schema files are not in the tarballs, intentionally,
because they are not available with a FLOSS license.

so you can either disable the validation, build from a git clone, or
copy the schema directory manually...

Since when is that the case? At least until LibreOffice 6.1.5.2 it worked.

apparently since

commit 34dced99c33a97dab86c4538fa267ad4ad4fb41f
Author:     Thorsten Behrens <Thorsten.Behrens@CIB.de>
AuthorDate: Tue Aug 30 13:18:18 2016 +0200

    Ignore schema files for src tarball generation

which should be much older than 6.1?

So, tarball users should not run `make check`?

just disable the validation, --without-export-validation

actually i guess it would be ideal if the configure script would just check if the schemas are there or not, because it's a waste of time to run into the problem via test failures, see
https://gerrit.libreoffice.org/#/c/77383/ for a patch to do that.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.