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


Now I tried "ooinstall -l ./install" in the toplevel dir and below you find my results :-( What are those files which cannot be found?

Christina


... languages en-US ...
... analyzing files ...
ERROR: The following files could not be found:
ERROR: File not found: dict-ar.oxt
ERROR: File not found: dict-bg.oxt
ERROR: File not found: dict-bn.oxt
ERROR: File not found: dict-de.oxt
ERROR: File not found: dict-gu.oxt
ERROR: File not found: dict-hi.oxt
ERROR: File not found: dict-lv.oxt
ERROR: File not found: dict-pt-pt.oxt
... cleaning the output tree ...
... removing directory /tmp/ooopackaging/i_161541321273155 ...


Am 14.11.2011 13:14, schrieb Michael Meeks:
Hi Christina,

On Mon, 2011-11-14 at 12:10 +0100, Chr. Rossmanith wrote:
I've commited all my recent changes locally, did a "git pull -r", "make
clean" and "make" - successful up to this point.
        Lovely :-)

  Then LibO tells me "Developers might prefer this way: make
dev-install -o build" but this command fails:
        Ah - it looks like the smoketest failed; personally I use:

        ooinstall -l /path/to/directory

        myself (with a sourced environment: . ./Env.Set.sh) - which is a quick
workaround for that. I'd use that to test your work&  send it in, I
imagine the smoketest problem is transient and fixed on master.

        Looking forward to your patch :-)

        Regards,

                Michael.



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.