From: "Yoann Congal" <yoann.congal@smile.fr>
To: <asparmar@cisco.com>, <openembedded-core@lists.openembedded.org>
Cc: <xe-linux-external@cisco.com>
Subject: Re: [OE-core][scarthgap][PATCH v2] bind: Upgrade 9.18.44 -> 9.18.49
Date: Tue, 07 Jul 2026 12:19:26 +0200 [thread overview]
Message-ID: <DJS9H2DLIVVC.2DDDZVKTEK2TS@smile.fr> (raw)
In-Reply-To: <20260630060410.1203985-1-asparmar@cisco.com>
On Tue Jun 30, 2026 at 8:04 AM CEST, Ashishkumar Parmar X (asparmar - E INFOCHIPS PRIVATE LIMITED at Cisco) via lists.openembedded.org wrote:
> From: Ashishkumar Parmar <asparmar@cisco.com>
>
> This upgrade fixes CVE-2026-1519, CVE-2026-3039, CVE-2026-3592, CVE-2026-5946 and CVE-2026-5950.
>
> Changelog
> =========
> https://downloads.isc.org/isc/bind9/9.18.49/doc/arm/html/notes.html
That changelog contains:
| Notes for BIND 9.18.45
| Feature Changes
| Update requirements for system test suite.
| Python 3.10 or newer is now required for running the system test
| suite. The required Python packages and their version requirements
| are now tracked in the file bin/tests/system/requirements.txt. [GL
| #5690] [GL #5614]
Feature changes are not usually acceptable for stable. Can you justify
why this is the case here?
Thanks!
>
> Signed-off-by: Ashishkumar Parmar <asparmar@cisco.com>
> ---
> .../bind/{bind_9.18.44.bb => bind_9.18.49.bb} | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> rename meta/recipes-connectivity/bind/{bind_9.18.44.bb => bind_9.18.49.bb} (97%)
>
> diff --git a/meta/recipes-connectivity/bind/bind_9.18.44.bb b/meta/recipes-connectivity/bind/bind_9.18.49.bb
> similarity index 97%
> rename from meta/recipes-connectivity/bind/bind_9.18.44.bb
> rename to meta/recipes-connectivity/bind/bind_9.18.49.bb
> index d424edcb4e..723a09e739 100644
> --- a/meta/recipes-connectivity/bind/bind_9.18.44.bb
> +++ b/meta/recipes-connectivity/bind/bind_9.18.49.bb
> @@ -20,7 +20,7 @@ SRC_URI = "https://ftp.isc.org/isc/bind9/${PV}/${BPN}-${PV}.tar.xz \
> file://0001-avoid-start-failure-with-bind-user.patch \
> "
>
> -SRC_URI[sha256sum] = "81f5035a25c576af1a93f0061cf70bde6d00a0c7bd1274abf73f5b5389a6f82d"
> +SRC_URI[sha256sum] = "c43ce4548ebed788cd9df63658a7de105ceafba43fcd63fa352b1093e525cd24"
>
> UPSTREAM_CHECK_URI = "https://ftp.isc.org/isc/bind9/"
> # follow the ESV versions divisible by 2
--
Yoann Congal
Smile ECS
next prev parent reply other threads:[~2026-07-07 10:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 6:04 [OE-core][scarthgap][PATCH v2] bind: Upgrade 9.18.44 -> 9.18.49 Ashishkumar Parmar X (asparmar - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-07-07 10:19 ` Yoann Congal [this message]
2026-07-07 13:24 ` Ashishkumar Parmar -X (asparmar - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-07-07 14:24 ` Yoann Congal
2026-07-09 5:19 ` Ashishkumar Parmar -X (asparmar - E INFOCHIPS PRIVATE LIMITED at Cisco)
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=DJS9H2DLIVVC.2DDDZVKTEK2TS@smile.fr \
--to=yoann.congal@smile.fr \
--cc=asparmar@cisco.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=xe-linux-external@cisco.com \
/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