From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] openssl: update 1.0.0 to 1.0.0a
Date: Tue, 17 Aug 2010 13:58:09 +0200 [thread overview]
Message-ID: <20100817115809.GF11569@jama> (raw)
In-Reply-To: <1281983778-21054-1-git-send-email-khimov@altell.ru>
On Mon, Aug 16, 2010 at 10:36:18PM +0400, Roman I Khimov wrote:
> * exactly one fix, considered as safe upgrade
>
> Signed-off-by: Roman I Khimov <khimov@altell.ru>
Acked-by: Martin Jansa <Martin.Jansa@gmail.com>
> ---
> .../include/angstrom-2008-preferred-versions.inc | 4 +-
> conf/distro/include/preferred-shr-versions.inc | 4 +-
> .../openssl/openssl-1.0.0/configure-targets.patch | 25 -
> recipes/openssl/openssl-1.0.0/debian.patch | 515 --------------------
> .../engines-install-in-libdir-ssl.patch | 53 --
> recipes/openssl/openssl-1.0.0/libdeps-first.patch | 27 -
> recipes/openssl/openssl-1.0.0/oe-ldflags.patch | 22 -
> recipes/openssl/openssl-1.0.0/shared-libs.patch | 48 --
> .../openssl/openssl-1.0.0a/configure-targets.patch | 25 +
> recipes/openssl/openssl-1.0.0a/debian.patch | 515 ++++++++++++++++++++
> .../engines-install-in-libdir-ssl.patch | 53 ++
> recipes/openssl/openssl-1.0.0a/libdeps-first.patch | 27 +
> recipes/openssl/openssl-1.0.0a/oe-ldflags.patch | 22 +
> recipes/openssl/openssl-1.0.0a/shared-libs.patch | 48 ++
> recipes/openssl/openssl-native_1.0.0.bb | 27 -
> recipes/openssl/openssl-native_1.0.0a.bb | 27 +
> recipes/openssl/openssl_1.0.0.bb | 30 --
> recipes/openssl/openssl_1.0.0a.bb | 30 ++
> 18 files changed, 751 insertions(+), 751 deletions(-)
> delete mode 100644 recipes/openssl/openssl-1.0.0/configure-targets.patch
> delete mode 100644 recipes/openssl/openssl-1.0.0/debian.patch
> delete mode 100644 recipes/openssl/openssl-1.0.0/engines-install-in-libdir-ssl.patch
> delete mode 100644 recipes/openssl/openssl-1.0.0/libdeps-first.patch
> delete mode 100644 recipes/openssl/openssl-1.0.0/oe-ldflags.patch
> delete mode 100644 recipes/openssl/openssl-1.0.0/shared-libs.patch
> create mode 100644 recipes/openssl/openssl-1.0.0a/configure-targets.patch
> create mode 100644 recipes/openssl/openssl-1.0.0a/debian.patch
> create mode 100644 recipes/openssl/openssl-1.0.0a/engines-install-in-libdir-ssl.patch
> create mode 100644 recipes/openssl/openssl-1.0.0a/libdeps-first.patch
> create mode 100644 recipes/openssl/openssl-1.0.0a/oe-ldflags.patch
> create mode 100644 recipes/openssl/openssl-1.0.0a/shared-libs.patch
> delete mode 100644 recipes/openssl/openssl-native_1.0.0.bb
> create mode 100644 recipes/openssl/openssl-native_1.0.0a.bb
> delete mode 100644 recipes/openssl/openssl_1.0.0.bb
> create mode 100644 recipes/openssl/openssl_1.0.0a.bb
prev parent reply other threads:[~2010-08-17 11:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 18:36 [PATCH] openssl: update 1.0.0 to 1.0.0a Roman I Khimov
2010-08-16 18:59 ` Frans Meulenbroeks
2010-08-16 19:25 ` Roman I Khimov
2010-08-16 19:32 ` Frans Meulenbroeks
2010-08-16 19:35 ` Khem Raj
2010-08-16 20:10 ` Frans Meulenbroeks
2010-08-17 6:50 ` Roman I Khimov
2010-08-17 7:05 ` Martin Jansa
2010-08-17 7:06 ` Frans Meulenbroeks
2010-08-17 7:26 ` `DEFAULT_PREFERENCE = "-1"` of current (upstream) releases (was: [PATCH] openssl: update 1.0.0 to 1.0.0a) Paul Menzel
2010-08-17 8:42 ` Dr. Michael Lauer
2010-08-17 11:58 ` Martin Jansa [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=20100817115809.GF11569@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@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