From: Michael Albinus <michael.albinus@gmx.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 48015@debbugs.gnu.org
Subject: bug#48015: 28.0.50; ELPA package compilation fails
Date: Tue, 27 Apr 2021 14:05:18 +0200 [thread overview]
Message-ID: <87v988c4qp.fsf@gmx.de> (raw)
In-Reply-To: <jwvlf94puu3.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 26 Apr 2021 18:16:18 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> The core problem that I see is the following:
>
> - Emacs's tramp gets loaded
> - We go to a Tramp-controlled default-directory
> - We call `package--load-files-for-activation`
> - This starts by loading ~/.emacs.d/elpa/tramp-NN.MM/tramp-autoloads.el
> This calls `tramp-register-autoload-file-name-handlers`.
> - At this point, `package--load-files-for-activation` would like to
> continue by (re)loading the new Tramp files, such as `tramp-compat`
> and friends in the same order that they have been loaded
> (i.e. `tramp-compat.el` before `tramp.el`).
> - But before it gets a chance to do that, the file-name handlers
> call `tramp-autoload-file-name-handler` because of `default-directory`,
> which does (load "tramp" 'noerror 'nomessage), which loads the new
> `tramp.el` before we got a change to load the new `tramp-compat.el`,
> which then leads to an error when the new code in `tramp.el` calls
> a new function from `tramp-compat.el` (which happens to be
> `tramp-compat-thread-yield` AFAICT).
>
> At this point, I'm not sure how best to fix the problem.
> Maybe replacing (load "tramp" 'noerror 'nomessage) with
> (require 'tramp nil t) is all it takes.
> Or maybe a better option is to arrange the autoloads such that
> `tramp-register-autoload-file-name-handlers` doesn't "unload/unregister" file
> handlers that have already been loaded so that the directory that was
> already under Tramp's control doesn't re-trigger a call to
> `tramp-autoload-file-name-handler`?
What I don't understand: when (load "tramp" 'noerror 'nomessage) is
called, default-directory is already local due to a let-binding.
Anyway, even if the compilation runs through in case of a local
default-directory, the resulting *.elc files have errors. I have quit
Emacs (from the first recipe), and then I have started
emacs -Q -L ~/.emacs.d/elpa/tramp-2.5.0.3/ /ssh::
There are further errors, which are related to a wrong
tramp-compat.el. Only my new command tramp-recompile-elpa fixes this.
> Stefan
Best regards, Michael.
next prev parent reply other threads:[~2021-04-27 12:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-25 10:38 bug#48015: 28.0.50; ELPA package compilation fails Michael Albinus
2021-04-25 16:24 ` Stefan Monnier
2021-04-25 17:25 ` Michael Albinus
2021-04-26 22:16 ` Stefan Monnier
2021-04-27 12:05 ` Michael Albinus [this message]
2021-04-27 13:47 ` Stefan Monnier
2021-04-27 18:58 ` Stefan Monnier
2021-04-27 19:13 ` Michael Albinus
2021-04-28 14:22 ` Michael Albinus
2021-04-28 15:32 ` Stefan Monnier
2021-04-28 17:48 ` Michael Albinus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v988c4qp.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=48015@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.