From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 1/3] package/runc: bump to version 1.0.0-rc93
Date: Thu, 11 Feb 2021 16:49:34 +0100 [thread overview]
Message-ID: <87y2fuioz5.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20210210235203.2819535-1-christian@paral.in> (Christian Stewart's message of "Wed, 10 Feb 2021 15:52:01 -0800")
>>>>> "Christian" == Christian Stewart <christian@paral.in> writes:
> https://github.com/opencontainers/runc/releases/tag/v1.0.0-rc93
Is this meant for master or next?
It is in the same series as security bumps, but I see the release notes
talks about a feature-rich release?
It also mentions the following:
For packagers the following changes have been made which will have impact on
your packaging of runc:
The "selinux" and "apparmor" buildtags have been removed, and now all runc
builds will have SELinux and AppArmor support enabled. Note that "seccomp"
is still optional (though we very highly recommend you enable it).
But I see no changes related to this?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2021-02-11 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 23:52 [Buildroot] [PATCH v1 1/3] package/runc: bump to version 1.0.0-rc93 Christian Stewart
2021-02-10 23:52 ` [Buildroot] [PATCH v1 2/3] package/docker-engine: security bump to version 20.10.3 Christian Stewart
2021-02-11 15:52 ` Peter Korsgaard
2021-02-10 23:52 ` [Buildroot] [PATCH v1 3/3] package/docker-cli: " Christian Stewart
2021-02-11 15:52 ` Peter Korsgaard
2021-02-11 15:49 ` Peter Korsgaard [this message]
2021-02-11 21:11 ` [Buildroot] [PATCH v1 1/3] package/runc: bump to version 1.0.0-rc93 Christian Stewart
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=87y2fuioz5.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--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 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.