From: Mark Hatle <mark.hatle@windriver.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/3 v2] rpm: Uprev to rpm-5.4.16 (pre) and rpm-5.4+cvs to current CVS head
Date: Mon, 29 Feb 2016 09:18:36 -0600 [thread overview]
Message-ID: <56D4614C.1050909@windriver.com> (raw)
In-Reply-To: <56D4449F.8010407@linux.intel.com>
On 2/29/16 7:16 AM, Alexander Kanavin wrote:
> On 02/26/2016 04:26 PM, Mark Hatle wrote:
>>> Why not update the oe-core recipe of db to 6.1 instead? Rpm is the only
>>> thing that is holding it back.
>>
>> Because today is feature freeze, and I'm not going to introduce a new BerkleyDB
>> version on the day of feature freeze. The only thing I can test on is RPM --
>> and there may be other users.
>>
>> The patch was done as a single unit specifically so when DB-6.1 is introduced,
>> it's VERY simple to remove.
>
> Can you then drop the NO_UPDATE_REASON from the db recipe as a part of
> this patchset?
I'll add a commit that does this.
> Alex
>
next prev parent reply other threads:[~2016-02-29 15:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 3:28 [PATCH 0/3 v2] Upgrade RPM 5 to 5.4.16 (CVS HEAD) Mark Hatle
2016-02-26 3:28 ` [PATCH 1/3 v2] rpm: Uprev to rpm-5.4.16 (pre) and rpm-5.4+cvs to current CVS head Mark Hatle
[not found] ` <39dcc8978920aeaf0eeb206b7292f32af4b775f7.1456456877.git.mark.hatle@wi ndriver.com>
2016-02-26 15:01 ` alexander.kanavin
2016-02-26 14:26 ` Mark Hatle
2016-02-29 13:16 ` Alexander Kanavin
2016-02-29 15:18 ` Mark Hatle [this message]
2016-02-26 3:28 ` [PATCH 2/3 v2] rpm: Enable specific crypto and digest settings via variables Mark Hatle
2016-02-26 3:28 ` [PATCH 3/3 v2] rpm: A number of the patches have been submitted upstream Mark Hatle
2016-02-26 23:11 ` [PATCH 0/3 v2] Upgrade RPM 5 to 5.4.16 (CVS HEAD) Burton, Ross
2016-02-27 4:26 ` Mark Hatle
2016-02-27 22:47 ` Burton, Ross
2016-02-27 23:26 ` Mark Hatle
2016-02-29 15:36 ` Mark Hatle
2016-03-01 1:33 ` Mark Hatle
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=56D4614C.1050909@windriver.com \
--to=mark.hatle@windriver.com \
--cc=alexander.kanavin@linux.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 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.