Bug#941046: bbdb: byte-compilation and startup broken with unversioned emacs
Package: bbdb
Version: 2.36-4.1
Severity: serious
Justification: package does not load
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
debian/bbdb.emacsen-install was never updated for unversioned
emacs. This means the package fails to byte compile, which in turn
causes the startup file to bail out.
I'm not 100% sure about the severity. This bug does mean that unless
people write their own startup code (manipulating load-paths and so
on), bbdb is completely useless.
- -- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.2.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages bbdb depends on:
ii emacs-gtk [emacsen] 1:26.1+1-4
ii make 4.2.1-1.2
ii perl 5.28.1-6
bbdb recommends no packages.
Versions of packages bbdb suggests:
pn gnus | t-gnus <none>
pn gnuserv <none>
ii perl 5.28.1-6
pn vm <none>
pn w3m-el <none>
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAl2JVkAACgkQA0U5G1Wq
FSHHEA/9GKyJ3tO/0HJyU+Tj+y1oYwoLOlbggdeCNgO5IcXUBAC3BH3wx8Y6ebQm
/XuKUAC+xReUc3FL7PjYPTm6evUQP6fCNF8IUqcQBEzzWM4WBeAFcefyyZOHN5on
kSS7oqMTou+GHGdP+xl9gmzP0VJCDerR7dQbOdK9cQNd5aCtcqewFrq42qjpgXnX
Rnnz1CQ8UFYtDVuYBxt2N0YU0I9828ssp8oDkduvjDMANZNCpyVn1qukJ/MnYYij
6jt4Tg86dLw+KljCI7I3mF4GAofRgyK9m8PfYS2cJSjMfZ3PDCHWJnLwWlz8UKcW
t23UjIKf0PWLQA1SjVee+fH+zoFo1tPmRD+gFKxjZE/+eo6CJJgnsviqlj3LUAtX
uGRpbGu26vJbaEg2FBLywN21Q3pDs95K73n8Ajq7dObrSNLF2ug6xnI+7qk+NWo9
YOg2Z27fZebrBBmVJ2DI+ebpOm3mV+Z2V0DiuXzXYTrKn0Ji5tAqs+ffvp6eNww/
L6kIf6CR0rTL6tom31TFJo3L8EITcFsZE4TeiyFXmjUwdkPuSksb3SeVS+DlEsBO
pa3X5/kgx1EVYSq0wCne8UE36+dHeXRT32Gl8T1X80Hc3Z0a6oFBZAd9Cy1tRtBu
IyFb0l6XI8zDEMc4PN32eUnpY2eJxKupjwty4TF1VMgeykz6Auk=
=/02+
-----END PGP SIGNATURE-----
Reply to: