From: Anuj Mittal <anuj.mittal@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [honister][PATCH 0/3] Pull request
Date: Tue, 22 Mar 2022 09:00:31 +0800 [thread overview]
Message-ID: <cover.1647910766.git.anuj.mittal@intel.com> (raw)
The following changes since commit 427f4ef11beb8ceee007b5c7e152f2383a114aca:
patch.py: Prevent git repo reinitialization (2022-03-11 10:55:24 +0800)
are available in the Git repository at:
git://push.openembedded.org/openembedded-core-contrib stable/honister-next
Chee Yang Lee (2):
ghostscript: fix CVE-2021-3781
go: update to 1.16.15
Sakib Sajal (1):
go: upgrade 1.16.13 -> 1.16.14
.../go/{go-1.16.13.inc => go-1.16.15.inc} | 4 +-
...1.16.13.bb => go-binary-native_1.16.15.bb} | 4 +-
....16.13.bb => go-cross-canadian_1.16.15.bb} | 0
...o-cross_1.16.13.bb => go-cross_1.16.15.bb} | 0
...ssdk_1.16.13.bb => go-crosssdk_1.16.15.bb} | 0
...native_1.16.13.bb => go-native_1.16.15.bb} | 0
...ntime_1.16.13.bb => go-runtime_1.16.15.bb} | 0
.../go/{go_1.16.13.bb => go_1.16.15.bb} | 0
.../ghostscript/CVE-2021-3781.patch | 236 ++++++++++++++++++
.../ghostscript/ghostscript_9.54.0.bb | 1 +
10 files changed, 241 insertions(+), 4 deletions(-)
rename meta/recipes-devtools/go/{go-1.16.13.inc => go-1.16.15.inc} (90%)
rename meta/recipes-devtools/go/{go-binary-native_1.16.13.bb => go-binary-native_1.16.15.bb} (83%)
rename meta/recipes-devtools/go/{go-cross-canadian_1.16.13.bb => go-cross-canadian_1.16.15.bb} (100%)
rename meta/recipes-devtools/go/{go-cross_1.16.13.bb => go-cross_1.16.15.bb} (100%)
rename meta/recipes-devtools/go/{go-crosssdk_1.16.13.bb => go-crosssdk_1.16.15.bb} (100%)
rename meta/recipes-devtools/go/{go-native_1.16.13.bb => go-native_1.16.15.bb} (100%)
rename meta/recipes-devtools/go/{go-runtime_1.16.13.bb => go-runtime_1.16.15.bb} (100%)
rename meta/recipes-devtools/go/{go_1.16.13.bb => go_1.16.15.bb} (100%)
create mode 100644 meta/recipes-extended/ghostscript/ghostscript/CVE-2021-3781.patch
--
2.35.1
reply other threads:[~2022-03-22 1:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=cover.1647910766.git.anuj.mittal@intel.com \
--to=anuj.mittal@intel.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox