Re: [REVIEW 3-6][REVIEW 3-6-0 1/3] fdo#51252 LO cannot start (reports runtime error with Visual C++ Runtime Library)

Stephan Bergmann <sbergman -AT- redhat.com>
Thu, 26 Jul 2012 18:17:09 +0200

On 07/26/2012 06:08 PM, Caolán McNamara wrote:

And lets remove, rather than fix, that bundled foo seeing as that's
twice now its tripped us up :-)

Indeed. It was a nice attempt at speeding up firststart, but I amconvinced that it is broken by design. Also, removing it saves us fromthe hassle of calling "unopkg sync" at instset creation time and/orduring installation (and why do we do the latter anyway---if we indeedstill do it, that is).


Stephan

Context

[REVIEW 3-6][REVIEW 3-6-0] fdo#51252 LO cannot start (reports runtime error with Visual C++ Runtime Library) · Stephan Bergmann
- Re: [REVIEW 3-6][REVIEW 3-6-0 1/3] fdo#51252 LO cannot start (reports runtime error with Visual C++ Runtime Library) · Caolán McNamara
  - Re: [REVIEW 3-6][REVIEW 3-6-0 1/3] fdo#51252 LO cannot start (reports runtime error with Visual C++ Runtime Library) · Stephan Bergmann
  - Re: [PUSHED 3-6][REVIEW 3-6-0 2/3] fdo#51252 LO cannot start (reports runtime error with Visual C++ Runtime Library) · Eike Rathke
    - Re: [PUSHED 3-6-0] fdo#51252 LO cannot start (reports runtime error with Visual C++ Runtime Library) · Petr Mladek
- Re: [REVIEW 3-6][REVIEW 3-6-0] fdo#51252 LO cannot start (reports runtime error with Visual C++ Runtime Library) · Fridrich Strba

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.