From: Marius Bakke <mbakke@fastmail.com>
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: 40383@debbugs.gnu.org
Subject: [bug#40383] [PATCH 0/5] Make some inputs native.
Date: Thu, 02 Apr 2020 18:01:32 +0200 [thread overview]
Message-ID: <87ftdlswpv.fsf@devup.no> (raw)
In-Reply-To: <877dyycknh.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 625 bytes --]
Mathieu Othacehe <m.othacehe@gmail.com> writes:
> Graphviz has 1370 dependencies, which makes it a candidate for
> core-updates branch that has been frozen recently. Maybe we can start a
> 'core-updates-next' branch. Marius, WDYT?
I've been meaning to rework the rebuild limits from the manual as a lot
has changed since that was written. In particular I want to keep "mesa"
on 'staging', but that has crept to almost 2000 rebuilds!
Perhaps we need another tier in between staging and core-updates, or
just aim for slower staging cycles (as has been de facto a while..).
Anyway for now I think this can go to 'staging'.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-04-02 16:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 23:20 [bug#40383] [PATCH 0/5] Make some inputs native Vincent Legoll
2020-04-01 23:22 ` [bug#40383] [PATCH 1/5] gnu: darktable: " Vincent Legoll
2020-04-01 23:22 ` [bug#40383] [PATCH 2/5] gnu: graphviz: " Vincent Legoll
2020-04-01 23:22 ` [bug#40383] [PATCH 3/5] gnu: iwd: " Vincent Legoll
2020-04-01 23:22 ` [bug#40383] [PATCH 4/5] gnu: mailutils: " Vincent Legoll
2020-04-01 23:22 ` [bug#40383] [PATCH 5/5] gnu: nethack: " Vincent Legoll
2020-04-02 9:16 ` [bug#40383] [PATCH 0/5] " Mathieu Othacehe
2020-04-02 16:01 ` Marius Bakke [this message]
2020-04-02 16:18 ` Mathieu Othacehe
2020-04-02 16:20 ` Mathieu Othacehe
2020-04-02 17:44 ` [bug#40383] numerous rebuilds Vincent Legoll
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=87ftdlswpv.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=40383@debbugs.gnu.org \
--cc=m.othacehe@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).