From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: yann.morin@orange.com
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 3/3] package/skopeo: security bump
Date: Mon, 21 Sep 2026 20:49:01 +0200 [thread overview]
Message-ID: <b766f279a156cf2bdb471435dbe621ed@free.fr> (raw)
In-Reply-To: <e08ef449d915444978f2bc784c9fdb7438d11c98.1789971481.git.yann.morin@orange.com>
Hi Yann,
On 21/09/2026 08:18, yann.morin@orange.com wrote:
> From: "Yann E. MORIN" <yann.morin@orange.com>
>
> This releases brings in a fix for:
> * CVE-2025-11395
>
> Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
> ---
> package/skopeo/skopeo.hash | 2 +-
> package/skopeo/skopeo.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/package/skopeo/skopeo.hash b/package/skopeo/skopeo.hash
> index 8a9fb22133..e496eb4410 100644
> --- a/package/skopeo/skopeo.hash
> +++ b/package/skopeo/skopeo.hash
> @@ -1,3 +1,3 @@
> # Locally calculated
> -sha256
> 1eea9364e344c4d6cb398fac53bc387663d19690552003b43c75819e8bb55527
> skopeo-1.24.0-go2.tar.gz
> +sha256
> 6a3f342a327ec7684198eb0e15114940b6101506db48d9a96590f5942cb3b335
> skopeo-1.24.1-go2.tar.gz
> sha256
> 716a8b80635c394681e652823e1e42e411ad2d254e1f202403422d74f4b0b106
> LICENSE
> diff --git a/package/skopeo/skopeo.mk b/package/skopeo/skopeo.mk
> index 354998b175..5a22658611 100644
> --- a/package/skopeo/skopeo.mk
> +++ b/package/skopeo/skopeo.mk
> @@ -4,7 +4,7 @@
> #
>
> ################################################################################
>
> -SKOPEO_VERSION = 1.24.0
> +SKOPEO_VERSION = 1.24.1
> SKOPEO_SITE = $(call github,containers,skopeo,v$(SKOPEO_VERSION))
While applying this patch, I noticed that:
https://github.com/containers/skopeo
was redirecting to:
https://github.com/podman-container-tools/skopeo
See also:
https://github.com/podman-container-tools/skopeo/commit/69ae01c7c6759d33fbe364ec7dff63e7c876e44c
Could you send a patch updating _SITE and the homepage
in Config.in please?
>
> SKOPEO_LICENSE = Apache-2.0
> --
> 2.43.0
Best regards,
Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-09-21 18:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 6:18 [Buildroot] [PATCH 0/3] Update a few packages, some for for security yann.morin
2026-09-21 6:18 ` [Buildroot] [PATCH 1/3] package/distribution-registry: security bump yann.morin
2026-09-21 18:45 ` Julien Olivain via buildroot
2026-10-02 10:33 ` Raphaël Mélotte via buildroot
2026-09-21 6:18 ` [Buildroot] [PATCH 2/3] package/docker-credential-gcr: bump version yann.morin
2026-09-21 6:18 ` [Buildroot] [PATCH 3/3] package/skopeo: security bump yann.morin
2026-09-21 18:49 ` Julien Olivain via buildroot [this message]
2026-10-02 10:34 ` Raphaël Mélotte 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=b766f279a156cf2bdb471435dbe621ed@free.fr \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=yann.morin@orange.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