All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] lzo: security bump to version 2.07
Date: Sun, 29 Jun 2014 06:45:13 -0500	[thread overview]
Message-ID: <20140629064513.7a946d43@core2quad.morethan.org> (raw)
In-Reply-To: <178793dde59515317a045893c8e0c090be510fcf.1404017271.git.baruch@tkos.co.il>

On Sun, 29 Jun 2014 07:47:51 +0300
Baruch Siach <baruch@tkos.co.il> wrote:

> Fixes CVE-2014-4607.
> 
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> v2:
>    Rephrase the comment explaining the need for AUTORECONF (Peter).
> ---
>  package/lzo/lzo.mk | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/package/lzo/lzo.mk b/package/lzo/lzo.mk
> index 10107fea3be3..3b348a3eff30 100644
> --- a/package/lzo/lzo.mk
> +++ b/package/lzo/lzo.mk
> @@ -4,11 +4,14 @@
>  #
>  ################################################################################
>  
> -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
> +# Out libtool patch does not apply to bundled ltmain.sh since it's too new.
s/out/our/

Two things mentioned in sentence, which of them is "too new"?

 try: "Our libtool patch is too new to apply to the bundled ltmain.sh"

> +# Run autoreconf to regenerate ltmain.sh.
> +LZO_AUTORECONF = YES
>  
>  $(eval $(autotools-package))
>  $(eval $(host-autotools-package))

  parent reply	other threads:[~2014-06-29 11:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-29  4:47 [Buildroot] [PATCH v2] lzo: security bump to version 2.07 Baruch Siach
2014-06-29 10:05 ` Thomas Petazzoni
2014-06-29 11:45 ` Mike Zick [this message]
2014-06-29 11:54   ` Baruch Siach

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=20140629064513.7a946d43@core2quad.morethan.org \
    --to=minimod@morethan.org \
    --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.