From: Tim Cross <theophilusx@gmail.com>
To: Daniel Ortmann <daniel.ortmann@oracle.com>
Cc: Ihor Radchenko <yantar92@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: [External] : Re: org-mode compile issue this morning - how to report this?
Date: Fri, 26 Aug 2022 08:50:16 +1000 [thread overview]
Message-ID: <86h7202asu.fsf@gmail.com> (raw)
In-Reply-To: <230c1073-2f55-aae6-c98a-9da2abfc0b16@oracle.com>
Emacs 29.1 refers to the first release of Emacs 29, which has not yet
occurred. Emacs 29.0.50 refers to version 29 of emacs which has not yet
had a release candidate issued i.e. still very much development and not
yet at beta level. Once the first release candidate is issued, the
version will likely change to 29.0.90 and then once actually released,
to 29.1.
Given that 29.0.50 at this point just means development version (and
unless a commit hash is also included, head of the devel branch), you
can assume the bug fix will be in 29.0.50 provided you have done a pull
since that bug fix notice was posted.
Daniel Ortmann <daniel.ortmann@oracle.com> writes:
> FYI,
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=57394
>
> Lars at gnu says it is fixed in emacs 29
> The bug's web page says, more specifically, "bug marked as fixed in version 29.1"
>
> ... I can't find emacs 29.1; my 'git pull' still says 29.0 and I don't see any 29.1 branches available.
> I have not been able to test and verify the fix.
>
> Thoughts?
>
> Daniel Ortmann <daniel.ortmann@oracle.com> writes:
>
> Error: error ("Eager macro-expansion failure: (void-function
> byte-compile-warn-obsolete)")
> debug-early-backtrace()
> debug-early(error (error "Eager macro-expansion failure:
> (void-function byte-compile-warn-obsolete)"))
>
> This should now be fixed in Emacs 29.
prev parent reply other threads:[~2022-08-25 23:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 19:36 org-mode compile issue this morning - how to report this? Daniel Ortmann
2022-08-23 2:26 ` Ihor Radchenko
2022-08-23 6:38 ` Tim Cross
2022-08-23 7:28 ` Ihor Radchenko
2022-08-24 22:15 ` [External] : " Daniel Ortmann
2022-08-25 14:36 ` Daniel Ortmann
2022-08-25 17:37 ` Daniel Ortmann
2022-08-25 20:26 ` Gregor Zattler
2022-08-25 22:50 ` Tim Cross [this message]
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://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86h7202asu.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=daniel.ortmann@oracle.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@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/emacs/org-mode.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).