From mboxrd@z Thu Jan  1 00:00:00 1970
From: zimoun <zimon.toutoune@gmail.com>
Subject: Re: Policy to remove obsolete packages
Date: Tue, 5 Feb 2019 00:47:42 +0100
Message-ID: <CAJ3okZ2B=K_qh0JON7teC+yrBp2pQ-RszRPaGD1LKMHKRXtSCw@mail.gmail.com>
References: <20190204100318.208254da@alma-ubu> <20190204180635.GB8736@jurong>
	<20190204221804.GA8806@jasmine.lan>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([209.51.188.92]:58211)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <zimon.toutoune@gmail.com>) id 1gqnxz-0001GX-Nf
	for guix-devel@gnu.org; Mon, 04 Feb 2019 18:47:56 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <zimon.toutoune@gmail.com>) id 1gqnxz-0003B5-3B
	for guix-devel@gnu.org; Mon, 04 Feb 2019 18:47:55 -0500
Received: from mail-qk1-x72a.google.com ([2607:f8b0:4864:20::72a]:36163)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <zimon.toutoune@gmail.com>)
	id 1gqnxy-0003Ak-V0
	for guix-devel@gnu.org; Mon, 04 Feb 2019 18:47:55 -0500
Received: by mail-qk1-x72a.google.com with SMTP id o125so1099216qkf.3
	for <guix-devel@gnu.org>; Mon, 04 Feb 2019 15:47:54 -0800 (PST)
In-Reply-To: <20190204221804.GA8806@jasmine.lan>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel <guix-devel@gnu.org>

Dear,

I agree too on the policy.

On Mon, 4 Feb 2019 at 23:26, Leo Famulari <leo@famulari.name> wrote:
>
> It might be tricky to know when a package has failed to build for 6
> months. Do we keep build farm evaluations for that long? Can we automate
> failure notifications after a certain date?

I agree.
To me the question is more about how to automatically detect that a
patch breaks another package than a policy to remove a broken package.

I mean if we are able to automatically detect 6 months later that a
package is broken, why are we not able to report the failure earlier?
And if it is not automatic, this means that someone reports  the
failure by hand, so somehow this patch is important to them and then
why remove it?




All the best,
simon