Issue 100909 - [Automation] Testscript fails to install extensions when calling unopkg
Summary: [Automation] Testscript fails to install extensions when calling unopkg
Status: CLOSED FIXED
Alias: None
Product: QA
Classification: Unclassified
Component: testscripts (show other issues)
Version: current
Hardware: All All
: P3 Trivial
Target Milestone: ---
Assignee: b.osi.ooo
QA Contact: issues@qa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-07 09:51 UTC by joerg.skottke
Modified: 2013-08-07 15:07 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description joerg.skottke 2009-04-07 09:51:48 UTC 
OOo310m9 - Automated tests:
- extensions/optional/e_extensions.bas
- extension/optional/e_publisher.bas

dump a "unopkg add ..." command to a shell to install extensions via the
function sExtensionCLI().
The function fails.
Comment 1 joerg.skottke 2009-04-07 11:51:38 UTC 
@TBO
Comment 2 b.osi.ooo 2009-04-20 13:16:57 UTC 
found culprint;
again something broken with URE_BOOTSTRAP -
is taken from running testtool process and not from ooo
see old issue i86718;
there should be a workaround available to prevent this, but unfortunately only
for OOo, not for other binaries.
Workaround for this would be to write a script everytime, that sets the right
URE_BOOTSTRAP variable...
Comment 3 b.osi.ooo 2009-04-20 13:30:26 UTC 
Not working: take an old testtool and execute:
shell
("/local/home/autotb/OOo_3.1.0_090320_unxlngi6_install/openoffice.org3/program/unopkg",1,"gui")
Result: no gui comes up, just an error on the console:
ERROR: cannot initialize UCB!
unopkg failed.

Workaround: Create uno.sh:
export
URE_BOOTSTRAP=file:///local/home/autotb/OOo_3.1.0_090320_unxlngi6_install/openoffice.org3/program/fundamentalrc
/local/home/autotb/OOo_3.1.0_090320_unxlngi6_install/openoffice.org3/program/unopkg
gui

and use shell comand:
shell ("/local/home/autotb/uno.sh",1,"gui")

@sb: Could we fix this the same way we did this for OOo, for all binaries?
       So that the wrong URE_BOOTSTRAP does not matter and we do not need to
workaround this?
       Or am I wrong that there was a fix for OOo in OOo and not only in our
testtool environment preventing this?
Comment 4 Stephan Bergmann 2009-04-20 13:52:37 UTC 
@tbo:  "Or am I wrong that there was a fix for OOo in OOo and not only in our
testtool environment preventing this?"  Yes, you are wrong.  For OOo itself, you
did the (only) change in testautomation, see
<http://qa.openoffice.org/issues/show_bug.cgi?id=86718#desc3>, so I would
suggest to do similarly for unopkg.
Comment 5 b.osi.ooo 2009-04-20 17:51:08 UTC 
Sending        optional/t_extension_manager_tools.inc
Transmitting file data .
Committed revision 271008.
Comment 6 b.osi.ooo 2009-10-06 13:43:57 UTC 
closing as integrated into master