Hi Friedrich, Friedrich Beckmann <friedrich.beckmann@gmx.de> writes: > Hi Nicholas, > > thanks for looking into the problem! > You're welcome :-) Sorry I won't be able to look into it in-depth for the near-future, but here are some hints: >> Am 20.06.2020 um 22:22 schrieb Nicholas D Steeves <nsteeves@gmail.com>: >> Friedrich Beckmann <friedrich.beckmann@gmx.de> writes: >> >> Installed with dpkg/apt? > > Installed with apt. > [snip] >>> In the current emacs version in testing 1:26.3+1-2 >>> I cannot install the package. When I run >>> >>> M-x package-list-packages >>> >>> I see: >>> ... >>> zones 2019.7.13 available Zones of text - like multiple regions >>> ztree 1.0.5 available Text mode directory tree >>> poker 0.2 installed Texas hold 'em poker >>> psgml 1.3.4 installed SGML-editing mode with parsing support >>> dh-elpa 2.0.4 external package.el style packages for Debian >>> pspp-mode 1.0 external Major mode for editing PSPP files >> >> * if you click on pspp-mode I think you'll find >> Status: External in ‘/usr/share/emacs/site-lisp/elpa-src/pspp-mode-1.0/pspp-mode.el’ > > I see: > Status: External in ‘/usr/share/emacs/site-lisp/elpa/pspp-mode-1.0/’ (unsigned). > >> * "Status: External" means it has been installed. >> * What does M-x locate-library psp-mode return? > > M-x locate-library pspp-mode returns: > > Library is file /usr/share/emacs/site-lisp/pspp/pspp-mode.el > This combination of facts makes me wonder if something is wrong with pspp's ELPA/packages.el metadata. >>> There are only the dh-elpa and the pspp-mode package listed as „external“. When >>> I type „i“ to install pspp-mode, then this does not work. >> >> Haven't you already installed it with 'apt install pspp‘? > > Yes, I have and I expected that I can activate the pspp-mode simply > with "M-x pspp-mode“, but that is not possible. I have to do > > M-x load-library pspp-mode.el (loading from /usr/share/emacs/site-lisp/pspp/pspp-mode.el) > > and then I can do > > M-x pspp-mode > > to switch the mode. As far as I remember the only requirement for that > would be to have just the pspp-mode.el file in that path, no? > See above. IIRC, clicking on pspp-mode should return the path to the library's file and not the library's load-path. >>> This works for the „available“ packages. So listing works, the info is >>> shown but I cannot use the package. It seems that nobody else uses >>> dh-elpa right? >> >> Plenty of people use dh-elpa :-) At this point it's unclear what you're >> reporting. Maybe it's one of these?: >> >> 1. pspp regression after converting to dh-elpa >> * normal bug, against in pspp package > > Maybe I use dh-elpa in wrong way in the pspp debian package setup. > I remember that it worked some time ago but today it does not. > The first thing to try is a rebuild of the package using an up-to-date sid (meaning up-to-date dh-elpa). On the Emacsen Team we occasionally rebuild all packages built with ancient dh-elpa versions, but given the two recent uploads I don't think this is the problem. It's also recommended to use a bin:elpa-pspp or bin:elpa-pspp-mode package. Legacy all-in-one non-Emacs packages containing an Emacs mode are less well tested, and it's possible you found found a bug in this. >> 2. request to install Debian packages from the 'package-list-packages' >> interface. >> * wishlist bug in src:emacs (in a desktop-general sense) to add >> Debian package management to packages.el > > No, I expect that I can activate the pspp-mode right after installation > of the pspp package via apt. > Agreed, that's how it should work. [snip] > As far as I remember the dh-elpa procedure worked some time ago but now > it is at least unexpected behaviour. I expect that I can use the > pspp-mode after the installation of the pspp package directly. But > this does not happen. Maybe I use the dh-elpa package in a wrong way > during the preparation of the pspp debian package. [snip] > The pspp debian package is here: > > https://salsa.debian.org/science-team/pspp/-/tree/master/debian Well, no commits mention dh-elpa, and the changelog entry doesn't mention it either...which makes me suspect there may be other problems. > Maybe I use emacs in a wrong way. Maybe emacs is broken with external > packages. Really? This is a bit hyperbolic ;-) > Thanks for your detailed questions! I hope I could clarify the > things. It would really help if somebody with more experience with > emacs and dh-elpa could have a look at this. Sorry I can't be of more help at this time; I'm at a point where I have to avoid taking on additional responsibilities. Other hints are enabling DH_VERBOSE and checking the build log for anything elpa-related, and also seeing if the dh-elpa managed byte-compilation detects the correct ELPA/packages.el name and version during package installation. And of course man DH_ELPA(1) I'm leaving this bug tagged as moreinfo until we know if it's a dh-elpa bug supporting the legacy packaging style, but I suspect there's a warning in the build log or package installation output, DH_ELPA(1) can be used to interpret this, and I wonder if it's missing a correct elpa-package-pkg.el and/or if the package name is bad (see that man page for more info). Cheers, Nicholas
Attachment:
signature.asc
Description: PGP signature