From: Ricardo Wurmus <rekado@elephly.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 43075@debbugs.gnu.org, chaosmonk@riseup.net
Subject: bug#43075: Prioritize providing substitutes for security-critical packages with potentially long build times
Date: Fri, 11 Sep 2020 10:23:36 +0200 [thread overview]
Message-ID: <87h7s43enr.fsf@elephly.net> (raw)
In-Reply-To: <CAJ3okZ30O-Y-1QyKymxwGh6WCcxKiqKizogiT=A5Sy76Ef3gVA@mail.gmail.com>
zimoun <zimon.toutoune@gmail.com> writes:
> I understand the annoyance and the frustration of the substitutes
> availability but I am not convinced that some packages have higher
> priority on the substitute delivery than others.
Hard to say. I think this discussion is a little premature given our
historic underutilization of the build farm hardware, which is very
often idle. Perhaps once the instrumentation of Cuirass has yielded
actionable paths to improving this we can reconsider if priorization is
still necessary or even feasible.
--
Ricardo
next prev parent reply other threads:[~2020-09-11 8:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 20:50 bug#43075: Prioritize providing substitutes for security-critical packages with potentially long build times chaosmonk
2020-09-10 8:00 ` Ludovic Courtès
2020-09-10 9:19 ` zimoun
2020-09-11 0:47 ` Bengt Richter
2020-09-11 1:06 ` Mason Hock
2020-09-11 6:56 ` Ludovic Courtès
2020-09-11 7:37 ` zimoun
2020-09-11 8:23 ` Ricardo Wurmus [this message]
2020-09-11 13:39 ` Leo Famulari
2020-09-11 14:33 ` Dr. Arne Babenhauserheide
2020-09-11 14:45 ` Ludovic Courtès
2020-09-11 1:14 ` Mason Hock
2020-09-11 6:53 ` Ludovic Courtès
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=87h7s43enr.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=43075@debbugs.gnu.org \
--cc=chaosmonk@riseup.net \
--cc=zimon.toutoune@gmail.com \
/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).