From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] db: Remove unneeded PR
Date: Mon, 3 Oct 2016 14:30:15 -0500 [thread overview]
Message-ID: <57F2B1C7.4070305@linux.intel.com> (raw)
In-Reply-To: <10109248.sKfs07qT7T@peggleto-mobl.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]
On 10/03/2016 02:25 PM, Paul Eggleton wrote:
> On Mon, 03 Oct 2016 14:17:27 Aníbal Limón wrote:
>> The PR is not need so remove it after upgrade to 6.0.35.
>>
>> Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
>> ---
>> meta/recipes-support/db/db_6.0.35.bb | 2 --
>> 1 file changed, 2 deletions(-)
>>
>> diff --git a/meta/recipes-support/db/db_6.0.35.bb
>> b/meta/recipes-support/db/db_6.0.35.bb index 32afbe8..ecb1bee 100644
>> --- a/meta/recipes-support/db/db_6.0.35.bb
>> +++ b/meta/recipes-support/db/db_6.0.35.bb
>> @@ -15,8 +15,6 @@ LICENSE = "AGPL-3.0"
>> VIRTUAL_NAME ?= "virtual/db"
>> RCONFLICTS_${PN} = "db3"
>>
>> -PR = "r1"
>> -
>> # Note, when upgraded to 6.1.x, a patch in RPM will need to be removed to
>> activate db 6.1 support. SRC_URI =
>> "http://distfiles.gentoo.org/distfiles/db-${PV}.tar.gz \
>> file://arm-thumb-mutex_db5.patch \
>
> I think it's too late to do this unfortunately - it needs to be done at the
> same time as the upgrade.
I sent a PATCHv3 [1] removing the PR but unfortunately was not integrated.
[1]
http://lists.openembedded.org/pipermail/openembedded-core/2016-September/127027.html
Cheers,
alimon
>
> Cheers,
> Paul
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2016-10-03 19:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 19:17 [PATCH] db: Remove unneeded PR Aníbal Limón
2016-10-03 19:25 ` Paul Eggleton
2016-10-03 19:30 ` Aníbal Limón [this message]
2016-10-03 19:51 ` Paul Eggleton
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=57F2B1C7.4070305@linux.intel.com \
--to=anibal.limon@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox