From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/dovecot: bump version to 2.3.9.2
Date: Sat, 4 Jan 2020 16:19:26 +0100 [thread overview]
Message-ID: <20200104161926.4f7b1e45@windsurf> (raw)
In-Reply-To: <20200104140824.2338592-1-bernd.kuhls@t-online.de>
On Sat, 4 Jan 2020 15:08:23 +0100
Bernd Kuhls <bernd.kuhls@t-online.de> wrote:
> Release notes:
> https://dovecot.org/pipermail/dovecot-news/2019-October/000419.html
> https://dovecot.org/pipermail/dovecot-news/2019-December/000423.html
> https://dovecot.org/pipermail/dovecot-news/2019-December/000425.html
> https://dovecot.org/pipermail/dovecot-news/2019-December/000427.html
>
> Please note that according to
> https://security-tracker.debian.org/tracker/CVE-2019-19722
> CVE-2019-19722 fixes a bug introduced in 2.3.9 so backporting this patch
> to older buildroot branches is not necessary.
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> ...-Do-not-build-static-test-iostream-s.patch | 30 +++++++++++++++++++
> package/dovecot/dovecot.hash | 2 +-
> package/dovecot/dovecot.mk | 6 +++-
> 3 files changed, 36 insertions(+), 2 deletions(-)
> create mode 100644 package/dovecot/0002-lib-ssl-iostream-Do-not-build-static-test-iostream-s.patch
Both applied, thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-01-04 15:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-04 14:08 [Buildroot] [PATCH 1/2] package/dovecot: bump version to 2.3.9.2 Bernd Kuhls
2020-01-04 14:08 ` [Buildroot] [PATCH 2/2] package/dovecot-pigeonhole: bump version to 0.5.9 Bernd Kuhls
2020-01-04 15:19 ` Thomas Petazzoni [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=20200104161926.4f7b1e45@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.