From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: 65391@debbugs.gnu.org, atai@atai.org, maximedevos@telenet.be,
iyzsong@envs.net, mirai@makinata.eu, raingloom@riseup.net
Subject: bug#65391: Acknowledgement (People need to report failing builds even though we have ci.guix.gnu.org for that)
Date: Wed, 30 Aug 2023 15:12:08 -0400 [thread overview]
Message-ID: <87bkeo73av.fsf@gmail.com> (raw)
In-Reply-To: <871qfkg65s.fsf@web.de> (Arne Babenhauserheide's message of "Wed, 30 Aug 2023 12:39:09 +0200")
Hi Arne,
"Dr. Arne Babenhauserheide" <arne_bab@web.de> writes:
[...]
> Please don’t remove packages that are broken on the CI. I often had a
> case where no substitute was available but the package built just fine
> locally. This is not a perfect situation (nicer would be to track why it
> doesn’t come from CI — sometimes it’s just a resource problem on the
> CI), but if you removed a package I use that would break all updates for
> me.
I agree! It'd be important, if we decide to have such a policy, to add
add guards such that packages are only removed as a last resort, after
options have been considered, and when it's been broken for a while with
an issue opened for it, and when it's a real problem with the package,
not with our CI.
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-08-30 19:13 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-19 23:53 bug#65391: People need to report failing builds even though we have ci.guix.gnu.org for that Maxime Devos
2023-08-22 23:45 ` Csepp
2023-08-24 9:57 ` Simon Tournier
2023-08-24 17:23 ` Csepp
2023-08-24 14:52 ` Maxime Devos
2023-08-24 17:27 ` Csepp
2023-08-29 22:52 ` Maxime Devos
2023-08-30 2:36 ` Maxim Cournoyer
2023-08-24 15:02 ` Maxime Devos
2023-08-24 17:38 ` Csepp
2023-08-27 1:13 ` 宋文武
2023-08-27 3:38 ` Maxim Cournoyer
2023-08-27 8:16 ` bug#65391: [Cuirass] feature requests for dashboard 宋文武 via Bug reports for GNU Guix
2023-08-27 3:39 ` bug#65391: People need to report failing builds even though we have ci.guix.gnu.org for that Maxim Cournoyer
2023-08-27 4:30 ` Bruno Victal
2023-08-27 15:07 ` Giovanni Biscuolo
2023-08-27 16:24 ` bug#65391: People need to report failing builds even Andy Tai
2023-08-27 21:26 ` Andy Tai
[not found] ` <handler.65391.B.169248925726403.ack@debbugs.gnu.org>
2023-08-29 14:03 ` bug#65391: Acknowledgement (People need to report failing builds even though we have ci.guix.gnu.org for that) Maxime Devos
2023-08-29 14:45 ` Maxim Cournoyer
2023-08-29 22:44 ` Maxime Devos
2023-08-30 2:28 ` Maxim Cournoyer
2023-08-30 10:39 ` Dr. Arne Babenhauserheide
2023-08-30 19:12 ` Maxim Cournoyer [this message]
2023-09-07 11:53 ` Simon Tournier
2023-09-11 8:30 ` Dr. Arne Babenhauserheide
2023-09-11 14:00 ` Simon Tournier
2023-09-11 23:12 ` Dr. Arne Babenhauserheide
2023-09-12 0:39 ` Simon Tournier
2023-08-30 11:50 ` Maxime Devos
2023-09-07 11:32 ` Simon Tournier
2023-09-11 7:28 ` bug#65391: People need to report failing builds even though we have ci.guix.gnu.org for that Csepp
2023-09-11 7:58 ` Simon Tournier
2023-09-11 21:52 ` Csepp
2023-09-12 18:43 ` bug#65391: Acknowledgement (People need to report failing builds even though we have ci.guix.gnu.org for that) Maxime Devos
2023-08-30 10:29 ` 宋文武 via Bug reports for GNU Guix
2024-02-14 9:13 ` bug#65391: Close Andreas Enge
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=87bkeo73av.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=65391@debbugs.gnu.org \
--cc=arne_bab@web.de \
--cc=atai@atai.org \
--cc=iyzsong@envs.net \
--cc=maximedevos@telenet.be \
--cc=mirai@makinata.eu \
--cc=raingloom@riseup.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.