From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id E7565138247 for ; Sat, 18 Jan 2014 15:34:45 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DD0BDE0A87; Sat, 18 Jan 2014 15:34:40 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id E418BE0839 for ; Sat, 18 Jan 2014 15:34:39 +0000 (UTC) Received: from [192.168.1.33] (182.Red-2-137-18.dynamicIP.rima-tde.net [2.137.18.182]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: pacho) by smtp.gentoo.org (Postfix) with ESMTPSA id 5348B33F98D; Sat, 18 Jan 2014 15:34:38 +0000 (UTC) Message-ID: <1390059274.24148.80.camel@belkin5> Subject: [gentoo-dev] Regarding long delays on GLSA generation From: Pacho Ramos To: gentoo-dev@lists.gentoo.org Cc: security@gentoo.org Date: Sat, 18 Jan 2014 16:34:34 +0100 Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.8.5 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Archives-Salt: 3b5778c9-99d0-4f3a-bca3-33cbc278d0ce X-Archives-Hash: 245cc3f55c7210ed5fa4bec6eb3b7f2a Was looking to existing gedit bug reports and I found: https://bugs.gentoo.org/show_bug.cgi?id=257004 That is only one more example of a really old bug report still opened and waiting for a GLSA. Was wondering what really causes this long delays, can't GLSA be done automatically? Would a GLSA even have any sense for cases like this (after 5 years) Thanks for your help