From: Constantin Musca <constantinx.musca@intel.com>
To: openembedded-core@lists.openembedded.org
Cc: Constantin Musca <constantinx.musca@intel.com>
Subject: [PATCH 1/6] dbus: upgrade to 1.6.4
Date: Thu, 16 Aug 2012 15:55:15 +0300 [thread overview]
Message-ID: <1345121720-25925-2-git-send-email-constantinx.musca@intel.com> (raw)
In-Reply-To: <1345121720-25925-1-git-send-email-constantinx.musca@intel.com>
Signed-off-by: Constantin Musca <constantinx.musca@intel.com>
---
.../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 ++--
3 files changed, 2 insertions(+), 2 deletions(-)
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%)
diff --git a/meta/recipes-core/dbus/dbus-1.4.20/dbus-1.init b/meta/recipes-core/dbus/dbus-1.6.4/dbus-1.init
similarity index 100%
rename from meta/recipes-core/dbus/dbus-1.4.20/dbus-1.init
rename to meta/recipes-core/dbus/dbus-1.6.4/dbus-1.init
diff --git a/meta/recipes-core/dbus/dbus-1.4.20/tmpdir.patch b/meta/recipes-core/dbus/dbus-1.6.4/tmpdir.patch
similarity index 100%
rename from meta/recipes-core/dbus/dbus-1.4.20/tmpdir.patch
rename to meta/recipes-core/dbus/dbus-1.6.4/tmpdir.patch
diff --git a/meta/recipes-core/dbus/dbus_1.4.20.bb b/meta/recipes-core/dbus/dbus_1.6.4.bb
similarity index 21%
rename from meta/recipes-core/dbus/dbus_1.4.20.bb
rename to meta/recipes-core/dbus/dbus_1.6.4.bb
index c0da998..179097d 100644
--- a/meta/recipes-core/dbus/dbus_1.4.20.bb
+++ b/meta/recipes-core/dbus/dbus_1.6.4.bb
@@ -2,5 +2,5 @@ include dbus.inc
PR = "${INC_PR}.0"
-SRC_URI[md5sum] = "79eca2f2c1894ac347acce128314428b"
-SRC_URI[sha256sum] = "103bdcd261a13140730b5fa69f56a98ab5c89ba3f0116ea62fcfd639520d5aaf"
+SRC_URI[md5sum] = "5ec43dc4554cba638917317b2b4f7640"
+SRC_URI[sha256sum] = "5fba6b7a415d761a843fb8e0aee72db61cf13057a9ef8cdc795e5d369dc74cf1"
--
1.7.9.5
next prev parent reply other threads:[~2012-08-16 14:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 12:55 [PATCH 0/6] Package upgrades Constantin Musca
2012-08-16 12:55 ` Constantin Musca [this message]
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
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-2-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