Installing TRAMP with package.el fails on startup

Martin Kjær Jørgensen <[email protected]>
Newsgroups gmane.emacs.tramp
Message-ID <[email protected]>
Hey,

I'm using 'GNU Emacs 29.1 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.24.38,
cairo version 1.16.0) of 2023-08-30, modified by Debian' with ...

(setq package-install-upgrade-built-in t)

... set in order to update built-in packages. Updating other build-in pacakges
seems to work, except tramp (2.6.1.3), which installs without errors, but
produces errors on emacs startup, like:

Symbol's function definition is void: tramp-register-crypt-file-name-handler


When running emacs with --debug-init I get this trace:

Debugger entered--Lisp error: (void-function tramp--with-startup)
(tramp--with-startup (add-to-list 'tramp-methods (cons tramp-adb-method (cons (list 'tramp-login-program tramp-adb-program) '((tramp-login-args (... ...)) (tramp-direct-async t) (tramp-tmpdir "/data/local/tmp") (tramp-default-port 5555))))) (add-to-list 'tramp-default-host-alist (cons tramp-adb-method '(nil ""))) (tramp-set-completion-function $
  load-with-code-conversion("/home/mkj/.emacs.d/elpa-debian/tramp-2.6.1.3/tramp..." "/home/mkj/.emacs.d/elpa-debian/tramp-2.6.1.3/tramp..." nil t)
  load("/home/mkj/.emacs.d/elpa-debian/tramp-2.6.1.3/tramp..." nil t)
  package-activate-1(#s(package-desc :name tramp :version (2 6 1 3) :summary "Transparent Remote Access, Multiple Protocol" :reqs ((emacs (26 1))) :kind nil :archive nil :dir "/home/mkj/.emacs.d/elpa-debian/tramp-2.6.1.3" :extras ((:url . "https://www.gnu.org/software/tramp/") (:keywords "comm" "processes") (:maintainer "Michael Albinus" . "micha$
  package-activate(tramp)
  package--activate-all()
  package-activate-all()
  load-with-code-conversion("/home/mkj/.emacs.d/init.el"
  "/home/mkj/.emacs.d/init.el" t t)
  ....
  ....

Perhaps the TRAMP loading conflicts with built-in TRAMP or some order of
loading is needed?

/Martin
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.