unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: linux-libre source tarballs
Date: Sun, 2 May 2021 00:42:31 -0400	[thread overview]
Message-ID: <YI4tt5UY4MLkl7QB@jasmine.lan> (raw)
In-Reply-To: <YI4SQtQSIQNvyApa@jasmine.lan>

On Sat, May 01, 2021 at 10:45:22PM -0400, Leo Famulari wrote:
> The immediate solution is for me to make sure the tarballs have built
> before committing the updates. I already do this for x86_64 and I can
> start doing it for aarch64 too.

I started building the current derivations "by hand" on the build farm
with a longer max-silent-time.

I'll check in a day or so if it succeeded and how long it took. We can
adjust the packages based on that to avoid "silent time" timeouts even
when I don't pre-build these tarballs.


  reply	other threads:[~2021-05-02  4:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-02  1:45 linux-libre source tarballs Vagrant Cascadian
2021-05-02  2:45 ` Leo Famulari
2021-05-02  4:42   ` Leo Famulari [this message]
2021-05-02 21:08     ` Ludovic Courtès
2021-05-02 22:26       ` Leo Famulari
2021-05-02 22:38         ` Leo Famulari
2021-05-03 15:44   ` linux-libre source tarballs (disable "deblob-check"?) Leo Famulari
2021-05-03 16:39   ` linux-libre source tarballs Alexandre Oliva
2021-05-03 17:13     ` Leo Famulari
2021-05-06  4:10       ` Alexandre Oliva
2021-05-06 21:23         ` Leo Famulari
2021-05-06 20:30     ` Maxim Cournoyer
2021-05-09  3:27       ` Alexandre Oliva
2021-05-30  4:50   ` Vagrant Cascadian
2021-05-31  3:42     ` Leo Famulari
2021-05-31 19:57       ` Mathieu Othacehe
2021-08-01 20:45     ` source tarballs potentially built for each derivation Vagrant Cascadian
2021-08-01 21:04       ` Vagrant Cascadian

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=YI4tt5UY4MLkl7QB@jasmine.lan \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=vagrant@debian.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).