On Sun, Dec 11, 2022 at 10:17:19PM +0100, Salvatore Bonaccorso wrote: > Hi Antonio, > > On Sun, Dec 11, 2022 at 09:59:18PM +0100, Antonio Radici wrote: > > On Thu, Dec 01, 2022 at 10:05:14PM +0100, Salvatore Bonaccorso wrote: > > > Hi Antonio, > > > > > > On Wed, Nov 30, 2022 at 09:38:39AM -0800, Kevin J. McCarthy wrote: > > > > Note this was fixed in Mutt 2.2.8. See > > > > https://gitlab.com/muttmua/mutt/-/issues/428 for the Mutt bug report. > > > > > > > > This important fix is at: > > > > https://gitlab.com/muttmua/mutt/-/commit/48b6ea32e21db8b580cd3ca8c346c3e2c22756f6.patch > > > > > > > > There are two related commits, that may be of interest in backporting > > > > too, > > > > but aren't the cause of this segfault: > > > > https://gitlab.com/muttmua/mutt/-/commit/f0eb3586480c301b66657c7326b6546ef086c7f4.patch > > > > https://gitlab.com/muttmua/mutt/-/commit/b254f2fb44f994c48e2491adaf03d97d3c628283.patch > > > > > > There is an upcoming point release for bullseye on 17th of december, > > > can you pick those fixes for a stable update? > > > > > > Thanks for your work on mutt! > > > > Yes, I will have an updated package tomorrow evening (Mon Dec 12th) > > note that the time did pass this weekend for having fixes included in > the next bullseye-point release. I went ahead earlier with #1025716 > which got accepted the stable release managers. > > Hope this NMU was fine with you to get the fixes in time into the next > bullseye point release.
Sure that's no problem, I realized that just after my email was sent :)
