Hi Antoine, Вт 27 апр 2021 @ 13:53 Antoine Beaupre <anar...@debian.org>:
> Package: elpa-esup > Version: 0.7.1-3 > Severity: grave > Tags: upstream > > This package is unusable in Debian 11 bullseye in its current > state. In my Emacs 1:27.1+1-3.1 session, i run M-x esup and I get: > > error in process sentinel: Wrong type argument: (or eieio-object class), nil, > obj > > *Messages* has this: > > Loading /usr/share/emacs/site-lisp/elpa/esup-0.7.1/esup-autoloads.el > (source)...done > Starting esup... > esup process started on port 37851 > at 1 > error in process sentinel: slot-value: Wrong type argument: (or eieio-object > class), nil, obj > error in process sentinel: Wrong type argument: (or eieio-object class), nil, > obj > > This is the upstream bug: https://github.com/jschaf/esup/issues/85 > > It looks like it is a packaging issue, since, according to the above > bug report, recompiling the .el files fixes the problem (haven't tested). Thanks for reporting, investigating and forwarding! Is it a fresh install of elpa-esup? I have elpa-esup installed for a long time and I cannot reproduce the bug on my machine. Running esup starts another GNU Emacs session and gives me a proper report on startup like the following excerpt: ``` Total User Startup Time: 0.357sec Total Number of GC Pauses: 3 Total GC Time: 0.065sec package.elc:16 0.134sec 37% (byte-code "\301\302!\210\301\303!\210 [...] ``` I wonder how recompiling could fix the problem you face, since installing/reinstalling the package or GNU Emacs itself should trigger recompilation of it along with all other installed Emacs packages. The package does not contain any pre-compiled files: ``` $ apt-file show elpa-esup elpa-esup: /usr/lib/emacsen-common/packages/compat/elpa-esup elpa-esup: /usr/lib/emacsen-common/packages/install/elpa-esup elpa-esup: /usr/lib/emacsen-common/packages/remove/elpa-esup elpa-esup: /usr/share/doc/elpa-esup/README.md elpa-esup: /usr/share/doc/elpa-esup/changelog.Debian.gz elpa-esup: /usr/share/doc/elpa-esup/copyright elpa-esup: /usr/share/emacs/site-lisp/elpa-src/esup-0.7.1/esup-autoloads.el elpa-esup: /usr/share/emacs/site-lisp/elpa-src/esup-0.7.1/esup-child.el elpa-esup: /usr/share/emacs/site-lisp/elpa-src/esup-0.7.1/esup-pkg.el elpa-esup: /usr/share/emacs/site-lisp/elpa-src/esup-0.7.1/esup.el ``` So, may it be a bug in dh-elpa or GNU Emacs itself? Cheers! Lev