Severity: normal On Wed, Jan 19, 2011 at 08:09:02PM -0500, Stefan Monnier wrote: > Package: dictionaries-common > Version: 1.5.17 > Severity: important
Hi, Stefan, nice to read you here, > Installation of dictionaries-common failed as follows: > > Setting up dictionaries-common (1.5.17) ... > install/dictionaries-common: Byte-compiling for emacsen flavour emacs20 emacs20?? > Warning: Lisp directory `/usr/local/share/emacs/20.7/site-lisp' does not > exist. > Wrote /usr/share/emacs20/site-lisp/dictionaries-common/debian-ispell.elc > Wrote /usr/share/emacs20/site-lisp/dictionaries-common/ispell.elc > While compiling toplevel forms in file /usr/share/emacs20/site-lisp > /dictionaries-common/flyspell.el: > !! Symbol's function definition is void ((executable-find)) > Done > emacs-package-install: > /usr/lib/emacsen-common/packages/install/dictionaries- > common emacs20 emacs19 emacs20 emacs21 emacs22 emacs23 xemacs21 failed at emacs19?? > /usr/lib/emacsen-common/emacs-package-install line 30, <TSORT> line 1. > dpkg: error processing dictionaries-common (--configure): > subprocess installed post-installation script returned error exit status 1 > Errors were encountered while processing: > dictionaries-common The reason for this failure was that I missed to explicitly add ancient (last upload was on 2005) emacs20 Debian package to the list of exclusions (emacs19 and emacs-snapshot at that time). IIRC, the reason behind that miss was that at some time emacs20 package was not installable at all along with the rest of Debian and package manager program decided to remove it because of some incompatibility, so I forgot to add the extra harmless exclusion. Seems that incompatibiity finally disappeared or you managed to work around it (or I remember wrong, cannot find relevant info). A wider list of exclusions will be uploaded once squeeze is released, including emacs19 emacs20 emacs21 and emacs22, so only emacs23 and xemacs21 are enabled and the other, if present, use pristine code. In the meantime, I am afraid there is nothing that can be done about this, we are in deep freeze (squeeze is temptatively scheduled for early February) and fixing things to work with an ancient emacs flavour is not the kind of things release managers will consider important enough at this stage of release. > Failure to byte-compile those non-essential Elisp files should clearly not > prevent installation of the package. This part belongs to the emacsen-common package, which contains Debian policy for emacsen and auxiliary tools. I personally think is correct to catch the error and fail, that increases probability of bug reporting and fixing. Thanks for yor feedback, -- Agustin -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
