You are not logged in.
When I try and run /usr/bin/Meshroom I get the python Traceback:
Traceback (most recent call last):
File "/usr/lib/python3.7/site-packages/cx_Freeze/initscripts/__startup__.py", line 14, in run
module.run()
File "/home/john/AURpkgfiles/meshroom/meshroom/src/meshroom/setupInitScriptUnix.py", line 39, in run
File "meshroom/ui/__main__.py", line 10, in <module>
File "/home/john/AURpkgfiles/meshroom/meshroom/src/meshroom/meshroom/ui/app.py", line 12, in <module>
File "/home/john/AURpkgfiles/meshroom/meshroom/src/meshroom/meshroom/ui/components/scene3D.py", line 8, in <module>
File "/home/john/AURpkgfiles/meshroom/meshroom/src/meshroom/meshroom/ui/utils.py", line 6, in <module>
ImportError: cannot import name 'shiboken2' from 'PySide2' (/usr/lib/Meshroom-2019.1.0/lib/PySide2/__init__.pyc)
I've installed shiboken2 from python-shiboken2-5.13.0-4 which is in testing
and pyside2 from python-pyside2-5.13.0-2.
Has anyone any idea why PySide2 can't import the module?
Thanks
j.b.
Offline
[…] File "/home/john/AURpkgfiles/meshroom/meshroom/src/meshroom/setupInitScriptUnix.py", line 39, in run […]
Not sure about that tool in particular, but this looks like it's importing a script inside a PKGBUILD tree. Why is that?
What is the command you run, from which directory?
How did you install Meshroom?
Last edited by ayekat (2019-07-21 19:48:10)
Offline
I created /home/john/AURpkgfiles/meshroom/ and then
git clone from the meshroom AUR website.
I then did
cd meshroom
makepkg -si
and it installed the package binary.
Is this not the way to install an AUR package?
Offline
Does meshroom own any files under /home?
pacman -Ql meshroom
Offline
No, all the files are under /usr - viz.
/usr/bin/Meshroom
/usr/bin/meshroom_compute
/usr/bin/meshroom_photogrammetry
loads of libraries, *.pyc and *.qml files under:
/usr/lib/Meshroom-2019.1.0
some libraries under:
/usr/lib/qt
and finally:
/usr/share/meshroom/
/usr/share/meshroom/vlfeat_K80L3.SIFT.tree
So the installation dir was 'locked-in' during the compile stage. That dir no longer exists.
Offline
I've installed shiboken2 from python-shiboken2-5.13.0-4 which is in testing
and pyside2 from python-pyside2-5.13.0-2.
Do you have python2 installed ?
Have you tried building with testing repo disabled ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Yes, I have python2 installed but any python-based dependencies were installed using python3
and also meshroom is built using python3.
Do you mean the testing repository for meshroom? If so, the answer is no, I haven't tried to disable it.
The PKGBUILD file does not have a 'check' section in it so I don't know, and haven't investigated, what testing occurs
in the build. And I don't know if there is a '--disable-test' or equivalent option in the cmake configure phase.
Offline
Some build systems (including cmake) prefer python2 over python3 if both are present.
This can lead to a search for python2 modules when the code actually needs the python3 version and vice versa.
Try removing python2 or building in a clean chroot.
Do you mean the testing repository for meshroom? If so, the answer is no, I haven't tried to disable it.
The PKGBUILD file does not have a 'check' section in it so I don't know, and haven't investigated, what testing occurs
in the build. And I don't know if there is a '--disable-test' or equivalent option in the cmake configure phase.
You're using shiboken2 from [testing] , but pyside2 is not in [testing] repo . It is possible this is causing your problems.
By reverting from [testing] to stable repos, you can verify that possibility.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline