From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: GNU Debbugs <control@debbugs.gnu.org>, 67307@debbugs.gnu.org
Subject: bug#67307: Build of emacs-org-recent-headings and other emacs-org-* packages broken
Date: Wed, 22 Nov 2023 23:43:17 -0500 [thread overview]
Message-ID: <87zfz56pwa.fsf@gmail.com> (raw)
In-Reply-To: <87o7fokwik.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Mon, 20 Nov 2023 21:19:47 +0100")
merge 67307 54447
thanks
Hi Nicolas,
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Hello,
>
> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>
>> cuirass@gnu.org (Cuirass) writes:
>>
>>> <p>The build <b>emacs-org-recent-headings.i686-linux</b> for
>>> specification <b>master</b> is broken. You can find the detailed
>>> information about this build <a
>>> href="https://ci.guix.gnu.org/build/2603350/details">here</a>.</p>
>>>
>>> https://ci.guix.gnu.org/build/2603350/details
>>
>> This package and a few others appear to have broken following an update
>> to emacs-org [0].
>>
>> [0] https://ci.guix.gnu.org/eval/917321?status=failed
>
> Most packages report a missing substitute. Do you understand what is
> happening?
Ah, apologies, I should have inspected the logs. So that is the
unresolved Cuirass/build farm issue reported in
https://issues.guix.gnu.org/54447. Until it is fixed the builds must be
restarted manually else people will not have substitutes for them (at
least from Berlin).
Do you have the client certificate to do admin actions from Cuirass? If
not, I can provide you with one.
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-11-23 4:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1664@guix-ci.nnrss>
2023-11-20 19:19 ` bug#67307: Build of emacs-org-recent-headings and other emacs-org-* packages broken Maxim Cournoyer
2023-11-20 20:19 ` Nicolas Goaziou via Bug reports for GNU Guix
2023-11-23 4:43 ` Maxim Cournoyer [this message]
2023-11-24 18:53 ` Nicolas Goaziou via Bug reports for GNU Guix
2023-12-04 0:17 ` Maxim Cournoyer
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=87zfz56pwa.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=67307@debbugs.gnu.org \
--cc=control@debbugs.gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).