emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Kyle Meyer <kyle@kyleam.com>
Cc: Bastien <bzg@gnu.org>, Pierre Langlois <pierre.langlois@gmx.com>,
	emacs-orgmode@gnu.org
Subject: Re: Bug: (org-release) returns empty string on Elpa [ ( @ /home/pierre/.guix-profile/share/emacs/site-lisp/)]
Date: Wed, 06 Jan 2021 10:36:53 -0500	[thread overview]
Message-ID: <jwvim8at72z.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <8735zezpf2.fsf@kyleam.com> (Kyle Meyer's message of "Wed, 06 Jan 2021 03:59:14 GMT")

>> Since the latest update to 9.4.4, some of us in Guix have been
>> experiencing issues with loading packages that depend on Org [0]. It
>> seems the root of the problem is that (org-release) returns an empty
>> string, you can see this manifesting in this email actually :-).
[...]
> In between those two releases, there seems to have been some
> restructuring on ELPA's end, in particular ee03829f90 (Finalize the new
> master branch, 2020-12-14).

Indeed that's the origin of the problem.

I don't know exactly how `org-version.el` is created and how the release
version is extracted&inserted, so I'm not sure how to fix it.

The approach I'd advocate would be to use `package-get-version` (or
something similar since `package-get-version` doesn't exist in
Emacs<27).


        Stefan



  reply	other threads:[~2021-01-06 15:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-28 10:27 Bug: (org-release) returns empty string on Elpa [ ( @ /home/pierre/.guix-profile/share/emacs/site-lisp/)] Pierre Langlois
2021-01-06  3:59 ` Kyle Meyer
2021-01-06 15:36   ` Stefan Monnier [this message]
2021-02-05  6:24     ` Kyle Meyer
2021-02-05 15:37       ` Stefan Monnier
2021-02-06 11:51       ` Pierre Langlois

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=jwvim8at72z.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=kyle@kyleam.com \
    --cc=pierre.langlois@gmx.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).