Stephan Bergmann píše v Po 13. 08. 2012 v 18:01 +0200:
As Petr found out, if you first run LO 3.6.1, then some old LO 3.5.x
(making use of share/prereg/bundled), then LO 3.6.1 again, all on the
same UserInstallation, it can still happen that LO 3.6.1 refuses to
start (as LO 3.5.x copied potentially broken data to
user/extensions/bundled but did not touch
user/extensions/bundled/buildid, so that LO 3.6.1 would not detect that
it needs to remove the potentially poisonous data again).
<http://cgit.freedesktop.org/libreoffice/core/commit/?id=e9631f40ee49a244b6c6816e5cfb36814b9bafba>
"fdo#53006: And detect LO downgrading scenarios..." addresses that by
adding yet another pirouette (even though one could argue that such
downgrading scenarios never worked by design, anyway). Between Petr and
me, we have seen it to be effective for both Linux and Windows (master,
at least). Please review and consider for backporting to libreoffice-3-6.
It works fine. It is great that you have found this solution. I have
pushed it into the 3-6 branch.
Thanks a lot for coping with this annoying bug. I keep my finger
crossed.
Best Regards,
Petr
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.