Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: Thomas Perale <thomas.perale@mind.be>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/mutt: bump version to 2.2.16
Date: Fri, 15 May 2026 19:46:40 +0200	[thread overview]
Message-ID: <20260515174640.530418-1-thomas.perale@mind.be> (raw)
In-Reply-To: <20260504162929.41045-1-peter@korsgaard.com>

In reply of:
> Bugfix release fixing crash / NULL pointer access issues and gsasl
> authentication compatibility with Microsoft servers.
> 
> Mutt 2.2.14 was released on February 20, 2025.  This is a bug-fix release,
> fixing a couple possible crashes, in GPGME and with IMAP when logging out,
> and correcting a small issue with unnecessary encoding of "." in attachment
> names (2231 encoding).
> 
> Mutt 2.2.15 was released on October 2, 2025.  This is a bug-fix release,
> fixing an IMAP search/limit bug, a compilation issue, and containing a
> workaround for gsasl SMTP authentication issues with some MS servers.  A few
> parts of the documentation were also improved.
> 
> Mutt 2.2.16 was released on November 22, 2025.  This is a bug-fix release,
> fixing a resource leak when compiled with OpenSSL/LibreSSL, which could
> eventually result in new connections failing.
> 
> http://www.mutt.org/news.html
> 
> The 2.2.16 release is not available on bitbucket, so change to the official
> ftp.mutt.org location instead.
> 
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

Applied to 2025.02.x & 2026.02.x. Thanks

> ---
>  package/mutt/mutt.hash | 2 +-
>  package/mutt/mutt.mk   | 4 ++--
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/package/mutt/mutt.hash b/package/mutt/mutt.hash
> index 72c7924e9b..4fd71fd6ab 100644
> --- a/package/mutt/mutt.hash
> +++ b/package/mutt/mutt.hash
> @@ -1,3 +1,3 @@
>  # Locally calculated
> -sha256  eb23faddc1cc97d867693f3a4a9f30949ad93765ad5b6fdae2797a4001c58efb  mutt-2.2.13.tar.gz
> +sha256  1d3109a743ad8b25eef97109b2bdb465db7837d0a8d211cd388be1b6faac3f32  mutt-2.2.16.tar.gz
>  sha256  732f24b69a6c71cd8e01e4672bb8e12cc1cbb88a50a4665e6ca4fd95000a57ee  GPL
> diff --git a/package/mutt/mutt.mk b/package/mutt/mutt.mk
> index 9a6be6d4a0..503f2d283e 100644
> --- a/package/mutt/mutt.mk
> +++ b/package/mutt/mutt.mk
> @@ -4,8 +4,8 @@
>  #
>  ################################################################################
>  
> -MUTT_VERSION = 2.2.13
> -MUTT_SITE = https://bitbucket.org/mutt/mutt/downloads
> +MUTT_VERSION = 2.2.16
> +MUTT_SITE = http://ftp.mutt.org/pub/mutt
>  MUTT_LICENSE = GPL-2.0+
>  MUTT_LICENSE_FILES = GPL
>  MUTT_CPE_ID_VENDOR = mutt
> -- 
> 2.47.3
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2026-05-15 17:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-04 16:29 [Buildroot] [PATCH] package/mutt: bump version to 2.2.16 Peter Korsgaard
2026-05-04 17:18 ` Julien Olivain via buildroot
2026-05-15 17:46 ` Thomas Perale via buildroot [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260515174640.530418-1-thomas.perale@mind.be \
    --to=buildroot@buildroot.org \
    --cc=peter@korsgaard.com \
    --cc=thomas.perale@mind.be \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox