From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: srcpkgs: mark broken packages to not waste time of build farm
Date: Tue, 26 May 2020 20:23:20 +0200 [thread overview]
Message-ID: <20200526182320.nSpqmObBYzyifP4Ehc4k_I752ss5C8Oh-UTTbUofsu4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22192@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/pull/22192#issuecomment-634195949
Comment:
A better way to solve this would be to clean things up on the builders. The only reason the builders are trying to build these every time is because it used to be built sometime in the past, and now the builders have it inside their state and attempt to rebuild them every time. But this should not be happening in the first place, the builders should stop trying once they see the dependency tree is not resolvable.
next prev parent reply other threads:[~2020-05-26 18:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 7:12 [PR PATCH] " sgn
2020-05-22 7:34 ` [PR PATCH] [Updated] " sgn
2020-05-22 7:36 ` sgn
2020-05-22 10:45 ` sgn
2020-05-22 23:56 ` fosslinux
2020-05-22 23:57 ` fosslinux
2020-05-23 1:34 ` sgn
2020-05-25 14:06 ` ericonr
2020-05-25 15:56 ` sgn
2020-05-26 6:31 ` fosslinux
2020-05-26 7:45 ` travankor
2020-05-26 15:30 ` [PR PATCH] [Updated] " sgn
2020-05-26 15:30 ` sgn
2020-05-26 18:23 ` q66 [this message]
2020-05-27 0:04 ` sgn
2020-05-27 0:05 ` [PR PATCH] [Closed]: " sgn
2020-05-27 0:58 ` ericonr
2020-05-27 12:34 ` sgn
2020-05-29 0:38 ` ericonr
2020-05-29 1:02 ` sgn
2020-05-29 2:25 ` ericonr
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200526182320.nSpqmObBYzyifP4Ehc4k_I752ss5C8Oh-UTTbUofsu4@z \
--to=q66@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).