Issue 99249 - unopkg fails to install extensions from command line
Summary: unopkg fails to install extensions from command line
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOO310m1
Hardware: Unknown Windows, all
: P3 Trivial (vote)
Target Milestone: OOo 3.1
Assignee: joerg.skottke
QA Contact: issues@framework
URL:
Keywords: regression
Depends on:
Blocks: 95768 98990
  Show dependency tree
 
Reported: 2009-02-16 06:31 UTC by Oliver Brinzing
Modified: 2009-03-18 12:36 UTC (History)
1 user (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 Oliver Brinzing 2009-02-16 06:31:37 UTC 
- install oo 3.1m1 (complete)
- open cmd
- c:
- cd "program files\ooo-dev 3\program"
- unopkg add c:\myextension.oxt --shared --verbose
- nothing happens

or simply try "unopkg --help" ...
Comment 1 Olaf Felka 2009-02-16 07:42:10 UTC 
@ jsk: Please have a look. Might be a 3.1 stopper
Comment 2 joerg.skottke 2009-02-16 09:43:40 UTC 
Confirmed, unopkg list --shared does not list the newly added extension. 
However, the Extension Manager does. 
Installing and removing the extension using unopkg works, though.

Being a regression (keyword set) this issue justifies for a 3.1 target. However,
an easy workaround is available (use Extension Manager, start unopkg gui). As
this is a minor problem i set the target to 3.2.
Comment 3 Oliver Brinzing 2009-02-16 12:39:22 UTC 
> start unopkg gui)

the workaround you mention is ok for developers, but not usable if you want
to deploy oo 3.1 (configured via extension's) for some hundred users ...
Comment 4 joachim.lingner 2009-02-16 13:21:45 UTC 
The bug causes in other cases, for example pdfimport.oxt, that unopkg returns
while the process unopkg.bin and unopkg.exe still run. The extension is then not
installed.
Comment 5 joachim.lingner 2009-02-17 11:07:15 UTC 
.
Comment 6 joachim.lingner 2009-02-23 16:03:35 UTC 
@jsk: Please verify.
Comment 7 Oliver Brinzing 2009-03-01 15:41:40 UTC 
seems not to be fixed in m3
Comment 8 joerg.skottke 2009-03-03 08:14:30 UTC 
@brinzing: The fix ins in CWS jl117. It should be in m4, m5 at the latest.
Comment 9 joerg.skottke 2009-03-03 08:27:16 UTC 
I'm not certain that i like the outcome:

C:\test\extensions\features\input\extensible_help>"c:\Program
Files\Sun\StarOffice 9\program\unopkg" add --shared extensible_help_en_de.oxt
????????????????????????????????????????????????????????????????????????????????
?????????????????????????????????????????>??????????????????????????????????????
????????????????????????????????????????????????????????????????????????
C:\test\extensions\features\input\extensible_help>

This is new, afaik.
Comment 10 joerg.skottke 2009-03-03 08:38:03 UTC 
Setting owner to JL
Comment 11 joachim.lingner 2009-03-03 09:25:46 UTC 
This output is caused by the help linker which is a different issue. See issue
98680.
Comment 12 joachim.lingner 2009-03-03 09:26:29 UTC 
.
Comment 13 joerg.skottke 2009-03-04 09:47:19 UTC 
Accepted. Setting verified.
Comment 14 Oliver Brinzing 2009-03-13 17:24:49 UTC 
seems to be fixed in oo 3.1m5

but now there is anoher problem:

echo yes | unopkg add myExtension.oxt

should automatically accept the licence agreement on windows systems
but this seems not work any more - is it a regression ?
Comment 15 joerg.skottke 2009-03-18 12:36:35 UTC 
Help is shown, installation with --shared --verbose results in a "unopkg done."
statement.

Closing