From: Sebastian Pipping <sping@gentoo.org>
To: Samuli Suominen <ssuominen@gentoo.org>
Cc: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Re: [gentoo-dev-announce] Lastrite: 4suite, amara and testoob (mostly for security)
Date: Wed, 16 May 2012 21:31:02 +0200 [thread overview]
Message-ID: <4FB40076.10608@gentoo.org> (raw)
In-Reply-To: <4FB3681A.1030303@gentoo.org>
On 05/16/2012 10:40 AM, Samuli Suominen wrote:
> # Samuli Suominen <ssuominen@gentoo.org> (16 May 2012)
> # Internal copy of vulnerable dev-libs/expat wrt #250930,
> # CVE-2009-{3720,3560} and CVE-2012-{0876,1147,1148}.
> #
> # Fails to compile wrt bug #368089
> # Bad migration away from dev-python/pyxml wrt #367745
> #
> # Removal in 30 days.
> dev-python/4suite
Can I veto on 4suite (without fixing things myself yet) ?
Thanks,
Sebastian
next prev parent reply other threads:[~2012-05-16 19:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 8:40 [gentoo-dev] Lastrite: 4suite, amara and testoob (mostly for security) Samuli Suominen
2012-05-16 19:31 ` Sebastian Pipping [this message]
2012-05-16 21:56 ` [gentoo-dev] Re: [gentoo-dev-announce] " Samuli Suominen
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=4FB40076.10608@gentoo.org \
--to=sping@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=ssuominen@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