Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/postgresql: security bump version to 11.5
Date: Mon, 02 Sep 2019 21:00:09 +0300	[thread overview]
Message-ID: <87d0gia89i.fsf@tarshish> (raw)
In-Reply-To: <87ftley7fz.fsf@dell.be.48ers.dk>

Hi Peter,

On Mon, Sep 02 2019, Peter Korsgaard wrote:
>>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
>  > On Mon, Sep 02, 2019 at 01:15:09PM +0200, Peter Korsgaard wrote:
>  >> >>>>> "Bernd" == Bernd Kuhls <bernd.kuhls@t-online.de> writes:
>  >>
>  >> > Release notes: https://www.postgresql.org/about/news/1960/
>  >> > Switch POSTGRESQL_SITE to https.
>  >>
>  >> > Fixes CVE-2019-10208, CVE-2019-10209, CVE-2019-10210 & CVE-2019-10211.
>  >>
>  >> > Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
>  >>
>  >> Committed to 2019.02.x and 2019.05.x, thanks.
>
>  > Not in 2019.05.x as of 5d77d83bd3db.
>
> Sorry, I didn't push right away as I was considering if the wpewebkit
> patches were worthwhile to backport for 2019.05.x.
>
> I've pushed now.

But this postgresql bump is still not in 2019.05.x, which is now at
a236e8fb3647.

baruch

--
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

  reply	other threads:[~2019-09-02 18:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-09 15:59 [Buildroot] [PATCH 1/1] package/postgresql: security bump version to 11.5 Bernd Kuhls
2019-08-09 20:06 ` Thomas Petazzoni
2019-09-02 11:15 ` Peter Korsgaard
2019-09-02 13:52   ` Baruch Siach
2019-09-02 16:44     ` Peter Korsgaard
2019-09-02 18:00       ` Baruch Siach [this message]
2019-09-02 20:18         ` Peter Korsgaard

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=87d0gia89i.fsf@tarshish \
    --to=baruch@tkos.co.il \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox