New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error attempting to install to linux mint 18.3 #155
Comments
I note this error
Likely not going to work for you until you update python or to a newer version of linux mint (19.x comes with python 3.6) |
This particular error during the installation seems to be caused by an old version of pip failing to install PyQt5. But as @techman83 notes, Maestral will not work with Python 3.5 unfortunately. You can install a newer version of Python alongside the system Python. For example, miniconda provides a good standalone distribution. |
I added the deadsnakes PPA to synaptic and installed python3.6 here. I tried again and got: So is there a way to download the PyQt5 first and try again? Will maestral work with python3.6 as I have it? |
After a bit more reading of things I tried yet again: Now it looks as if I am partially installed but getting new errors. Where do I go from here? I can confirm that Maestral itself is installed, as I get the help screen. Trying to invoke the gui returns an error about "xcb" not being loaded. |
I did a search on the error I encountered attempting to run the gui and ran with QT_DEBUG_PLUGINS=1 and got: Checking the libraries yielded: dhdurgee@Z560 ~/.local/lib/python3.6/site-packages/PyQt5/Qt/plugins/platforms $ ldd libqeglfs.so | grep "not found" So where do I get these missing dependencies? |
Located and installed missing xinerama library, gui now working. Will attempt to use. |
Attempt to link failed, log is: Where do I go from here? PS: I tried "maestral link" and got a similar error. I will do so again and paste it if it will be helpful. |
Going back to when I got it installed the log contains: ERROR: maestral 1.0.3 requires rubicon-objc>=0.3.1, which is not installed. I suspect this is the problem, but have no idea where the more current versions are available. Help. |
A web search revealed how to update requests and six, so pip3 list now shows: requests 2.23.0 This however did not solve the problem. Given this, here is the log from the command line version: At this point I believe I have everything installed correctly as documented, What did I miss? |
Could you post a list of all installed packages with Also, |
Mint 18.3 had installed 2.7.12 and 3.5.2 installed from their repositories. As you required 3.6 I had to see about installing it. I finally was able to install 3.6.10 by adding the deadsnakes PPA and using synaptic to install it. I followed your example of "pip3 install --update" to update requests and six to meet your requirements. I can only assume I need to update a few more for this to work. Thank you for your assistance. |
Those dependencies seem fine. Could you try explicitly uninstalling and reinstalling requests, as suggested on stackexchange? |
I just tried as suggested and see no change: What next? |
About the only other thing I can think of trying would be to uninstall python3.5 and see if that makes a difference. Is python3.6 completely backwards compatible with pythion3.5 code? I know that python3 and python2 are NOT compatible, so I have to ask. |
Please don’t do that! I don’t have any experience with Mint but all sort of things could go wrong when removing the system Python. There often are subtle non-backwards compatible changes. I suspect the continued error comes from some leftover file from the old requests installation. Googling the issue shows a whole lot of similar problems which do sometimes persist after updating requests. It’s difficult to debug for me without reproducing it. |
Understood. I will await further instructions from you when you have something I can try for you. Given you suspect a leftover file, would it help to zip up the requests-2.23.0 related files in site-packages and upload them here? I would think you could install a local copy and hopefully recreate the problem. |
I just noticed something looking at the traceback in requests.log that I missed. Why is the version in /usr/lib/python3/dist-packages/requests/ being called? This is the OLD 2.9.1 version! I suspect this is the problem, the question is why isn't the 2.23.0 that I installed being called? |
Possibly a stupid question, but the Wiki says a particular version of requests is needed and looking in the maestral-1.0.3.dist-info directory and inspecting the metadata files no such restriction is noted. Is this perhaps the problem, or just a documentation error? |
A web search turned up a reference to "usercustomize.py" in the python 3.6.3 documentation that could be added in my user site-packages directory. Could this be useful? I don't code python, so I can't guess or code even if it is useful. |
Yes, using an old version of requests is almost certainly the issue. But I don't understand why it's used, either. Other packages are correctly loaded from
Does it? The minimum requirement is given by the dropbox package itself as |
Stopping the daemon improved the situation, but I hit another package that had to be upgraded. Once I upgraded cryptography I was able to link my account. So it appears that the daemon was running with the old package imported and kept it even when an update was available. You are correct, the Wiki did not mention it. I guess I was remembering the notice I received when I installed your package. Regarding your package, does it have any problems dealing with symlinks? I had used them to link to files in their original locations until Dropbox started having a fit about this and I had to put the original in the Dropbox folder and symlink back to my Documents, Downloads, etc. Since your folder is named differently, can I simply uninstall the Dropbox client that isn't working right anyhow? Since it stared malfunctioning on 28 May I have stopped it and disabled autostart. I notice that your client did not preserve the timestamps of the files it retrieved from my online folder. Is this an error? Did I miss a setting? |
I don't know python, but given my experience perhaps you should consider reflecting the critical requirements of your entire dependencies tree in your top level maestral client package. That would have avoided the situation where I was able to start your daemon with packages that did not meet the requirements of the dropbox package. You might also want to inform the maintainer of the SecretStorage package that they need to add a required level to their use of the cryptography package, as the 1.2.3 level that came with my distro had to be upgraded for this to work. |
Possibly. When you pause and resume syncing, symlinks will be followed and changes will sync. However, depending on the platform, you may not get “live” syncing because file systems events may not be registered. I’ll be interested in hearing about your experience.
Yes, Maestral will work independently. Regarding dependencies, it is typically the responsibility of every package maintainer to track its own dependencies and minimum requirements. I do give a reference set in Since the install has been successful now, I’ll close this issue. If there are any other cases of missing dependencies, do let me know. |
unable to install to linux mint 18.3
python3 -m pip install --upgrade maestral[gui]
expected successful install, instead got following error:
Complete output from command python setup.py egg_info:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3.5/tokenize.py", line 454, in open
buffer = _builtin_open(filename, 'rb')
FileNotFoundError: [Errno 2] No such file or directory: '/tmp/pip-build-trbqdsma/PyQt5/setup.py'
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-trbqdsma/PyQt5/
You are using pip version 8.1.1, however version 20.1.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
dhdurgee@Z560 ~ $
I want t see if I can replace the dropbox client which does not want to work on my filesystem
maestral.log
The text was updated successfully, but these errors were encountered: