From: Pierre Langlois <pierre.langlois@gmx.com>
To: Pierre Langlois <pierre.langlois@gmx.com>
Cc: 45448@debbugs.gnu.org
Subject: bug#45448: Emacs can't load org mode after last update
Date: Sun, 27 Dec 2020 13:07:48 +0000 [thread overview]
Message-ID: <87pn2vbdnf.fsf@gmx.com> (raw)
In-Reply-To: <875z4nlddy.fsf@gmx.com>
[-- Attachment #1: Type: text/plain, Size: 4727 bytes --]
Pierre Langlois writes:
> Hi!
>
> Marinus Savoritias writes:
>
>> I update Guix yesterday and org-mode doesn't load anymore.
>>
>> The debug trace is this:
>>
>> Debugger entered--Lisp error: (error "Invalid version syntax: ‘’ (must start
>> with a number)")
>> signal(error ("Invalid version syntax: ‘’ (must start with a number)"))
>> error("Invalid version syntax: `%s' (must start with a number)" "")
>> version-to-list("")
>> version<("" "9.0")
>> #f(compiled-function () #<bytecode 0x5c3b49>)()
>> funcall(#f(compiled-function () #<bytecode 0x5c3b49>))
>> (lambda nil (funcall '#f(compiled-function () #<bytecode 0x5c3b49>)))()
>> eval-after-load-helper("/home/marinus/.guix-profile/share/emacs/site-lisp/org.elc")
>> run-hook-with-args(eval-after-load-helper
>> "/home/marinus/.guix-profile/share/emacs/site-lisp/org.elc")
>> do-after-load-evaluation("/home/marinus/.guix-profile/share/emacs/site-lisp/org.elc")
>> require(org)
>> byte-code("\300\301!\210\300\302!\210\300\303!\210\300\304!\210\300\305!\210\300\306!\210\307\310\311\312\313\314%\210\315\316\317\320\313\310\321\322&\7\210\315\323\324\325\313\310\321..."
>> [require elfeed org dash s cl-lib xml custom-declare-group elfeed-org
>> nil "Configure the Elfeed RSS reader with an Orgmode fi..." :group comm
>> custom-declare-variable rmh-elfeed-org-tree-id "elfeed" "The tag or ID
>> property on the trees containing the..." :type string rmh-elfeed-org-ignore-tag
>> "ignore" "The tag on the feed trees that will be ignored."
>> rmh-elfeed-org-auto-ignore-invalid-feeds "Tag feeds to ignore them when a feed
>> could not loa..." bool rmh-elfeed-org-files (list "~/.emacs.d/elfeed.org") "The
>> files where we look to find trees with the `rm..." (repeat (file :tag "org-mode
>> file"))] 8)
>> require(elfeed-org)
>> eval-buffer(#<buffer *load*> nil "/home/marinus/.emacs" nil t) ; Reading at
>> buffer position 39
>> load-with-code-conversion("/home/marinus/.emacs" "/home/marinus/.emacs" t t)
>> load("~/.emacs" noerror nomessage)
>> startup--load-user-init-file(#f(compiled-function () #<bytecode 0x5c3f71>)
>> #f(compiled-function () #<bytecode 0x5c3f85>) t)
>> command-line()
>> normal-top-level()
>>
>> Everytime I try to open a org file I get the same error. I noticed that after I
>> removed the elfeed-org requirement to see if that was the problem.
>>
>> Emacs commit is this: /gnu/store/lhw3zwhzra0w5l8a4jw8fvm58i75xyl8-emacs-27.1
>>
>> Guix System config is this:
>>
>> Generation 15 Dec 26 2020 15:25:17 (current)
>> guix 4969b51
>> repository URL: https://git.savannah.gnu.org/git/guix.git
>> branch: master
>> commit: 4969b51d175497bfcc354c91803e9d70542b7113
>>
>> My .emacs file has nothing besides this:
>>
>> ;;Elfeed config
>>
>> (require 'elfeed-org)
>> (setq rmh-elfeed-org-files (list "~/.emacs.d/elfeed.org"))
>
> I also hit this issue yesterday :-/. To fix it, I found you could make
> sure to have (require 'org) *before* loading other packages that
> depended on org. Would that work for you? I'm using use-package, so the
> particular fix for me was to add ":after org" on every package
> declaration that needed to use org.
>
> There's still an issue upstream I think, probably due to a mis-match
> between the org that's shipped in emacs and the newer one in guix?
Actually, it started failing again just after I sent this message... It
seems reordering require didn't actually fix anything, sorry!
Looking into it a little bit more, it seems there was an issue with the
version reporting, if you try and evaluate (org-version), it returns an
empty string, then causing the original backtrace.
There seems to be an issue when building the package, I see the result
of (org-version) should be defined at build-time: https://code.orgmode.org/bzg/org-mode/src/master/mk/default.mk#L118
But we don't do it properly:
--8<---------------cut here---------------start------------->8---
$ cat $(guix build emacs-org)/share/emacs/site-lisp/org-version.el
;;; org-version.el --- autogenerated file, do not edit
;;
;;; Code:
;;;###autoload
(defun org-release ()
"The release version of Org.
Inserted by installing Org mode or when a release is made."
(let ((org-release ""))
org-release))
;;;###autoload
(defun org-git-version ()
"The Git version of Org mode.
Inserted by installing Org or when a release is made."
(let ((org-git-version ""))
org-git-version))
(provide 'org-version)
--8<---------------cut here---------------end--------------->8---
I'll see if I can spot anything going wrong during the build process.
Thanks,
Pierre
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 519 bytes --]
next prev parent reply other threads:[~2020-12-27 13:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-26 17:42 bug#45448: Emacs can't load org mode after last update Marinus Savoritias
2020-12-27 9:19 ` Michael Rohleder
2020-12-27 11:03 ` Pierre Langlois
2020-12-27 13:07 ` Pierre Langlois [this message]
2020-12-28 13:21 ` Pierre Langlois
2020-12-28 15:04 ` Nicolas Goaziou
2020-12-28 16:34 ` Pierre Langlois
2021-01-15 21:53 ` Michael Rohleder
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=87pn2vbdnf.fsf@gmx.com \
--to=pierre.langlois@gmx.com \
--cc=45448@debbugs.gnu.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.
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).