Dovecot 1:2.4.1+dfsg1-5ubuntu1 is now in -proposed. This 2.4.x series includes a new config file format (which I'll be mentioning in the Questing Release Notes) which is not compatible with the old one.
C.f. https://doc.dovecot.org/2.4.0/installation/upgrade/2.3-to-2.4.html I notice the gsasl / dovecot autopkgtest is failing due to the following: 301s + dovecot -c /tmp/tmp.70vFN3geJb/d/dovecot.conf 301s doveconf: Fatal: Error in configuration file /tmp/tmp.70vFN3geJb/d/dovecot.conf line 1: The first setting must be dovecot_config_version 301s + grep -q Fatal: service(imap) access /tmp/tmp.70vFN3geJb/dovecot.log 301s grep: /tmp/tmp.70vFN3geJb/dovecot.log: No such file or directory So I'm guessing that the failure is indeed due to this config file change. Since the 2.2.2-2 update is specifically requiring Dovecot 2.4, I'll bet it includes a fix for this exact issue. I think once this version of gsasl is in -proposed, we can rerun the test run with triggers added for both dovecot and gsasl proposed versions and hopefully that should be enough to resolve this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2111860 Title: Please merge gsasl 2.2.2-2 from Debian experimental To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsasl/+bug/2111860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
