You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openoffice.apache.org by bu...@apache.org on 2012/07/24 20:07:10 UTC
[Bug 120359] New: ScriptProviderForooRexx.oxt cannot be successfully
installed with unopkg on MacOSX 3.4.0, 3.4.1
https://issues.apache.org/ooo/show_bug.cgi?id=120359
Priority: P3
Bug ID: 120359
Assignee: ooo-issues@incubator.apache.org
Summary: ScriptProviderForooRexx.oxt cannot be successfully
installed with unopkg on MacOSX 3.4.0, 3.4.1
Severity: normal
Issue Type: DEFECT
Classification: Application
OS: Mac OSX, all
Reporter: rony@apache.org
Hardware: All
Status: CONFIRMED
Version: AOO 3.4.0
Component: code
Product: installation
Report copied from the email on the developer list.
Problem exists in the rc of MacOSX (en-US), r1364591 AOO 3.4.1, as of
2012-07-17, as well, hence filing a bug!
In the case the Java code for interfacing ooRexx with AOO is relevant, here a
link to the source:
- jar with sources:
<http://bsf4oorexx.svn.sourceforge.net/viewvc/bsf4oorexx/tags/release-410.20120618/ScriptProviderForooRexx-source.jar?view=log>
- individual Java source files starting at:
<http://bsf4oorexx.svn.sourceforge.net/viewvc/bsf4oorexx/tags/release-410.20120618/com/sun/star/script/framework/provider/oorexx/>
-------- Original Message --------
Subject: MacOSX: problems deploying an extension in shared mode
Date: Sun, 22 Jul 2012 14:07:28 +0200
From: Rony G. Flatscher (Apache) <ro...@apache.org>
Reply-To: ooo-dev@incubator.apache.org
To: ooo-dev@incubator.apache.org
In the context of creating a new version of BSF4ooRexx for MacOSX as well
(<http://sourceforge.net/projects/bsf4oorexx/files/GA/BSF4ooRexx-410.20120618-GA/ooRexx411WithBSF4ooRexx-410.20120618-i386-MacOSX.pkg.zip/download>)
the automatic installation of an oxt-extension to AOO 3.4.0 to add ooRexx as a
macro language
directly to AOO, there are errors with the MacOSX version.
If you download the package from the above link you'll get ooRexx and
BSF4ooRexx for MacOSX in
32-Bit (as OOo is still 32-bit on MacOSX) installed and both ooRexx and
BSF4ooRexx (a Rexx function
package camouflaging Java as the dynamically typed ooRexx) are operational.
Unfortunately, the OOo extension named "ScriptProviderForooRexx.oxt" cannot be
added to the MacOSX
AOO 3.4 installation using "unopkg"! Here a few infos to the locations and the
scripts that are run
as sudo with the error message:
wu114123:sources rony$ *ls -al
/Applications/OpenOffice.org.app/Contents/program/unopkg**
lrwxr-xr-x@ 1 rony admin 10 Apr 19 08:28
/Applications/OpenOffice.org.app/Contents/program/unopkg -> unopkg.bin
-r-xr-xr-x@ 1 rony admin 13568 Apr 19 08:28
/Applications/OpenOffice.org.app/Contents/program/unopkg.bin
wu114123:sources rony$ *ls -al
/System/Library/Frameworks/BSF4ooRexx.framework/Libraries/ScriptProviderForooRexx.oxt*
-rwxrwxrwx 1 root wheel 330778 Jun 15 17:24
/System/Library/Frameworks/BSF4ooRexx.framework/Libraries/ScriptProviderForooRexx.oxt
wu114123:sources rony$ *sudo
/Applications/OpenOffice.org.app/Contents/program/unopkg add --shared
/System/Library/Frameworks/BSF4ooRexx.framework/Libraries/ScriptProviderForooRexx.oxt*
*ERROR: Error binding package:
vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/Qpgmug_/ScriptProviderForooRexx.oxt*
Cause: an error occured during file opening
unopkg failed.
There is no directory named "Qpgmug_" in the shared cache directory; not sure
why.
---
Trying to do the same from AOO's "Tools -> Extension Manager" is not successful
either, if intending
to install for "All users" with the scarce error message "an error occured
during file opening".
However adding this extension via AOO's "Tools -> Extension Manager" for "Only
for me" works o.k.!
Restarting AOO, and the extension is available and operational allowing ooRexx
to be used as a macro
language!
Using the user extension has another irregularity: if using for the first
time in a totally
fresh AOO session "Tools -> Macros -> Run Macro" and then executing any
ooRexx macro will yield
an error ("unable to load language"). However, if first doing a "Tools ->
Macros -> Organize
Macros -> ooRexx" and editing any ooRexx macro and running it via the edit
window menu, ooRexx
can be later found via "Tools -> Macros -> Run Macro" as well.
[Using the oxt-extension on Windows and Linux with AOO, OOo, LO works in shared
mode, and AFAIK
there are no anomalities that I know of.]
Any ideas, what might be wrong, what I could do?
[To duplicate: just install the MacOSX package and then run the above commands
from a command line
to see for yourself.]
TIA for any hints, ideas and suggestions,
---rony
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 120359] ScriptProviderForooRexx.oxt cannot be successfully
installed with unopkg on MacOSX 3.4.0, 3.4.1
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=120359
--- Comment #2 from Andre <aw...@googlemail.com> ---
See bug 119272 for another representation of this kind of problem.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 120359] ScriptProviderForooRexx.oxt cannot be successfully
installed with unopkg on MacOSX 3.4.0, 3.4.1
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=120359
--- Comment #5 from rony@apache.org ---
Created attachment 79989
--> https://issues.apache.org/ooo/attachment.cgi?id=79989&action=edit
AOO extension (script provider for the ooRexx language)
This extension can only be installed in user mode on a MacOSX, but not in
"shared" mode, even if running unopkg as superuser.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 120359] ScriptProviderForooRexx.oxt cannot be successfully
installed with unopkg on MacOSX 3.4.0, 3.4.1
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=120359
Andre <aw...@googlemail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |awf.aoo@googlemail.com
--- Comment #1 from Andre <aw...@googlemail.com> ---
One possible reason for this problem might be that in order to install an
extensions shared, you need superuser/admin access rights. This is currently
not supported by AOO outside the installer. I am more surprised that it works
on Windows and Linux than that it does not work on MacOSX.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 120359] ScriptProviderForooRexx.oxt cannot be successfully
installed with unopkg on MacOSX 3.4.0, 3.4.1
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=120359
rony@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rony@apache.org
--- Comment #6 from rony@apache.org ---
At ApacheCon Europe it has turned out that the extension in question can be
successfully installed for a user.
However running unopkg as sudo and trying to install in shared mode yields the
reported errors/problems.
The oxt-file was just uploaded, such that this can be tested without a need to
install the full BSF4ooRexx package.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 120359] ScriptProviderForooRexx.oxt cannot be successfully
installed with unopkg on MacOSX 3.4.0, 3.4.1
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=120359
--- Comment #4 from rony@apache.org ---
Ah, forgot to point out: this installation is carried out under the control of
the BSF4ooRexx Iceberg installer. At the point when unopkg gets invoked to
install the oxt as a shared extension, the credentials are those of sudo such
that all rights should be available to unopkg to do whatever it needs to do.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 120359] ScriptProviderForooRexx.oxt cannot be successfully
installed with unopkg on MacOSX 3.4.0, 3.4.1
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=120359
--- Comment #9 from rony@apache.org ---
A question ad your remark to restart AOO in sudo mode to have it clean up the
tmp directory: how could one possibly do that from the command line? The
package is added using unopkg from the command line and causes an instance of
AOO to be created and lingering.
If there was a command line argument to soffice for quitting AOO, then I could
follow your advice.
Or, is there maybe some undocumented possibility to do that? If so, then I
would be able to follow your advice.
--
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.
[Bug 120359] ScriptProviderForooRexx.oxt cannot be successfully
installed with unopkg on MacOSX 3.4.0, 3.4.1
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=120359
--- Comment #3 from rony@apache.org ---
Andre, thank you for your feedback!
However, the postflight script runs unopkg via sudo, such that all rights
should be available to unopkg to create any directory or copy any files. The
installation in addition adds ooRexx sample scripts to the shared AOO locations
successfully.
Running the unopkg command with sudo from the command line as reported, does
not work either.
I am pretty sure, that in the past (OOo 3.2?) the installation as a shared
extension worked on MacOSX.
---
Ad Linux: here running unopkg via sudo works.
Ad Windows: here running elevated works.
---
If there is anything else I could provide, please let me know. On the MacOSX I
am using the Iceberg installer, if that makes a difference (it should not as
the postflight script runs unopkg explicitly via sudo).
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 120359] ScriptProviderForooRexx.oxt cannot be successfully
installed with unopkg on MacOSX 3.4.0, 3.4.1
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=120359
--- Comment #8 from rony@apache.org ---
The reported anomality when executing Rexx scripts may be linked to executing
the scripts on the wrong thread, cf.
<https://issues.apache.org/ooo/show_bug.cgi?id=124170> (there one finds
instructions how to test this with a debug version of the oxt, that simply uses
a JDialog for popups, which fails, when started on the wrong thread).
--
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.
[Bug 120359] ScriptProviderForooRexx.oxt cannot be successfully
installed with unopkg on MacOSX 3.4.0, 3.4.1
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=120359
jsc@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jsc@apache.org
--- Comment #7 from jsc@apache.org ---
I have installed the ScriptProviderForooRexx.oxt in a AOO 4.0 dev version on my
MacOs 10.7.5 system. I installed for all users and I am in the admin group. I
don't use sudo because this causes a problem with a tmp directory in the user
profile. The tmp directory can't be deleted.
Can you please try to install it with a user with admin rights. Or with sudo
unopkg ... but then please start the office also with sudo directly after the
installation. during the next office start the tmp directory gets synchronized
and deleted.
There is indeed room for improvements but I don't see that somebody will work
on this. The whole extension deployment framework should be reworked to remove
some complexity.
--
You are receiving this mail because:
You are the assignee for the bug.