Build of emacs-org-recent-headings and other emacs-org-* packages broken

  • Done
  • quality assurance status badge
Details
2 participants
  • Nicolas Goaziou
  • Maxim Cournoyer
Owner
unassigned
Submitted by
Maxim Cournoyer
Severity
normal
M
M
Maxim Cournoyer wrote on 20 Nov 2023 20:19
(name . bug-guix)(address . bug-guix@gnu.org)
87jzqc9qqz.fsf@gmail.com
Hello!

cuirass@gnu.org (Cuirass) writes:

Toggle quote (5 lines)
> <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].


--
Thanks,
Maxim
N
N
Nicolas Goaziou wrote on 20 Nov 2023 21:19
(name . Maxim Cournoyer)(address . maxim.cournoyer@gmail.com)(address . 67307@debbugs.gnu.org)
87o7fokwik.fsf@nicolasgoaziou.fr
Hello,

Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:

Toggle quote (12 lines)
> 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?

Regards,
--
Nicolas Goaziou
M
M
Maxim Cournoyer wrote on 23 Nov 2023 05:43
(name . Nicolas Goaziou)(address . mail@nicolasgoaziou.fr)
87zfz56pwa.fsf@gmail.com
merge 67307 54447
thanks

Hi Nicolas,

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

Toggle quote (21 lines)
> 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
N
N
Nicolas Goaziou wrote on 24 Nov 2023 19:53
(name . Maxim Cournoyer)(address . maxim.cournoyer@gmail.com)
875y1rasr1.fsf@nicolasgoaziou.fr
Hello,

Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:

Toggle quote (3 lines)
> Do you have the client certificate to do admin actions from Cuirass? If
> not, I can provide you with one.

I don't have it. I'll also need some guidance to install it and use it
wisely…

Regards,
--
Nicolas Goaziou
M
M
Maxim Cournoyer wrote on 4 Dec 2023 01:17
(name . Nicolas Goaziou)(address . mail@nicolasgoaziou.fr)
87msuqvn1g.fsf@gmail.com
Hi,

Toggle quote (10 lines)
> Hello,
>
> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>
>> Do you have the client certificate to do admin actions from Cuirass? If
>> not, I can provide you with one.
>
> I don't have it. I'll also need some guidance to install it and use it
> wisely…

I will send it to you as soon as I get an up to date GPG key for your
email :-).

--
Thanks,
Maxim
M
M
Maxim Cournoyer wrote on 12 Nov 07:22 +0100
control message for bug #67307
(address . control@debbugs.gnu.org)
87o72l6kfb.fsf@gmail.com
close 67307
quit
?
Your comment

This issue is archived.

To comment on this conversation send an email to 67307@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 67307
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch