I don't really like upstreams that change config format without handling the situation with grace, but this is not something we can solve, and doing such change during a Fedora version change is the best moment to do so.

+1

+1

+1 for the Change

I don't really like upstreams that change config format without handling the situation with grace, but this is not something we can solve, and doing such change during a Fedora version change is the best moment to do so.

Yeah, a major version upgrade is the best time we can provide. We can probably also work something up with the systemd units to validate that the configuration is compatible with 2.4 before attempting to actually start the service, if it doesn't fail gracefully on its own.

We can probably also work something up with the systemd units to validate that the configuration is compatible with 2.4 before attempting to actually start the service, if it doesn't fail gracefully on its own.

Shouldn't this be part of the change proposal?

Shouldn't this be part of the change proposal?

I'm not sure why I wrote "we" (meaning "The Fedora Project") there. That was ambiguous and implied that I am involved in the Change.

I meant to say that I am willing to help work through that if needed.

fyi, when trying to start dovecot 2.4.x with 2.3.x style configuration it will fail with:
doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 90: The first setting must be dovecot_config_version

2.3.x configuration does not use dovecot_config_version variable, for 2.4.x it is strict requirement. Anyway 2.4 is not just about different variable names, but overall syntax and sections are incompatible, so there is no chance that 2.4 would start with 2.3 configuration and just don't work.

+1

After a week:
APPROVED (+4, 0, 0)

Announced: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/4EHEV57OLAUEYPABK75J6QXZKPSRWXQR/