[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1115607: marked as done (elpa-vterm: "M-x vterm" insists on compiling `vterm-module` after initial installation)

Your message dated Fri, 19 Sep 2025 22:48:58 +0000
with message-id <E1uzjuU-000Vgy-1g@fasolo.debian.org>
and subject line Bug#1115607: fixed in emacs-libvterm 0.0.2+git20250113.056ad74-2
has caused the Debian Bug report #1115607,
regarding elpa-vterm: "M-x vterm" insists on compiling `vterm-module` after initial installation
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1115607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1115607
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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

--- End Message ---
--- Begin Message --- 
Source: emacs-libvterm
Source-Version: 0.0.2+git20250113.056ad74-2
Done: Xiyue Deng <manphiz@gmail.com>

We believe that the bug you reported is fixed in the latest version of
emacs-libvterm, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1115607@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Xiyue Deng <manphiz@gmail.com> (supplier of updated emacs-libvterm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 19 Sep 2025 15:32:17 -0700
Source: emacs-libvterm
Architecture: source
Version: 0.0.2+git20250113.056ad74-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team <debian-emacsen@lists.debian.org>
Changed-By: Xiyue Deng <manphiz@gmail.com>
Closes: 1115607
Changes:
 emacs-libvterm (0.0.2+git20250113.056ad74-2) unstable; urgency=medium
 .
   * Upload to unstable
     - Change elpa-vterm to arch:any fixed the DEB_HOST_MULTIARCH
       generation. (Closes: #1115607)
 .
 emacs-libvterm (0.0.2+git20250113.056ad74-2~exp1) experimental; urgency=medium
 .
   * Make elpa-vterm arch:any
     - elpa-vterm sets the shard library path according to the host arch.
       Previously when set as arch:all, the `load-path' is set once during
       building arch:all package and won't change based on the host arch,
       resulting in wrong `load-path' in non-amd64 archs.
   * Add `Multi-Arch: same' hint to arch:any packages
Checksums-Sha1:
 c0c62880522472b011cb90cd14e31cf9bbb776bc 2534 emacs-libvterm_0.0.2+git20250113.056ad74-2.dsc
 f54bee1addbe8b4c0b631aaa53d9c25e367a1873 4044 emacs-libvterm_0.0.2+git20250113.056ad74-2.debian.tar.xz
 0ef9926c97a2a0ff523cca923fd7909670b23e96 112784 emacs-libvterm_0.0.2+git20250113.056ad74-2.git.tar.xz
 d87d9ce7d5c00ef767a527a01c40248b57534362 18326 emacs-libvterm_0.0.2+git20250113.056ad74-2_source.buildinfo
Checksums-Sha256:
 ac5c8ec5d2e3ef89b6c9c6d4476f2f45a7cbb8660557cd22c20c40daab700274 2534 emacs-libvterm_0.0.2+git20250113.056ad74-2.dsc
 b25737d1898c32f87c13d7e80ab0c8525b6261a334672c67b6db6d151ba16d59 4044 emacs-libvterm_0.0.2+git20250113.056ad74-2.debian.tar.xz
 26a0f4a8728ed04176654ee0022ecd01750238f53b865dc903edac573702b935 112784 emacs-libvterm_0.0.2+git20250113.056ad74-2.git.tar.xz
 ef9ec34f5c636d38c4e6ac74fa19109be260eed4b246fb5b1a5705356bee7b89 18326 emacs-libvterm_0.0.2+git20250113.056ad74-2_source.buildinfo
Files:
 135f6798914f75817c0401a199774e79 2534 editors optional emacs-libvterm_0.0.2+git20250113.056ad74-2.dsc
 48afedf75512b3b78a9db25dabd4d01c 4044 editors optional emacs-libvterm_0.0.2+git20250113.056ad74-2.debian.tar.xz
 b20b0b67019d7e048e5b89fdeff4f26c 112784 editors optional emacs-libvterm_0.0.2+git20250113.056ad74-2.git.tar.xz
 6e83fb371a946c723b5c9da51bb13f11 18326 editors optional emacs-libvterm_0.0.2+git20250113.056ad74-2_source.buildinfo
Git-Tag-Info: tag=fdaed5ff954da83786bd1e291eb97c0c7008543e fp=88a41f77aa3cd668c8f8b5802de965ed63825c93
Git-Tag-Tagger: Xiyue Deng <manphiz@gmail.com>

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEN02M5NuW6cvUwJcqYG0ITkaDwHkFAmjN2lUACgkQYG0ITkaD
wHk1Pg//cKTu/Rci5o/fz7M7HKNRqaWCcBsKiyNeFfPUtm7X9imNVJ3xVjtzZ3la
dotFxVRdo9An3jkXLBPkE49BhIkJux1bb5Dx+WwsdMl4HTRCP52QSHwkiWf0suli
eg7h1/z6ENKPTD/f6UvvBcmAHnUPpEUAmlB0d+BDKW0MnfoUKYnPB3XAnOr4vRS8
/OwCNfxaPvI8CcYyEmj6UaJeNio6uIsNrteDx3yzvPyMNgEfWh5LcOrpX9J2ThYj
P8e0eMtQCeQGOxEKGVJijdVuWAqNwv5iVuZO8G2lHUgsB3zY6BfOS4W/Ltt+p1Cc
rnEleyr+a4PVbCNvj2EH1+/ZjZrFW1szhoX6slrSEU7KPMW+T8ibIf8WgUW+VDUB
8l9wX7DVWptttP3466UmVZT8CknJd/bWEX5X7ZlfupuSEfdE3eUBOzvfNczVB4gq
Fp7tLP8LaoORJlKye5T/HG6pqNU03GmjBkuo2MbnMlN5rMqmY4Zhoto2ghWmUEJZ
JjSkJu9wNP2zmhTuyH1xP8hf0fd2D0kTQGMXNUHM+9r7kC41sGawb3dPMBZl1yHx
nc7QoXScO0rArMdR8otPml1GD9PLweOZkY0wYxTTSMqy91rPKbcoDpmIrW0NbmX/
ckMp+AqatxTIedpHvSPPNS76JVWXWil6T9njpv1WOh/sJ+0onS8=
=Zj0A
-----END PGP SIGNATURE-----

Attachment: pgp1SDV5S9ouM.pgp
Description: PGP signature


--- End Message ---
Reply to: