public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Harald van Dijk" <truedfx@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] lastrite: www-client/kazehakase
Date: Sat, 26 Jun 2010 11:48:17 +0200	[thread overview]
Message-ID: <20100626094713.GA7299@boostbox> (raw)
In-Reply-To: <4C25BBE9.6090000@gentoo.org>

On Sat, Jun 26, 2010 at 11:35:29AM +0300, Samuli Suominen wrote:
> nothing usable left in tree.
> 
> # Samuli Suominen <ssuominen@gentoo.org> (26 Jun 2010)
> # Masked for QA
> #
> # Fails to compile with stable xulrunner, see bug 317275
> # Fails to compile with GTK+-2.20, see bug 325661
> # Ignores LDFLAGS, see bug 268491
> # Current stable is using vulnerable xulrunner, see bug 324953
> #
> # Removal in 30 days
> www-client/kazehakase

In case anyone is interested in picking this up, I've attached the
patches from upstream for xulrunner and gtk+ to their bugs. With those,
it's at least possible to get kazehakase to build, run, and display web
pages.



      reply	other threads:[~2010-06-26  9:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-26  8:35 [gentoo-dev] lastrite: www-client/kazehakase Samuli Suominen
2010-06-26  9:48 ` Harald van Dijk [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=20100626094713.GA7299@boostbox \
    --to=truedfx@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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