From: Dirkjan Ochtman <djc@gentoo.org>
To: Gentoo Development <gentoo-dev@lists.gentoo.org>
Cc: security@gentoo.org
Subject: Re: [gentoo-dev] Regarding long delays on GLSA generation
Date: Sat, 18 Jan 2014 17:33:36 +0100 [thread overview]
Message-ID: <CAKmKYaAtFGCr2nVUepBUN-VagU7wYt6szugcd2ZJ70cqbGvjjQ@mail.gmail.com> (raw)
In-Reply-To: <1390062615.24148.87.camel@belkin5>
On Sat, Jan 18, 2014 at 5:30 PM, Pacho Ramos <pacho@gentoo.org> wrote:
> What I want to achieve is to try to get this problem solved, I don't
> think has any sense to have pending GLSA bugs waiting for ages (yes,
> ages), I see this for really a lot of packages, the pointed one was only
> one example, but there are many more (like glib, dotnet stuff...)
From my perception, the security team in recent months has gone
through great lengths to improve the process and to work on the
backlog of old security bugs. AIUI, this *is* getting fixed, it just
takes some time to fix it properly.
Cheers,
Dirkjan
next prev parent reply other threads:[~2014-01-18 16:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-18 15:34 [gentoo-dev] Regarding long delays on GLSA generation Pacho Ramos
2014-01-18 16:02 ` Alex Legler
2014-01-18 16:30 ` Pacho Ramos
2014-01-18 16:33 ` Dirkjan Ochtman [this message]
2014-01-18 19:10 ` [gentoo-dev] " Duncan
2014-01-18 16:34 ` [gentoo-dev] " Pacho Ramos
2014-01-18 17:26 ` Alex Legler
2014-01-18 17:38 ` Pacho Ramos
2014-01-18 18:19 ` Alex Legler
2014-01-18 18:35 ` Pacho Ramos
2014-01-18 18:57 ` Pacho Ramos
-- strict thread matches above, loose matches on Subject: below --
2014-01-18 16:12 creffett
2014-01-18 18:57 Chris Reffett
[not found] <20140118185711.CFA13E0C62@pigeon.gentoo.org>
2014-01-18 19:08 ` Pacho Ramos
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=CAKmKYaAtFGCr2nVUepBUN-VagU7wYt6szugcd2ZJ70cqbGvjjQ@mail.gmail.com \
--to=djc@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=security@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