From: divoplade <d@divoplade.fr>
To: zimoun <zimon.toutoune@gmail.com>, 43093@debbugs.gnu.org
Subject: bug#43093: Is Emacs 27.1 that breaks emacs-ess?
Date: Fri, 04 Sep 2020 17:26:41 +0200 [thread overview]
Message-ID: <990023fbe6d2c7c3cb7d994077bc990dabef2e1b.camel@divoplade.fr> (raw)
In-Reply-To: <CAJ3okZ1g=zR7xotbjjxqefnxgPmX0txeBOddoRZ4BTGv85xR=w@mail.gmail.com>
Hello,
Le vendredi 04 septembre 2020 à 16:44 +0200, zimoun a écrit :
> But the commit 36a09d1853 introducing Emacs 27 had been pushed on Fri
> Aug 28
> 00:13:51 2020 -0400 and the CI reported failures before this
> offending
> commit.
>
> https://ci.guix.gnu.org/search?query=spec%3Aguix-master+system%3Ax86_64-linux+emacs-ess
>
> For other examples, see:
>
> https://data.guix.gnu.org/repository/1/branch/master/package/emacs-ess/output-history
>
> reporting issues both on Berlin and Bayfront and before the push of
> Emacs 27.
>
Well, you must be right. I did not think it out long enough. It broke
at the same time I saw the emacs update, so I inferred it incorrectly.
Is it possible to edit the title?
>
> Note that the parent commit c05d2cfcbd builds successfully on my
> machine. Therefore, I do not know from where the failure comes from.
I can't find such a commit ID. It does not seem to exist in the git
repo. Do you know the date, author or committer?
next prev parent reply other threads:[~2020-09-04 16:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 20:07 bug#43093: emacs-ess is broken by emacs 27.1 divoplade
2020-09-04 14:44 ` bug#43093: Is Emacs 27.1 that breaks emacs-ess? zimoun
2020-09-04 15:26 ` divoplade [this message]
2020-09-04 17:00 ` Mark H Weaver
2020-09-04 18:09 ` zimoun
2020-09-04 18:25 ` bug#43093: emacs-ess is broken by emacs 27.1 Tim Howes via Bug reports for GNU Guix
2020-09-07 21:19 ` divoplade
2020-09-07 21:43 ` divoplade
2020-09-07 21:52 ` divoplade
2020-09-08 19:24 ` Tim Howes via Bug reports for GNU Guix
2020-09-04 23:25 ` bug#43093: [PATCH] gnu: emacs-ess: Update to 20200903.1516 Tim Howes via Bug reports for GNU Guix
2020-09-28 3:28 ` 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=990023fbe6d2c7c3cb7d994077bc990dabef2e1b.camel@divoplade.fr \
--to=d@divoplade.fr \
--cc=43093@debbugs.gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).