From: Constantin Musca <constantinx.musca@intel.com>
To: openembedded-core@lists.openembedded.org
Cc: Constantin Musca <constantinx.musca@intel.com>
Subject: [PATCH 0/6] Package upgrades
Date: Thu, 16 Aug 2012 15:55:14 +0300 [thread overview]
Message-ID: <1345121720-25925-1-git-send-email-constantinx.musca@intel.com> (raw)
This is another set of package upgrades compiled on all architectures
and tested using core-image-sato-sdk. The connman 1.4 recipe doesn't
need the 0001-storage-check-that-the-string-isn-t-empty-before-spl.patch
anymore.
Constantin Musca (6):
dbus: upgrade to 1.6.4
ofono: upgrade to 1.10
iproute2: upgrade to 3.5.0
iptables: upgrade to 1.4.15
pulseaudio: upgrade to 2.1
connman: upgrade to 1.4
...ck-that-the-string-isn-t-empty-before-spl.patch | 37 --------------------
.../connman/{connman_1.3.bb => connman_1.4.bb} | 9 +++--
.../configure-cross.patch | 0
.../{iproute2_3.4.0.bb => iproute2_3.5.0.bb} | 4 +--
.../ofono/{ofono_1.8.bb => ofono_1.10.bb} | 6 ++--
.../dbus/{dbus-1.4.20 => dbus-1.6.4}/dbus-1.init | 0
.../dbus/{dbus-1.4.20 => dbus-1.6.4}/tmpdir.patch | 0
.../dbus/{dbus_1.4.20.bb => dbus_1.6.4.bb} | 4 +--
.../{iptables_1.4.14.bb => iptables_1.4.15.bb} | 4 +--
.../{pulseaudio_2.0.bb => pulseaudio_2.1.bb} | 4 +--
10 files changed, 15 insertions(+), 53 deletions(-)
delete mode 100644 meta/recipes-connectivity/connman/connman/0001-storage-check-that-the-string-isn-t-empty-before-spl.patch
rename meta/recipes-connectivity/connman/{connman_1.3.bb => connman_1.4.bb} (69%)
rename meta/recipes-connectivity/iproute2/{iproute2-3.4.0 => iproute2-3.5.0}/configure-cross.patch (100%)
rename meta/recipes-connectivity/iproute2/{iproute2_3.4.0.bb => iproute2_3.5.0.bb} (51%)
rename meta/recipes-connectivity/ofono/{ofono_1.8.bb => ofono_1.10.bb} (63%)
rename meta/recipes-core/dbus/{dbus-1.4.20 => dbus-1.6.4}/dbus-1.init (100%)
rename meta/recipes-core/dbus/{dbus-1.4.20 => dbus-1.6.4}/tmpdir.patch (100%)
rename meta/recipes-core/dbus/{dbus_1.4.20.bb => dbus_1.6.4.bb} (21%)
rename meta/recipes-extended/iptables/{iptables_1.4.14.bb => iptables_1.4.15.bb} (91%)
rename meta/recipes-multimedia/pulseaudio/{pulseaudio_2.0.bb => pulseaudio_2.1.bb} (71%)
--
1.7.9.5
next reply other threads:[~2012-08-16 14:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 12:55 Constantin Musca [this message]
2012-08-16 12:55 ` [PATCH 1/6] dbus: upgrade to 1.6.4 Constantin Musca
2012-08-16 12:55 ` [PATCH 2/6] ofono: upgrade to 1.10 Constantin Musca
2012-08-16 12:55 ` [PATCH 3/6] iproute2: upgrade to 3.5.0 Constantin Musca
2012-08-16 12:55 ` [PATCH 4/6] iptables: upgrade to 1.4.15 Constantin Musca
2012-08-16 12:55 ` [PATCH 5/6] pulseaudio: upgrade to 2.1 Constantin Musca
2012-08-16 12:55 ` [PATCH 6/6] connman: upgrade to 1.4 Constantin Musca
2012-08-17 16:19 ` Saul Wold
2012-08-17 15:51 ` Constantin Musca
2012-08-17 16:50 ` Saul Wold
2012-08-17 16:26 ` Andrei Gherzan
2012-08-17 21:22 ` [PATCH 0/6] Package upgrades Saul Wold
-- strict thread matches above, loose matches on Subject: below --
2015-04-08 10:24 [PATCH 0/6] Package Upgrades Chen Qi
2015-04-14 9:07 Robert Yang
2018-08-22 10:27 [PATCH 0/6] package upgrades Maxin B. John
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=1345121720-25925-1-git-send-email-constantinx.musca@intel.com \
--to=constantinx.musca@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