unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Policy to remove obsolete packages
Date: Tue, 5 Feb 2019 00:47:42 +0100	[thread overview]
Message-ID: <CAJ3okZ2B=K_qh0JON7teC+yrBp2pQ-RszRPaGD1LKMHKRXtSCw@mail.gmail.com> (raw)
In-Reply-To: <20190204221804.GA8806@jasmine.lan>

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

  reply	other threads:[~2019-02-04 23:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-04 11:16 Policy to remove obsolete packages Björn Höfling
2019-02-04 11:51 ` Pjotr Prins
2019-02-04 18:06 ` Andreas Enge
2019-02-04 22:18   ` Leo Famulari
2019-02-04 23:47     ` zimoun [this message]
2019-02-05 10:24       ` Björn Höfling
2019-02-07 12:40         ` zimoun
2019-02-08  8:47           ` Björn Höfling
2019-02-04 22:52 ` Ludovic Courtès
2019-02-05 10:13   ` Björn Höfling
2019-02-05 21:31     ` ng0
2019-02-05 22:47       ` swedebugia
2019-02-05 23:52         ` ng0
2019-02-06 22:32         ` Ricardo Wurmus
2019-02-07 12:42           ` swedebugia

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJ3okZ2B=K_qh0JON7teC+yrBp2pQ-RszRPaGD1LKMHKRXtSCw@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).