From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/7] Package Updates
Date: Tue, 21 May 2013 17:40:18 -0700 [thread overview]
Message-ID: <cover.1369183108.git.sgw@linux.intel.com> (raw)
Updates for Milestone 1
Sau!
The following changes since commit f45aa6e07318f22ede4614b28ea15cd48f5e4095:
packagegroup-core-clutter: use clutter-1.0 packages (2013-05-21 09:14:38 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib sgw/updates
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=sgw/updates
Saul Wold (7):
gnupg: Update to 2.0.20
desktop-file-utils: Update to 0.21
mklibs: Update to 0.1.37
libnl: Update to 3.2.22
mc: Update to 4.8.8
resolvconf: Update to 1.72
cmake: Update to 2.8.11
.../{resolvconf_1.71.bb => resolvconf_1.72.bb} | 4 +-
.../cmake/cmake-native_2.8.10.2.bb | 7 ---
meta/recipes-devtools/cmake/cmake-native_2.8.11.bb | 5 ++
meta/recipes-devtools/cmake/cmake.inc | 2 -
.../cmake/cmake/support-oe-qt4-tools-names.patch | 70 +++++-----------------
.../cmake/{cmake_2.8.10.2.bb => cmake_2.8.11.bb} | 6 +-
...e_0.15.bb => desktop-file-utils-native_0.21.bb} | 10 ++--
...bs-native_0.1.35.bb => mklibs-native_0.1.37.bb} | 4 +-
.../mc/{mc_4.8.7.bb => mc_4.8.8.bb} | 6 +-
.../gnupg/gnupg-2.0.19/GnuPG2-CVE-2012-6085.patch | 63 -------------------
.../gnupg/{gnupg_2.0.19.bb => gnupg_2.0.20.bb} | 8 +--
.../libnl/{libnl_3.2.21.bb => libnl_3.2.22.bb} | 5 +-
12 files changed, 37 insertions(+), 153 deletions(-)
rename meta/recipes-connectivity/resolvconf/{resolvconf_1.71.bb => resolvconf_1.72.bb} (88%)
delete mode 100644 meta/recipes-devtools/cmake/cmake-native_2.8.10.2.bb
create mode 100644 meta/recipes-devtools/cmake/cmake-native_2.8.11.bb
rename meta/recipes-devtools/cmake/{cmake_2.8.10.2.bb => cmake_2.8.11.bb} (86%)
rename meta/recipes-devtools/desktop-file-utils/{desktop-file-utils-native_0.15.bb => desktop-file-utils-native_0.21.bb} (57%)
rename meta/recipes-devtools/mklibs/{mklibs-native_0.1.35.bb => mklibs-native_0.1.37.bb} (80%)
rename meta/recipes-extended/mc/{mc_4.8.7.bb => mc_4.8.8.bb} (81%)
delete mode 100644 meta/recipes-support/gnupg/gnupg-2.0.19/GnuPG2-CVE-2012-6085.patch
rename meta/recipes-support/gnupg/{gnupg_2.0.19.bb => gnupg_2.0.20.bb} (80%)
rename meta/recipes-support/libnl/{libnl_3.2.21.bb => libnl_3.2.22.bb} (90%)
--
1.8.1.4
next reply other threads:[~2013-05-22 0:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 0:40 Saul Wold [this message]
2013-05-22 0:40 ` [PATCH 1/7] gnupg: Update to 2.0.20 Saul Wold
2013-05-22 0:40 ` [PATCH 2/7] desktop-file-utils: Update to 0.21 Saul Wold
2013-05-22 0:40 ` [PATCH 3/7] mklibs: Update to 0.1.37 Saul Wold
2013-05-22 0:40 ` [PATCH 4/7] libnl: Update to 3.2.22 Saul Wold
2013-05-22 0:40 ` [PATCH 5/7] mc: Update to 4.8.8 Saul Wold
2013-05-22 0:40 ` [PATCH 6/7] resolvconf: Update to 1.72 Saul Wold
2013-05-22 0:40 ` [PATCH 7/7] cmake: Update to 2.8.11 Saul Wold
2013-05-22 13:13 ` Otavio Salvador
2013-05-22 15:12 ` Saul Wold
-- strict thread matches above, loose matches on Subject: below --
2014-02-17 8:22 [PATCH 0/7] Package Updates Saul Wold
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.1369183108.git.sgw@linux.intel.com \
--to=sgw@linux.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