From: <znavko@tutanota.com>
Cc: 33737@debbugs.gnu.org
Subject: bug#33737: do not attempt to build a package known to be broken
Date: Sat, 15 Dec 2018 20:39:21 +0100 (CET) [thread overview]
Message-ID: <LTnNKXp--3-1@tutanota.com> (raw)
In-Reply-To: <20181215195437.32313415@alma-ubu>
[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]
Package can have additional fields in guix repository, like
architecture, version, buid_status, source_type
build_status may contain such info.
source_type could show if the package source url is one of those public git services (thus, user could enable proxy first).
Dec 15, 2018, 6:54 PM by bjoern.hoefling@bjoernhoefling.de:
> On Fri, 14 Dec 2018 05:41:37 +0100
> Ricardo Wurmus <> rekado@elephly.net <mailto:rekado@elephly.net>> > wrote:
>
>> The default use case is for users to have substitutes enabled and to
>> fetch binaries from a build farm. The build farm tries to build all
>> packages, but not all builds succeed. The daemon caches build
>> failures.
>>
>> This information, however, is not available for users. The default
>> behaviour of Guix is to attempt building the package locally. This is
>> fine for packages that the build farm hasn’t attempted yet, but it is
>> a waste of time when the build has already been attempted without
>> success.
>>
>
> +1
>
> Very good idea.
>
> Björn
>
[-- Attachment #2: Type: text/html, Size: 2534 bytes --]
next prev parent reply other threads:[~2018-12-15 19:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 4:41 bug#33737: do not attempt to build a package known to be broken Ricardo Wurmus
2018-12-15 18:54 ` Björn Höfling
2018-12-15 19:39 ` znavko [this message]
2018-12-16 20:14 ` Danny Milosavljevic
2018-12-16 21:55 ` Ricardo Wurmus
2018-12-18 10:50 ` 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=LTnNKXp--3-1@tutanota.com \
--to=znavko@tutanota.com \
--cc=33737@debbugs.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).