From: Chen Qi <Qi.Chen@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/4] Upgrade sudo, cups, sysstat, at
Date: Wed, 5 Dec 2018 16:40:42 +0800 [thread overview]
Message-ID: <cover.1543996242.git.Qi.Chen@windriver.com> (raw)
The following changes since commit 016e3dda2d6acc9b457079d11b5346a5352a431d:
btrfs-tools: update to 4.19 (2018-12-03 12:20:01 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib ChenQi/PU
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=ChenQi/PU
Chen Qi (4):
sudo: upgrade to 1.8.26
cups: upgrade to 2.2.9
sysstat: upgrade to 12.1.1
at: upgrade to 3.1.23
.../at/at/fix_parallel_build_error.patch | 15 +++++---
meta/recipes-extended/at/at/pam.conf.patch | 40 +++++++++++++---------
.../at/{at_3.1.20.bb => at_3.1.23.bb} | 6 ++--
.../0001-don-t-try-to-run-generated-binaries.patch | 29 ++++++++--------
.../cups/{cups_2.2.8.bb => cups_2.2.9.bb} | 4 +--
meta/recipes-extended/sudo/sudo.inc | 7 ++--
.../sudo/{sudo_1.8.23.bb => sudo_1.8.26.bb} | 4 +--
.../{sysstat_11.7.4.bb => sysstat_12.1.1.bb} | 4 +--
8 files changed, 63 insertions(+), 46 deletions(-)
rename meta/recipes-extended/at/{at_3.1.20.bb => at_3.1.23.bb} (90%)
rename meta/recipes-extended/cups/{cups_2.2.8.bb => cups_2.2.9.bb} (40%)
rename meta/recipes-extended/sudo/{sudo_1.8.23.bb => sudo_1.8.26.bb} (91%)
rename meta/recipes-extended/sysstat/{sysstat_11.7.4.bb => sysstat_12.1.1.bb} (53%)
--
1.9.1
next reply other threads:[~2018-12-05 8:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 8:40 Chen Qi [this message]
2018-12-05 8:40 ` [PATCH 1/4] sudo: upgrade to 1.8.26 Chen Qi
2018-12-05 8:40 ` [PATCH 2/4] cups: upgrade to 2.2.9 Chen Qi
2018-12-05 8:40 ` [PATCH 3/4] sysstat: upgrade to 12.1.1 Chen Qi
2018-12-05 8:40 ` [PATCH 4/4] at: upgrade to 3.1.23 Chen Qi
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.1543996242.git.Qi.Chen@windriver.com \
--to=qi.chen@windriver.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