Bug#1115607: elpa-vterm: "M-x vterm" insists on compiling `vterm-module` after initial installation
Package: elpa-vterm
Version: 0.0.2+git20250113.056ad74-1
Severity: important
Dear Maintainer,
* What led up to the situation?
Just installed elpa-vterm, launched Emacs, and issued M-x vterm.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Issued M-x vterm.
* What was the outcome of this action?
The following message appeared in Emacs:
Vterm needs `vterm-module' to work. Compile it now? (y or n)
This is weird, because vterm-module.so is already installed on the system due to
elpa-vterm depending on emacs-libvterm:
$ find /usr/lib -name vterm-module.so
/usr/lib/aarch64-linux-gnu/emacs-libvterm/vterm-module.so
* What outcome did you expect instead?
To get a vterm session buffer out of the box.
-- System Information:
Debian Release: 13.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'stable')
Architecture: arm64 (aarch64)
Kernel: Linux 6.12.43+deb13-arm64 (SMP w/10 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages elpa-vterm depends on:
ii dh-elpa-helper 2.1.9
ii emacs-libvterm 0.0.2+git20250113.056ad74-1
ii emacsen-common 3.0.8
elpa-vterm recommends no packages.
elpa-vterm suggests no packages.
-- no debconf information
Reply to: