From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 43075@debbugs.gnu.org, chaosmonk <chaosmonk@riseup.net>
Subject: bug#43075: Prioritize providing substitutes for security-critical packages with potentially long build times
Date: Fri, 11 Sep 2020 09:37:59 +0200 [thread overview]
Message-ID: <CAJ3okZ30O-Y-1QyKymxwGh6WCcxKiqKizogiT=A5Sy76Ef3gVA@mail.gmail.com> (raw)
In-Reply-To: <878sdg7qej.fsf@gnu.org>
Hi,
On Fri, 11 Sep 2020 at 08:56, Ludovic Courtès <ludo@gnu.org> wrote:
> > The recent updates of ungoogled-chromium do not mention [security
> > updates]. Well, I do not know if they are. So the question would be:
> > what triggers the special security build?
>
> To me the proposal is more about introducing scheduling priorities. For
> these packages, it’s indeed safe to assume that every new release brings
> security fixes.
Why would some packages be prioritized on the build farm than others?
Based on what? Which criteria?
Popularity? But we do not measure (yet?) how many times a substitute
is downloaded.
For example, I do not use ungoogled-chromium so I would prefer that
the resources of the build farm would be spent on these X packages.
Bob and Alice, they would prefer these Y packages. How do we reach a
consensus?
And security is one criteria. But how to detect it is a security fix?
(Aside the issue of ungoogled-chromium about the time limit you
described; which should be fixed, obviously. :-))
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.
All the best,
simon
next prev parent reply other threads:[~2020-09-11 7:39 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 [this message]
2020-09-11 8:23 ` Ricardo Wurmus
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='CAJ3okZ30O-Y-1QyKymxwGh6WCcxKiqKizogiT=A5Sy76Ef3gVA@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=43075@debbugs.gnu.org \
--cc=chaosmonk@riseup.net \
--cc=ludo@gnu.org \
/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).