From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Martin Jansa <martin.jansa@gmail.com>
Subject: Re: [PATCH 6/8] ofono: upgrade to version 1.6
Date: Mon, 30 Apr 2012 08:21:52 -0700 [thread overview]
Message-ID: <4F9EAE10.6090901@linux.intel.com> (raw)
In-Reply-To: <20120429084538.GA350@jama.jama.net>
On 04/29/2012 01:45 AM, Martin Jansa wrote:
> On Sat, Apr 28, 2012 at 04:12:30PM +0800, Dongxiao Xu wrote:
>> Signed-off-by: Dongxiao Xu<dongxiao.xu@intel.com>
>> ---
>> .../ofono/{ofono_1.5.bb => ofono_1.6.bb} | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>> rename meta/recipes-connectivity/ofono/{ofono_1.5.bb => ofono_1.6.bb} (97%)
>>
>> diff --git a/meta/recipes-connectivity/ofono/ofono_1.5.bb b/meta/recipes-connectivity/ofono/ofono_1.6.bb
>> similarity index 97%
>> rename from meta/recipes-connectivity/ofono/ofono_1.5.bb
>> rename to meta/recipes-connectivity/ofono/ofono_1.6.bb
>> index dad813f..d0f273b 100644
>> --- a/meta/recipes-connectivity/ofono/ofono_1.5.bb
>> +++ b/meta/recipes-connectivity/ofono/ofono_1.6.bb
>> @@ -1,6 +1,6 @@
>> require ofono.inc
>>
>> -PR = "r1"
>> +PR = "r0"
>
> without checksum change it will fail, right?
>
> I'll send patch I have for ofono upgrade in my branch.
>
This seems to have uncovered a problem with the Fetcher, it happily
pulls the upstream tarball, raises a BBFetchException, and writes the
checksum failure to the log file, but it seems to still mark the fetch
complete with a .done file and continues to build.
I will file a bug.
Sau!
>>
>> SRC_URI = "${KERNELORG_MIRROR}/linux/network/ofono/${BPN}-${PV}.tar.bz2 \
>> file://ofono"
>> --
>> 1.7.4.1
>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2012-04-30 15:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-28 8:12 [PATCH 0/8][PULL] Recipe upgrades for ofono, iptables, etc Dongxiao Xu
2012-04-28 8:12 ` [PATCH 1/8] gst-fluendo-mpegdemux: upgrade to version 0.10.70 Dongxiao Xu
2012-04-28 8:12 ` [PATCH 2/8] telepathy-mission-control: upgrade to version 5.12.0 Dongxiao Xu
2012-04-28 8:12 ` [PATCH 3/8] telepathy-glib: upgrade to version 0.18.1 Dongxiao Xu
2012-04-28 8:12 ` [PATCH 4/8] bluez-hcidump: upgrade to version 2.4 Dongxiao Xu
2012-04-28 8:12 ` [PATCH 5/8] iproute2: upgrade to version 3.3.0 Dongxiao Xu
2012-04-28 23:29 ` Saul Wold
2012-04-28 8:12 ` [PATCH 6/8] ofono: upgrade to version 1.6 Dongxiao Xu
2012-04-29 8:45 ` Martin Jansa
2012-04-29 8:46 ` [PATCH] ofono: upgrade to 1.6 Martin Jansa
2012-05-01 18:29 ` Saul Wold
2012-04-30 15:21 ` Saul Wold [this message]
2012-04-30 15:31 ` [PATCH 6/8] ofono: upgrade to version 1.6 Khem Raj
2012-04-30 15:46 ` Koen Kooi
2012-04-28 8:12 ` [PATCH 7/8] iptables: upgrade to version 1.4.13 Dongxiao Xu
2012-04-28 8:12 ` [PATCH 8/8] distro_tracking_fields: Change for ofono, iptables, etc Dongxiao Xu
2012-05-01 18:30 ` [PATCH 0/8][PULL] Recipe 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=4F9EAE10.6090901@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=martin.jansa@gmail.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