From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] lzo: security bump to version 2.07
Date: Fri, 27 Jun 2014 14:26:52 +0300 [thread overview]
Message-ID: <20140627112652.GC4155@tarshish> (raw)
In-Reply-To: <87wqc2lif0.fsf@dell.be.48ers.dk>
Hi Peter,
On Fri, Jun 27, 2014 at 01:07:47PM +0200, Peter Korsgaard wrote:
> >>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
>
> > Fixes CVE-2014-4607.
> > Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> > ---
> > package/lzo/lzo.mk | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
>
> > diff --git a/package/lzo/lzo.mk b/package/lzo/lzo.mk
> > index 10107fea3be3..bf85e84e9a71 100644
> > --- a/package/lzo/lzo.mk
> > +++ b/package/lzo/lzo.mk
> > @@ -4,11 +4,13 @@
> > #
> > ################################################################################
>
> > -LZO_VERSION = 2.06
> > +LZO_VERSION = 2.07
> > LZO_SITE = http://www.oberhumer.com/opensource/lzo/download
> > LZO_LICENSE = GPLv2+
> > LZO_LICENSE_FILES = COPYING
> > LZO_INSTALL_STAGING = YES
> > +# Make libtool patch apply
> > +LZO_AUTORECONF = YES
>
> Why? Please explain.
Otherwise libtool patching fails:
>>> lzo 2.07 Patching libtool
Applying buildroot-libtool-v2.4.patch using patch: patching file ltmain.sh
Hunk #1 FAILED at 1416.
Hunk #2 FAILED at 2962.
Hunk #3 succeeded at 7964 with fuzz 2 (offset 1281 lines).
Hunk #4 succeeded at 10554 (offset 1297 lines).
2 out of 4 hunks FAILED -- saving rejects to file ltmain.sh.rej
Patch failed! Please fix buildroot-libtool-v2.4.patch!
Should I rephrase the comment?
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2014-06-27 11:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 4:32 [Buildroot] [PATCH] lzo: security bump to version 2.07 Baruch Siach
2014-06-27 11:07 ` Peter Korsgaard
2014-06-27 11:26 ` Baruch Siach [this message]
2014-06-27 14:08 ` Peter Korsgaard
2014-06-27 18:36 ` Thomas Petazzoni
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=20140627112652.GC4155@tarshish \
--to=baruch@tkos.co.il \
--cc=buildroot@busybox.net \
/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.