Skip to content
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

mbsync: update module for v1.5.0 #5884

Open
antonmosich opened this issue Sep 23, 2024 · 6 comments · May be fixed by #5918
Open

mbsync: update module for v1.5.0 #5884

antonmosich opened this issue Sep 23, 2024 · 6 comments · May be fixed by #5918

Comments

@antonmosich
Copy link
Contributor

isync had a new release v1.5.0 in August, and the update has been merged into nixpkgs master a few days ago (see NixOS/nixpkgs#331813). The update introduces several breaking changes, the details of which can be seen on https://sourceforge.net/projects/isync/files/isync/1.5.0/. See #3317 as well for an issue specific to one of those changes.

Maintainer ping: @KarlJoad

@KarlJoad
Copy link
Contributor

KarlJoad commented Sep 23, 2024

Looking at isync's change notes, this is what I see needs to be done on home-manager's end:

Is there anything I missed @antonmosich?

@antonmosich
Copy link
Contributor Author

Thank you for the quick response. Those are the changes I noticed as well. I have some other errors appear when testing, but I think those are due to configuration errors on my side.
I just didn't want to open a potentially incomplete PR, because I don't understand mbsync thoroughly enough.

@KarlJoad
Copy link
Contributor

Feel free to drop the other errors you are getting here. I have moved off of NixOS and home-manager, so I cannot as easily test as I could in the past. I would like to get as much as I can fixed at once rather than have many issues opened one at a time.

@antonmosich
Copy link
Contributor Author

I've looked into it and been able to fix it (although I think it could've been done better). The "Maildir Path cannot be nested into Inbox anymore" is the change that caused the errors. Now for my configuration it only shows the deprecation notice for SSLVersions.

@peterhoeg
Copy link
Collaborator

SSLType has also changed to TLSType

@KarlJoad KarlJoad linked a pull request Sep 30, 2024 that will close this issue
6 tasks
@KarlJoad
Copy link
Contributor

From my searching, the SSLVersions option is not an explicit option that can be used (You cannot say sslVersions = [ "TLSv1.2" ... ]; somewhere. Please correct me if I am wrong, and point me in the right direction. home-manager has changed significantly since I last looked at it.

From what I see, you must set TLSVersion in an extraConfig.account attrset, which means you must rename your option. I can always add a check to alert the user, but that's the most I can do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants