Bug#1023599: mutt: FTBFS due to lack of gpgme-config since gpgme1.0 1.18.0-2

2022-11-12 Thread Kevin J. McCarthy
I've just released mutt 2.2.9, which I believe should fix this problem. -Kevin signature.asc Description: PGP signature

Bug#1023599: mutt: FTBFS due to lack of gpgme-config since gpgme1.0 1.18.0-2

2022-11-07 Thread Kevin J. McCarthy
On Mon, 7 Nov 2022 13:04:04 +0100 Vincent Lefevre wrote: The gpgme-config utility was removed in gpgme1.0 1.18.0-2 (because it needs gpg-error-config, which has been removed). As a consequence the use of --enable-gpgme to build Mutt yields an error: Just as a note, with Vincent's help, I've

Bug#992927: mutt: Mutt 2.1.2 is available, fixing a potential data-loss IMAP bug

2021-11-23 Thread Kevin J. McCarthy
On Tue, Nov 23, 2021 at 08:45:47PM +0100, Hannes von Haugwitz wrote: Is there any progress with this bug? Mutt 2.1.3 included the corrected sort commit referenced in my last email. So, for unstable/testing it would be nice to get 2.1.3 uploaded. For stable/oldstable I guess it rests in the

Bug#992927: mutt: Mutt 2.1.2 is available, fixing a potential data-loss IMAP bug

2021-09-08 Thread Kevin J. McCarthy
On Tue, Sep 07, 2021 at 08:20:49PM -0700, Kevin J. McCarthy wrote: I think the probability of users encountering that in practice is low. But if you're going through the effort of back-porting the fix, please wait and I'll commit a corrected fix tomorrow. This is still on a branch, waiting

Bug#992927: mutt: Mutt 2.1.2 is available, fixing a potential data-loss IMAP bug

2021-09-07 Thread Kevin J. McCarthy
Antonio, I was going through recent Mutt commits, and I realized my fix for this is not quite correct. The IMAP UID field is a 32-bit unsigned integer. I unfortunately modeled the new compare_uid() function after all the other ones use by Mutt for sorting, which just uses subtraction.