ubuntu-elisp team mailing list archive

[Reinhard Tartler <siretart@xxxxxxxxxx>]

Matt Zimmerman <mdz@xxxxxxxxxx> writes:

> On Wed, Nov 18, 2009 at 04:37:50PM +0100, Reinhard Tartler wrote:
>> Matt Zimmerman <mdz@xxxxxxxxxx> writes:
>> 
>> > I suggest looking at the existing scripts in /usr/share/apport which create
>> > problem reports in response to various error events.
>> 
>> Ok, it seems that currently the best way would be to change
>> /usr/share/apport/general-hooks/ubuntu.py, since apport (currently) does
>> not seem to provide better integration for postinst failiures. That file
>> contains special handling for grub, grub2, initramfs, and kernel
>> packages, so I guess adding emacsen to that list is the way to go.
>
> The logic for maintainer script failures in ubuntu.py tries to guess the
> right package where apt gets it wrong, e.g. when the kernel postinst fails
> because of grub2.  If that's analogous to the issue with emacsen (e.g. an
> elisp package causing some other package's postinst to fail), then you could
> do the same thing.  It's a bit of a hack, though, as it parses through the
> log to try to figure out what happened.

Yes, this is about exactly the situation. emacsen need to byte-compile
all installed add-on packages. This recompilation happens from emacsen's
postinst script, but the fix needs to happen in the add-on package.

> If there is some common hook already for emacs packages, you could probably
> do better. 

No, there is no such hook (yet). I don't see how an hook could help with
this particular case.

> Does that make sense?

It does, thanks!

-- 
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4