From: Saul Wold <sgw@linux.intel.com>
To: "Iorga, Cristian" <cristian.iorga@intel.com>,
Lei Yang <yanglei.fage@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] net-tools: upgrade to v1.60-24.2
Date: Mon, 04 Feb 2013 13:52:30 -0800 [thread overview]
Message-ID: <51102D9E.1000305@linux.intel.com> (raw)
In-Reply-To: <969F26A8BAB325438E7EB80D3C3134FB161F3065@IRSMSX102.ger.corp.intel.com>
On 02/04/2013 01:10 AM, Iorga, Cristian wrote:
> See my answers below.
>
> -----Original Message-----
> From: Lei Yang [mailto:yanglei.fage@gmail.com]
> Sent: Sunday, February 03, 2013 4:15 AM
> To: Iorga, Cristian
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH] net-tools: upgrade to v1.60-24.2
>
>
>
> Sent from my iPhone
>
> On 2013-2-1, at 23:09, Cristian Iorga <cristian.iorga@intel.com> wrote:
>
>> Signed-off-by: Cristian Iorga <cristian.iorga@intel.com>
>> ---
>> .../net-tools-config.h | 0
>> .../net-tools-config.make | 0
>> .../net-tools/{net-tools_1.60-23.bb => net-tools_1.60-24.2.bb} | 6 +++---
>> 3 files changed, 3 insertions(+), 3 deletions(-) rename
>> meta/recipes-extended/net-tools/{net-tools-1.60-23 =>
>> net-tools-1.60-24.2}/net-tools-config.h (100%) rename
>> meta/recipes-extended/net-tools/{net-tools-1.60-23 =>
>> net-tools-1.60-24.2}/net-tools-config.make (100%) rename
>> meta/recipes-extended/net-tools/{net-tools_1.60-23.bb =>
>> net-tools_1.60-24.2.bb} (94%)
>>
>> diff --git
>> a/meta/recipes-extended/net-tools/net-tools-1.60-23/net-tools-config.h
>> b/meta/recipes-extended/net-tools/net-tools-1.60-24.2/net-tools-config
>> .h
>> similarity index 100%
>> rename from
>> meta/recipes-extended/net-tools/net-tools-1.60-23/net-tools-config.h
>> rename to
>> meta/recipes-extended/net-tools/net-tools-1.60-24.2/net-tools-config.h
>> diff --git
>> a/meta/recipes-extended/net-tools/net-tools-1.60-23/net-tools-config.m
>> ake
>> b/meta/recipes-extended/net-tools/net-tools-1.60-24.2/net-tools-config
>> .make
>> similarity index 100%
>> rename from
>> meta/recipes-extended/net-tools/net-tools-1.60-23/net-tools-config.mak
>> e rename to
>> meta/recipes-extended/net-tools/net-tools-1.60-24.2/net-tools-config.m
>> ake diff --git a/meta/recipes-extended/net-tools/net-tools_1.60-23.bb
>> b/meta/recipes-extended/net-tools/net-tools_1.60-24.2.bb
>> similarity index 94%
>> rename from meta/recipes-extended/net-tools/net-tools_1.60-23.bb
>> rename to meta/recipes-extended/net-tools/net-tools_1.60-24.2.bb
>> index bc61d21..4040e1a 100644
>> --- a/meta/recipes-extended/net-tools/net-tools_1.60-23.bb
>> +++ b/meta/recipes-extended/net-tools/net-tools_1.60-24.2.bb
>> @@ -5,7 +5,7 @@ BUGTRACKER = "http://bugs.debian.org/net-tools"
>> LICENSE = "GPLv2+"
>> LIC_FILES_CHKSUM = "file://COPYING;md5=8ca43cbc842c2336e835926c2166c28b \
>> file://ifconfig.c;beginline=11;endline=15;md5=d1ca372080ad5401e23ca0afc35cf9ba"
>> -PR = "r3"
>> +PR = "r0"
>>
>
> Is there a reason to change it back to r0
> Yes, because an upgrade has been done.
>
>
> Lei
>
>> SRC_URI = "${DEBIAN_MIRROR}/main/n/net-tools/net-tools_1.60.orig.tar.gz;name=tarball \
>>
>> ${DEBIAN_MIRROR}/main/n/net-tools/${BPN}_${PV}.diff.gz;apply=no;name=p
>> atch \
>
> Not sure why it not apply but not remove it.
> Sorry, I don't understand your comment.
> This package is distributed as a "base" tarball + patches to higher versions.
> Hence, I don't understand your comment.
>
Cristian:
A couple of questions that further need answering:
It seems that 1.60-24.2 is a testing/unstable version. Although it also
seems that whezzy and Sid are running with this version.
Lei:
If you look at the full recipe, you will see that net-tools has it's own
do_patch to deal with the downloaded version diff patch, therefore not
applying during normal patching is correct.
In this case as Cristian points out, the .diff.gz is the "update"
Sau!
>
> Lei
>
>> @@ -17,8 +17,8 @@ S = "${WORKDIR}/net-tools-1.60"
>> SRC_URI[tarball.md5sum] = "ecaf37acb5b5daff4bdda77785fd916d"
>> SRC_URI[tarball.sha256sum] = "ec67967cf7b1a3a3828a84762fbc013ac50ee5dc9aa3095d5c591f302c2de0f5"
>>
>> -SRC_URI[patch.md5sum] = "2412e55c20308d5fbd28bfadd18c075f"
>> -SRC_URI[patch.sha256sum] = "d678b3ea97d6c7ca548918994642bfc6b5511ab02f3a5881dfcca00c88bfd73b"
>> +SRC_URI[patch.md5sum] = "524658bb8df5ff92c4a991f5edcaf240"
>> +SRC_URI[patch.sha256sum] = "170cc024fcb34329f4c25fd88b5f160a06be5d6d3eaf0bc976650fd1b1a6235d"
>>
>> inherit gettext
>>
>> --
>> 1.7.10.4
>>
>>
>> _______________________________________________
>> 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:[~2013-02-04 22:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 15:09 [PATCH] net-tools: upgrade to v1.60-24.2 Cristian Iorga
2013-02-03 2:14 ` Lei Yang
2013-02-04 9:10 ` Iorga, Cristian
2013-02-04 21:52 ` Saul Wold [this message]
2013-02-05 7:23 ` Iorga, Cristian
2013-02-05 2:00 ` lei yang
2013-02-05 7:11 ` Iorga, Cristian
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=51102D9E.1000305@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=cristian.iorga@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=yanglei.fage@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.