01:23:21 <iprog4u> I meant to imply that you lot are smart not clear the room :)
11:29:19 <jfqd> jperkin: dovecot has a new 2.4 release. Would it be possible to have the old 2.3 branch additionally on trunk? Cause 2.4 is a massive upgrade with config changes! And an upgrade from 2.3 to 2.4 will break all dovecot installations.
11:32:25 <jperkin> ugh
11:34:10 <jfqd> jperkin: Yeah, I know
11:35:42 <jperkin> so, yes and no, we could add a new dovecot23 package, but you'll still have the problem that pkgin will upgrade you to 2.4 unless you specifically request the 23 version
11:36:03 <jperkin> and as you won't be able to install both simultaneously, I'm not really sure it helps much other than to delay the inevitable
11:36:43 <jfqd> jperkin: how can I dely it?
11:36:53 <jfqd> dely=delay
11:37:37 <jperkin> switch to 2024Q4 if you want to avoid any major upgrades
11:38:14 <jfqd> Or can I use pkgin keep?
11:38:34 <jperkin> no, that just selects which packages should not be autoremoved
11:39:47 <jperkin> we don't support the use-case where you hold a package at a specific version, it's just not a reliable way to manage software, all packages must always be consistent with each other
11:40:12 <jfqd> Ah ok. Phew. dovecot 24 ist a totally different product with massive changes. Something like ruby 1.9 to ruby 3.3.
11:43:05 <jfqd> Here is the list of config changes from 2.3 to 2.4: https://doc.dovecot.org/2.4.0/installation/upgrade/2.3-to-2.4.html
15:29:31 <rmustacc> /win 12