From: Randy MacLeod <randy.macleod@windriver.com>
To: <rongqing.li@windriver.com>,
<openembedded-core@lists.openembedded.org>,
"openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>,
<Mark.Hatle@windriver.com>
Subject: Re: [PATCH 1/1] apt: upgrade to 1.0.9.9
Date: Wed, 6 May 2015 11:43:19 -0400 [thread overview]
Message-ID: <554A3697.5050208@windriver.com> (raw)
In-Reply-To: <1430810046-27021-1-git-send-email-rongqing.li@windriver.com>
On 2015-05-05 03:14 AM, rongqing.li@windriver.com wrote:
> From: Roy Li <rongqing.li@windriver.com>
>
> Upgrade to fix the several CVEs: CVE-2014-0488, CVE-2014-0490
> Remove apt-0.9.9.4-CVE-2014-0478.patch, which was backport.
> Romve no-ko-translation.patch, apt-1.0.9.9 has ko translation
s/Romve/Remove/
> Update use-host.patch no-curl.patch db_linking_hack.patch and
> noconfigure.patch
> Not build the test cases since it requires gtest
meta-oe has gtest:
http://layers.openembedded.org/layerindex/recipe/31721/
Is there any reason not to move it and gmock to oe-core?
It has no dependencies and it's used by:
llvm, google-protocol buffers, opencv, google-chrome
and probably other packages.
I think Mark mentioned that llvm might move to oe-core as
well so that would be two recipes that benefit from moving gtest.
--
# Randy MacLeod. SMTS, Linux, Wind River
Direct: 613.963.1350 | 350 Terry Fox Drive, Suite 200, Ottawa, ON,
Canada, K2K 2W5
prev parent reply other threads:[~2015-05-06 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 7:14 [PATCH 1/1] apt: upgrade to 1.0.9.9 rongqing.li
2015-05-05 15:34 ` Burton, Ross
2015-05-06 6:33 ` Rongqing Li
2015-05-06 15:54 ` Aníbal Limón
2015-05-06 15:43 ` Randy MacLeod [this message]
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=554A3697.5050208@windriver.com \
--to=randy.macleod@windriver.com \
--cc=Mark.Hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=rongqing.li@windriver.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