unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Giovanni Biscuolo <g@xelera.eu>
To: "Bruno Victal" <mirai@makinata.eu>, 宋文武 <iyzsong@envs.net>,
	"Maxime Devos" <maximedevos@telenet.be>
Cc: 65391@debbugs.gnu.org, guix-devel@gnu.org
Subject: Re: bug#65391: People need to report failing builds even though we have ci.guix.gnu.org for that
Date: Sun, 27 Aug 2023 17:07:31 +0200	[thread overview]
Message-ID: <87sf84a5ho.fsf@xelera.eu> (raw)
In-Reply-To: <283d99d4-4682-4577-b69c-f064ff5cd179@makinata.eu>

[-- Attachment #1: Type: text/plain, Size: 874 bytes --]

Bruno Victal <mirai@makinata.eu> writes:

> On 2023-08-27 02:13, 宋文武 wrote:
>> Maybe we can automatically report the failures as bugs, say every 7
>> days, and remove a package if it still fail to build in 90 days?

maybe precedeed by an automated email notification (to guix-bugs) so
that interested people have the chance to step in and fix it?

> I'm not so sure about removing packages, personally if I'm in need of
> a package that happens to be broken I find it easier to fix it given
> that some work has already been put into writing the package definition
> than starting from scratch.

You don't need to start from scratch if you want, you just have to
checkout the right git commit (before the package was deleted) and start
from that, if needed: WDYT?

Happy hacking! Gio'

[...]

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]

      reply	other threads:[~2023-08-27 15:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <295ef8c8-574a-4169-98f3-6d9aaeb773f1@telenet.be>
2023-08-27  1:13 ` bug#65391: People need to report failing builds even though we have ci.guix.gnu.org for that 宋文武
2023-08-27  3:38   ` Maxim Cournoyer
2023-08-27  3:39   ` Maxim Cournoyer
2023-08-27  4:30   ` Bruno Victal
2023-08-27 15:07     ` Giovanni Biscuolo [this message]

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=87sf84a5ho.fsf@xelera.eu \
    --to=g@xelera.eu \
    --cc=65391@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=iyzsong@envs.net \
    --cc=maximedevos@telenet.be \
    --cc=mirai@makinata.eu \
    /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).