From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] wireshark: security bump to version 1.8.7
Date: Mon, 20 May 2013 11:22:07 +0300 [thread overview]
Message-ID: <20130520082207.GE7188@tarshish> (raw)
In-Reply-To: <5199978C.3040702@zacarias.com.ar>
Hi Gustavo,
On Mon, May 20, 2013 at 12:25:00AM -0300, Gustavo Zacarias wrote:
> On 05/19/2013 11:55 PM, Baruch Siach wrote:
> > Have you seen an actual build failure caused by this missing dependency?
>
> No, it's unreachable because glib2 is always failing before with it's
> own fork()ing.
> It's used in capture_sync.c which is mandatory even for tshark, so it
> would fail even if glib2 worked.
OK, thanks. So, FWIW:
Acked-by: Baruch Siach <baruch@tkos.co.il>
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:[~2013-05-20 8:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-19 23:47 [Buildroot] [PATCH] wireshark: security bump to version 1.8.7 Gustavo Zacarias
2013-05-20 2:55 ` Baruch Siach
2013-05-20 3:25 ` Gustavo Zacarias
2013-05-20 8:22 ` Baruch Siach [this message]
2013-05-25 11:56 ` Peter Korsgaard
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=20130520082207.GE7188@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox