From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Maxim Kochetkov <fido_max@inbox.ru>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/postgresql: security bump version to 15.5
Date: Sun, 26 Nov 2023 22:45:08 +0100 [thread overview]
Message-ID: <20231126214508.GK3177259@scaer> (raw)
In-Reply-To: <20231123061500.984461-1-fido_max@inbox.ru>
Maxim, All,
On 2023-11-23 09:15 +0300, Maxim Kochetkov spake thusly:
> Release notes:
> https://www.postgresql.org/about/news/postgresql-161-155-1410-1313-1217-and-1122-released-2749/
>
> Fixes CVE-2023-5868, CVE-2023-5869, CVE-2023-5870.
>
> Signed-off-by: Maxim Kochetkov <fido_max@inbox.ru>
Applied to master, thanks.
Regards,
Yann E. MORIN.
> ---
> package/postgresql/postgresql.hash | 4 ++--
> package/postgresql/postgresql.mk | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/package/postgresql/postgresql.hash b/package/postgresql/postgresql.hash
> index 0640f883a7..4fc3bfcff0 100644
> --- a/package/postgresql/postgresql.hash
> +++ b/package/postgresql/postgresql.hash
> @@ -1,4 +1,4 @@
> -# From https://ftp.postgresql.org/pub/source/v15.4/postgresql-15.4.tar.bz2.sha256
> -sha256 baec5a4bdc4437336653b6cb5d9ed89be5bd5c0c58b94e0becee0a999e63c8f9 postgresql-15.4.tar.bz2
> +# From https://ftp.postgresql.org/pub/source/v15.4/postgresql-15.5.tar.bz2.sha256
> +sha256 8f53aa95d78eb8e82536ea46b68187793b42bba3b4f65aa342f540b23c9b10a6 postgresql-15.5.tar.bz2
> # License file, Locally calculated
> sha256 1a7d13c3ab31961b91ba256f77d6e82e0b54bf992253060fe93bdb5466df416a COPYRIGHT
> diff --git a/package/postgresql/postgresql.mk b/package/postgresql/postgresql.mk
> index b951b14aa0..3108fe65e1 100644
> --- a/package/postgresql/postgresql.mk
> +++ b/package/postgresql/postgresql.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -POSTGRESQL_VERSION = 15.4
> +POSTGRESQL_VERSION = 15.5
> POSTGRESQL_SOURCE = postgresql-$(POSTGRESQL_VERSION).tar.bz2
> POSTGRESQL_SITE = https://ftp.postgresql.org/pub/source/v$(POSTGRESQL_VERSION)
> POSTGRESQL_LICENSE = PostgreSQL
> --
> 2.40.1
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
>
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-11-26 21:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 6:15 [Buildroot] [PATCH 1/1] package/postgresql: security bump version to 15.5 Maxim Kochetkov
2023-11-26 21:45 ` Yann E. MORIN [this message]
2023-11-30 8:27 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2023-12-05 5:51 Maxim Kochetkov via buildroot
2023-12-05 9:41 ` Peter Korsgaard
2023-12-05 9:42 ` Maxim Kochetkov via buildroot
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=20231126214508.GK3177259@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=fido_max@inbox.ru \
/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