From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: core-updates, let’s go!
Date: Wed, 3 Jan 2018 15:06:59 -0500 [thread overview]
Message-ID: <20180103200659.GA9853@jasmine.lan> (raw)
In-Reply-To: <20180103183531.GA28138@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 430 bytes --]
On Wed, Jan 03, 2018 at 01:35:31PM -0500, Leo Famulari wrote:
> Libtiff failed the first build attempt when the upstream FTP server
> timed out. It has succeeded since then, but this will have caused a lot
> of dependent packages to fail.
>
> Should I "Restart all dependency failed builds" now?
I went ahead and did this because it was too hard to failed packages
that did not fail due to the earlier libtiff problem.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-01-03 20:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-31 10:27 core-updates, let’s go! Ludovic Courtès
2017-12-31 10:32 ` Efraim Flashner
2017-12-31 11:14 ` Danny Milosavljevic
2017-12-31 12:20 ` Danny Milosavljevic
2017-12-31 15:07 ` Marius Bakke
2017-12-31 17:27 ` Ricardo Wurmus
2018-01-02 18:12 ` change to the wrap-program procedure (was: core-updates, let’s go!) Hartmut Goebel
2018-01-02 19:01 ` Ricardo Wurmus
2018-01-02 19:19 ` change to the wrap-program procedure Hartmut Goebel
2018-01-02 20:47 ` Ricardo Wurmus
2017-12-31 14:44 ` core-updates, let’s go! Marius Bakke
2018-01-01 17:12 ` Ludovic Courtès
2018-01-01 19:08 ` Efraim Flashner
2018-01-03 18:35 ` Leo Famulari
2018-01-03 20:06 ` Leo Famulari [this message]
2018-01-03 19:34 ` Leo Famulari
2018-01-18 3:50 ` Leo Famulari
2018-01-20 0:51 ` core-updates: SELinux Leo Famulari
2018-01-28 12:32 ` Ricardo Wurmus
2018-01-20 20:57 ` core-updates, let’s go! Kei Kebreau
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=20180103200659.GA9853@jasmine.lan \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--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).