Rob Browning <r...@defaultvalue.org> writes:

> Sébastien Villemot <sebast...@debian.org> writes:
>
>> devscripts-el/wheezy's postinst crashes. The problem is that apel/wheezy
>> is configured before emacsen-common/wheezy, and this apparently breaks.
>> If the order is changed and emacsen-common/wheezy is configured before
>> apel/wheezy and devscripts-el/wheezy, then everything goes fine.
>
> I don't know offhand (and may well be wrong), but I'm guessing that this
> may a bug in apel.  Though it could also be a bug in emacsen-common
> 2.*'s new approach to dependencies.

Here is the sequence of events:

- apel/wheezy is configured: it does not byte-compile, apparently
  because emacsen-common/wheezy is not yet configured

- emacsen-common/wheezy is configured: it does *not* byte-compile apel

- devscripts-el/wheezy is configured: it crashes, because it cannot find
  mcharset.elc (which belongs to apel)

I see only two possible solutions:

- either force apel to be configured *after* emacsen-common: only a
  direct dependency apel->emacsen-common can achieve that, and this
  seems against the spirit of the recent changes to emacsen-common; so
  this solution seems excluded

- or have emacsen-common's postinst byte-compile all add-ons that are
  already configured but not yet byte-compiled; I don't know if the fact
  that this does not actually happen here is a bug in emacsen-common or
  in apel. What is your stance on this?

-- 
 .''`.    Sébastien Villemot
: :' :    Debian Developer
`. `'     http://www.dynare.org/sebastien
  `-      GPG Key: 4096R/381A7594

Attachment: pgp5EPagRBRYl.pgp
Description: PGP signature

Reply via email to