On 2008-04-12 13:56 +0200, Stefano Zacchiroli wrote:

> Package: emacs22
> Version: 22.2+1-1
> Severity: important
>
> After today aptitude run:
>
>   A package failed to install.  Trying to recover:
>   Setting up emacs22 (22.2+1-1) ...
>   emacs-install emacs22
>   install/a2ps: Handling install for emacsen flavor emacs22
>   Warning: Lisp directory `/etc/emacs22' does not exist.
>   Wrote /usr/share/emacs22/site-lisp/a2ps/a2ps.elc
>   Wrote /usr/share/emacs22/site-lisp/a2ps/a2ps-print.elc
>   install/dictionaries-common: Already byte-compiled for emacs22. Skipping ...
>   emacsen-common: Handling install of emacsen flavor emacs22
>   emacsen-common: byte-compiling for emacs22
>   cp: cannot create regular file `/etc/emacs22/site-start.d': No such file or 
> directory

Strange, /etc/emacs22/site-start.d is supposed to be a directory and is
shipped in emacs22-common (on which emacs22 indirectly depends).

>   emacs-install: /usr/lib/emacsen-common/packages/install/emacsen-common 
> emacs22 failed at /usr/lib/emacsen-common/emacs-install line 28, <TSORT> line 
> 6.
>   dpkg: error processing emacs22 (--configure):
>    subprocess post-installation script returned error exit status 1
>   Errors were encountered while processing:
>    emacs22
>
> Of course the first (non reported) configure attempt fails in the same
> way. While I do not have a /etc/emacs22 directory I do have a /etc/emacs
> one, dunno if there lies the problem, but for sure I haven't deleted the
> dir myself.

As I said above, /etc/emacs22 is shipped in emacs22-common, and this ...

> Versions of packages emacs22 depends on:
> ii  emacs22-bin-common     22.2+1-1          The GNU Emacs editor's shared, 
> arc

... indicates that emacs22-common must be correctly installed, since
emacs22-bin-common depends on it.  So how can the directory be missing?

Can you please send the aptitude and dpkg logs of the failed install?
And what does `dpkg -S /etc/emacs22' print?

Regards,
        Sven



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to