Thanks @dobedobedo, I ran the simplified version to make the correction:
sudo chmod -R 755 /opt/agisoft/metashape-pro/ /usr/share/licenses/agisoft-metashape-pro/licenses/
Git Clone URL: | https://aur.archlinux.org/agisoft-metashape-pro.git (read-only, click to copy) |
---|---|
Package Base: | agisoft-metashape-pro |
Description: | Phtogrammetric processing of digital images and 3D spatial data generation software. Professional edition |
Upstream URL: | https://www.agisoft.com/ |
Licenses: | |
Provides: | |
Replaces: | |
Submitter: | dobedobedo |
Maintainer: | dobedobedo |
Last Packager: | dobedobedo |
Votes: | 0 |
Popularity: | 0.000000 |
First Submitted: | 2020-03-10 05:20 |
Last Updated: | 2021-01-05 04:49 |
Thanks @dobedobedo, I ran the simplified version to make the correction:
sudo chmod -R 755 /opt/agisoft/metashape-pro/ /usr/share/licenses/agisoft-metashape-pro/licenses/
I updated the post-upgrade script to fix the permission issue. Please update.
Having permission issues after upgrade. Output from upgrade had many permission warnings, example of top warning:
warning: directory permissions differ on /opt/agisoft/metashape-pro/
filesystem: 755 package: 700
When I try to run the program:
$ agisoft-metashape-pro
/usr/bin/agisoft-metashape-pro: line 2: /opt/agisoft/metashape-pro/metashape.sh: Permission denied
Updating permissions to match system allowed the program to run as expected.
Check the forum thread here:
https://www.agisoft.com/forum/index.php?topic=10943.0
There is a workaround for installing external python modules.
Hi @theodore, yes I got the same error message on my Arch WSL. Haven't tried it on my Manjaro machine as I'm away from it at the moment, but the python module installation worked on my another Ubunt 18.04 workstation.
I tried manually compile the pyOpenSSL module into the agisoft python packages directory, but didn't change anything. May need to recompile the python with libssl option. Hope that Agisoft can provide some solutions soon.
Hi @dobedobedo, I've seen this thread on the agisoft forum when I was looking for a solution on my own and I was hoping that it was only ubuntu related since as they say the current workaround was to downgrade the ubuntu instalation. However it seems that apparently it is not. In any case thanks for commenting there.
So I assume that you are also getting the same error when you run the command, right?
Hi @theodore, I suspect that the Metashape built-in python doesn't recognise the system openssl implementation. The same thing seems happening on Ubuntu 20.04 according to the forum posts.
I already post the errors on their official forum https://www.agisoft.com/forum/index.php?topic=10943.0 to see if there's a solution for this. You can also add some of your details there.
@dobedobedo yes I've used the python in the metashape-pro path not with the --user
flag though. In any case I've tried your suggested commands and I am still getting the error regarding the ImportError: cannot import name 'HTTPSHandler'
Actually this is the complete error message:
$ LD_LIBRARY_PATH=/opt/agisoft/metashape-pro/python/lib /opt/agisoft/metashape-pro/python/bin/python3.5 -m pip install --user pillow
Traceback (most recent call last):
File "/opt/agisoft/metashape-pro/python/lib/python3.5/runpy.py", line 174, in _run_module_as_main
mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
File "/opt/agisoft/metashape-pro/python/lib/python3.5/runpy.py", line 133, in _get_module_details
return _get_module_details(pkg_main_name, error)
File "/opt/agisoft/metashape-pro/python/lib/python3.5/runpy.py", line 109, in _get_module_details
__import__(pkg_name)
File "/opt/agisoft/metashape-pro/python/lib/python3.5/site-packages/pip/__init__.py", line 16, in <module>
from pip.vcs import git, mercurial, subversion, bazaar # noqa
File "/opt/agisoft/metashape-pro/python/lib/python3.5/site-packages/pip/vcs/subversion.py", line 9, in <module>
from pip.index import Link
File "/opt/agisoft/metashape-pro/python/lib/python3.5/site-packages/pip/index.py", line 30, in <module>
from pip.wheel import Wheel, wheel_ext
File "/opt/agisoft/metashape-pro/python/lib/python3.5/site-packages/pip/wheel.py", line 39, in <module>
from pip._vendor.distlib.scripts import ScriptMaker
File "/opt/agisoft/metashape-pro/python/lib/python3.5/site-packages/pip/_vendor/distlib/scripts.py", line 14, in <module>
from .compat import sysconfig, detect_encoding, ZipFile
File "/opt/agisoft/metashape-pro/python/lib/python3.5/site-packages/pip/_vendor/distlib/compat.py", line 66, in <module>
from urllib.request import (urlopen, urlretrieve, Request, url2pathname,
ImportError: cannot import name 'HTTPSHandler'
Hi @theodore, did you execute the python which belongs to metashape-pro? The path of metashape-pro python is /opt/agisoft/metashape-pro/python/bin/python3.5
.
Besides, you need to use --user
when executing pip
since we would like to avoid messing up the python modules with root permission.
The correct way to install external modules would like run commands like:
/opt/agisoft/metashape-pro/python/bin/python3.5 -m pip install --user python_module_names
If you encounter the error message
error while loading shared libraries: libpython3.5m.so.1.0: cannot open shared object file: No such file or directory
then add the path prefix in the command:
LD_LIBRARY_PATH=/opt/agisoft/metashape-pro/python/lib /opt/agisoft/metashape-pro/python/bin/python3.5 -m pip install --user python_module_names
Hi, I am trying to install an external module according to this https://agisoft.freshdesk.com/support/solutions/articles/31000136860-how-to-install-external-python-module-to-metashape-professional-package but I am getting the ImportError: cannot import name 'HTTPSHandler' error. Then I've tried to install the openssl098 package (https://aur.archlinux.org/packages/openssl098/), but I am still getting the same error message. Any idea how to solve the issue?
Pinned Comments
dobedobedo commented on 2020-09-08 02:42
Check the forum thread here:
https://www.agisoft.com/forum/index.php?topic=10943.0
There is a workaround for installing external python modules.
dobedobedo commented on 2019-10-01 15:23
Run the following command to activate the product
NOTE: the number after "--activate" is your node-locked license