Package: mutt Version: 1.5.24-1+b1 Severity: normal I'm starting to get ready for 1.6.0, and was looking through the patches in the Debian package.
These patches appear to have already fixed in upstream, in a different way. I think it would be good to drop these patches to make sure. If there is still an issue, please open a new ticket, but right now upstream is considering these issues resolved: * misc/fix-configure-test-operator.patch This can be dropped and Debian ticket 759013 closed. The patch file was an incorrect fix. The correct fix was committed upstream in 80186ee6eb57 and released in 1.5.24. * upstream/531430-imapuser.patch Fixed in https://dev.mutt.org/trac/ticket/3240 7 years ago. * upstream/543467-thread-segfault.patch Fixed in https://dev.mutt.org/trac/ticket/3335 5 years ago. * upstream/548577-gpgme-1.2.patch Fixed in https://dev.mutt.org/trac/ticket/3300 3 years ago. * upstream/553321-ansi-escape-segfault.patch Fixed in https://dev.mutt.org/trac/ticket/3371 6 years ago. * upstream/603288-split-fetches.patch Closed/invalid at https://dev.mutt.org/trac/ticket/3459 3 years ago. If this really is still an issue, please open a ticket. * upstream/611410-no-implicit_autoview-for-text-html.patch Fixed in https://dev.mutt.org/trac/ticket/3496 3 years ago. * upstream/771125-CVE-2014-9116-jessie.patch This one is fine to leave in. It offers further protection. However, officially https://dev.mutt.org/trac/ticket/3716 was fixed and closed. Also, just a reminder that these other Debian tickets were fixed in 1.5.24 and it would be great if you could close them out: * 742627 * 759013 * 711511 Behavior change. $mail_check_recent controls this now. * 751476 * 772782 * 774666 * 775199 * 800780 The warning is new, but the behavior has not changed. * 743744 * 797923 * 537694 This looks like it was accidentally re-opened. It wasn't fixed in 1.5.24. * 606742 * 658324 Lastly, these tickets have been fixed and will be in the next release: * 677687 * 741147 * 434235 * 701013
