All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: jonas.gorski@bisdn.de
Cc: meta-virtualization@lists.yoctoproject.org
Subject: Re: [meta-virtualization][kirkstone][PATCH 0/4] runc: update to 1.1.15
Date: Mon, 30 Mar 2026 15:48:36 -0400	[thread overview]
Message-ID: <acrTlFWe3YF8dX4l@gmail.com> (raw)
In-Reply-To: <20260327140640.126833-1-jonas.gorski@bisdn.de>



In message: [meta-virtualization][kirkstone][PATCH 0/4] runc: update to 1.1.15
on 27/03/2026 Jonas Gorski via lists.yoctoproject.org wrote:

> runc has been stuck at 1.1.4 for long while in kirkstone, and the last
> attempt at updating it had to be reverted.
> 
> In order to reduce the amount of open vulnerabilities, update it to the
> latest 1.1 release, 1.1.15, by first updating it to 1.1.12, which was
> the last 1.1 release in master, then updating it to 1.1.15.
> 
> To keep the amount of patches short, I squashed the cherry-picked
> updates from master to a single patch each.
> 
> In case anyone wonders, runc-opencontainers and runc-docker were at
> different commits before they were both bumped to 1.2.0-rc2, which is
> why their diffs looks different.
> 
> I runtested runc-opencontainers, and compile-tested runc-docker.

Thanks for the extra details, it made this much easier to
merge.

I confirmed bug/cve only in the 3rd digit bumps, so this is
now merged and pushed to the server.

Bruce

> 
> Jonas Gorski (4):
>   runc-opencontainers: update to 1.1.12
>   runc-docker: update to 1.1.12
>   runc-opencontainers: update to 1.1.15
>   runc-docker: update to 1.1.15
> 
>  ...spect-GOBUILDFLAGS-for-runc-and-remove-re.patch | 14 +++++++-------
>  recipes-containers/runc/runc-docker_git.bb         |  4 ++--
>  recipes-containers/runc/runc-opencontainers_git.bb |  4 ++--
>  3 files changed, 11 insertions(+), 11 deletions(-)
> 
> -- 
> 2.53.0
> 
> 
> -- 
> BISDN GmbH
> K�rnerstra�e 7-10
> 10785 Berlin
> Germany
> Phone: +49 30 610 816 100
> Managing Directors:�Dr.-Ing. Hagen Woesner, Andreas K�psel
> 
> 
> Commercial 
> register:�
> Amtsgericht Berlin-Charlottenburg HRB 141569 B
> VAT ID No:�
> DE283257294
> 
> 
> 

> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#9677): https://lists.yoctoproject.org/g/meta-virtualization/message/9677
> Mute This Topic: https://lists.yoctoproject.org/mt/118535116/1050810
> Group Owner: meta-virtualization+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub [bruce.ashfield@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 



  parent reply	other threads:[~2026-03-30 19:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-27 14:06 [meta-virtualization][kirkstone][PATCH 0/4] runc: update to 1.1.15 Jonas Gorski
2026-03-27 14:06 ` [meta-virtualization][kirkstone][PATCH 1/4] runc-opencontainers: update to 1.1.12 Jonas Gorski
2026-03-27 14:06 ` [meta-virtualization][kirkstone][PATCH 2/4] runc-docker: " Jonas Gorski
2026-03-27 14:06 ` [meta-virtualization][kirkstone][PATCH 3/4] runc-opencontainers: update to 1.1.15 Jonas Gorski
2026-03-27 14:06 ` [meta-virtualization][kirkstone][PATCH 4/4] runc-docker: " Jonas Gorski
2026-03-30 19:48 ` Bruce Ashfield [this message]
2026-03-31  8:13   ` [meta-virtualization][kirkstone][PATCH 0/4] runc: " Jonas Gorski

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=acrTlFWe3YF8dX4l@gmail.com \
    --to=bruce.ashfield@gmail.com \
    --cc=jonas.gorski@bisdn.de \
    --cc=meta-virtualization@lists.yoctoproject.org \
    /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.