-
-
Notifications
You must be signed in to change notification settings - Fork 64
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
[macOS] maestral 1.3.1 compatibility with keyring: No module named 'keyring.backends.OS_X' #997
Comments
You can try installing an older version of keyring. IIRC, the "backend" rename from |
Closing this is not anything fixable on the Maestral side. Newer releases of keyring and maestral address this issue if they can be installed. |
@samschott I kinda forgot, what was the constraint we faced for older MacOS? Besides Qt GUI, that cannot work with Qt5 presently. Something like fsevents issue? Maybe it is possible to have it working with some limitations, depending on what SDK features that requires. |
If I remember correctly, there should be no fundamental constraint by Maestral itself. Installing Python and the Rather, the briefcase packing tool that I am using only support macOS 11 and later. I believe this makes it easier to target both Intel and Apple Silicon Macs. |
@samschott Anything Cocoa is likely not to work, even if it installs (i.e. pure Python code may install, but SDK won’t have what it expects). If there is an X11 / GTK3 version, there we have more chances IMO. |
@samschott Ah, The current |
It won't, I'm afraid. The FSEvents backend for watchdog fixes a several fundamental sync and performance issues from the previously used kqueue backend. The days of macOS 10.6 are numbered, as nice and stable as Snow Leopard was! |
I see. Well, it may be possible to reimplement the thing so that
If only Apple had opensourced complete sources for the OS, we would probably have everything we need by now :) Still, I routinely see cases when something builds and works on 10.5–10.6, but is broken on any later systems. (Which is usually caused by a disaster of libc++ and clangs: say, my 10.6 with libstdc++ has C++23 support, but macOS 12 does not.) |
This is probably unsupported, but maybe you could give an advice.
I have installed
maestral
1.3.1 on 10.6, and trying running it fails with:Indeed, there is no such naming:
Should I just patch in
macOS
instead? Or it will not work with a recentkeychain
, and I need to dig out some old version of it to make it work?The text was updated successfully, but these errors were encountered: