From: pullmoll <pullmoll@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: ccache: update to 4.0 (alternative approach for chroot-cmake)
Date: Wed, 21 Oct 2020 04:26:22 +0200 [thread overview]
Message-ID: <20201021022622.c5jgQTYi7e561eUlWFe7ivpa0S8Yj2jIrPA695dyFyU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25753@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 279 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/pull/25753#issuecomment-713251623
Comment:
On a 2nd try the `./xbps-src zap` and `./xbps-src bootstrap` succeeded to build stage0. No idea what was causing the loop in the 1st try.
next prev parent reply other threads:[~2020-10-21 2:26 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 15:10 [PR PATCH] " sgn
2020-10-20 15:16 ` [PR REVIEW] " pullmoll
2020-10-20 15:18 ` pullmoll
2020-10-20 15:21 ` [PR PATCH] [Updated] " sgn
2020-10-20 15:23 ` [PR REVIEW] " sgn
2020-10-20 15:29 ` pullmoll
2020-10-20 15:36 ` sgn
2020-10-20 16:17 ` pullmoll
2020-10-20 16:18 ` pullmoll
2020-10-20 23:43 ` [PR PATCH] [Updated] " sgn
2020-10-20 23:43 ` [PR REVIEW] " sgn
2020-10-20 23:52 ` [PR PATCH] [Updated] " sgn
2020-10-20 23:58 ` [PR REVIEW] " sgn
2020-10-21 0:57 ` pullmoll
2020-10-21 0:59 ` pullmoll
2020-10-21 1:11 ` pullmoll
2020-10-21 1:24 ` [PR REVIEW] " q66
2020-10-21 2:26 ` pullmoll [this message]
2020-10-21 11:16 ` [PR PATCH] [Updated] " sgn
2020-10-21 14:18 ` [PR REVIEW] " sgn
2020-10-21 14:18 ` sgn
2020-10-21 14:42 ` pullmoll
2020-10-21 15:13 ` sgn
2020-10-21 15:14 ` sgn
2020-10-21 18:35 ` [PR REVIEW] " ericonr
2020-10-21 18:35 ` ericonr
2020-10-21 22:51 ` sgn
2020-10-21 22:55 ` sgn
2020-10-21 22:58 ` [PR PATCH] [Updated] " sgn
2020-10-22 11:00 ` sgn
2020-10-22 14:07 ` sgn
2020-10-23 9:51 ` [PR PATCH] [Merged]: " pullmoll
2020-11-01 0:33 ` Piraty
2020-11-01 0:34 ` Piraty
2020-11-01 0:55 ` sgn
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=20201021022622.c5jgQTYi7e561eUlWFe7ivpa0S8Yj2jIrPA695dyFyU@z \
--to=pullmoll@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).