On Tue, Feb 03, 2026 at 01:19:38PM +0300, Michael Tokarev wrote: > I weren't aware of this change. With this change in mind, yes, it is > a good reason NOT to push 2.4.2 to trixie. > > BTW, you can do it other way around: package 2.4.2 for trixie and revert > that particular pcre change to keep it compatible with the trixie > behavior. That'd be fun though.
"fun" yeah. It is definitely not an ideal situation. > > Given the above, I expect to continue backporting fixes for 2.4.1 while > > trixie is stable. Do you have any specific fixes you're looking for, or > > is this a general request? > > No, unfortunately not. I see my dovecot in trixie is crashing (rarely > but surely), and my questions to upstream about this got suggestions to > upgrade to the current version (2.4.2) only, so far. Yes, I'll try to > install 2.4.2 (debian package in forky built for trixie) just to see if > it changes this particular problem. Debugging were not successful so > far, either. What component is crashing for you? If you're able to get a stack trace, that might help track down a fix upstream, assuming the issue has been fixed in 2.4.2. It's entirely possible that it is, as they've fixed quite a few crashes. I've already got one crash fix queued for a trixie upload. (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1121000) I intend to go over the upstream changes looking for more that look worth pulling in. > Either way, I'm not uploading it just yet, let's see about the bug. > If it's fixed in 2.4.2, we can pick up that particular change to trixie. That would be ideal. If you do end up looking to upload to trixie-backports, I'd like to ask that you maintain the backport in a branch in https://salsa.debian.org/debian/dovecot/ noah
