From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] openssl: upgrade to 1.0.0i
Date: Tue, 08 May 2012 07:38:22 -0700 [thread overview]
Message-ID: <4FA92FDE.1010102@intel.com> (raw)
In-Reply-To: <4FA8C5DE.5070404@opendreambox.org>
On 05/08/2012 12:06 AM, Andreas Oberritter wrote:
> Hello Scott,
>
> On 25.04.2012 07:13, Scott Garman wrote:
>> --- a/meta/recipes-connectivity/openssl/openssl.inc
>> +++ b/meta/recipes-connectivity/openssl/openssl.inc
>> @@ -4,8 +4,7 @@ HOMEPAGE = "http://www.openssl.org/"
>> BUGTRACKER = "http://www.openssl.org/news/vulnerabilities.html"
>> SECTION = "libs/network"
>>
>> -# Big Jump for OpenSSL 1.0 support with meta-oe
>> -INC_PR = "r15"
>> +INC_PR = "r0"
>>
>> # "openssl | SSLeay" dual license
>> LICENSE = "openssl"
>
> this hunk broke the upgrade path of out-of-tree users of openssl.inc,
> e.g. users of openssl 0.9.8 in their own layer.
>
> Please reset INC_PR to r15. You should have reset only PR (if it wasn't
> already "${INC_PR}.0"), not INC_PR.
Ouch. Sorry about that. I will submit a patch in the next few minutes to
correct this and will keep this in mind in the future.
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2012-05-08 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 5:13 [PATCH 0/2] Recipe security updates: libpng and openssl Scott Garman
2012-04-25 5:13 ` [PATCH 1/2] libpng: upgrade to 1.2.49 Scott Garman
2012-04-25 5:13 ` [PATCH 2/2] openssl: upgrade to 1.0.0i Scott Garman
2012-05-08 7:06 ` Andreas Oberritter
2012-05-08 14:38 ` Scott Garman [this message]
2012-04-27 20:54 ` [PATCH 0/2] Recipe security updates: libpng and openssl 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=4FA92FDE.1010102@intel.com \
--to=scott.a.garman@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox