On 2011-02-22 21:39 +0100, Jonathan Nieder wrote:
> retitle 614578 git: postinst fails if emacsen-common is unpacked but not
> configured
> severity 614578 serious
> quit
>
> Hi,
>
> Christoph Egger wrote:
>
>> Setting up git (1:1.7.4.1-1) ...
>> ERROR: emacsen-common being used before being configured.
>> ERROR: This is likely a bug in the git package, which needs to
>> ERROR: add one of the appropriate dependencies.
>> ERROR: See /usr/share/doc/emacsen-common/debian-emacs-policy.gz
>> ERROR: for details.
>
> Yikes.
>
> git does not depend on emacsen, but its postinst contains
>
> if test -x /usr/lib/emacsen-common/emacs-package-install; then
> /usr/lib/emacsen-common/emacs-package-install git
> fi
>
> the theory being, if you have emacs installed, you'd presumably want
> to have these modules byte-compiled.
>
> It sounds like that "text -x" condition is too weak. Does the emacsen
> policy provide a way to check whether emacsen-common is configured
> (i.e., ready to be used)?
AFAIK, no; you have to depend on emacsen-common.
> Otherwise, I suppose the .el files will
> have to move to a separate git-emacs package (which would depend on
> emacsen-common).
If you want to make a separate package, it should be named git-el and
depend on emacs | emacsen. Alternatively, you could make git depend on
emacsen-common.
Cheers,
Sven
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
