[Pkg-mailman-hackers] Pkg-mailman commit - rev 741 - trunk/debian

Thijs Kinkhorst thijs at debian.org
Tue Aug 20 07:08:05 UTC 2013


On Thu, August 15, 2013 17:29, Thorsten Glaser wrote:
> On Thu, 15 Aug 2013, Thijs Kinkhorst wrote:
>
>> Installation/uninstallation would not be broken, because the user would
>> have been asked for the necessary info via debconf and the site list
>> would
>> have been created, so the init script doesn't fail.
>
> Hm right. But the init script apparently…
>
>> Can you point me to the relevant Policy remarks? I just read 9.3 and
>> didn't find something that indicates that init scripts should not fail
>> when the service they're trying to start didn't start.
>
> … still should not be failing. https://wiki.debian.org/LSBInitScripts
> the last paragraph and the referenced bug’s messages hint at that,
> although there is no policy (lowercase) on it yet, really. But that’s
> what I was being told in IRC.

I've read that. That mainly talks about what a proper exit code should be
when a package is removed-not-purged.

I propose to change only this specific case:
- Mailman is correctly installed, but there is no site list, so the daemon
cannot be started.
This case reads like a "configuration error" to me because, if we
implement site list creation on package install, there's no functional
mailman installation where this case applies.

You will notice that the apache init script fails when the apache
configuration has errors. I think this is the same situation.


Thijs





More information about the Pkg-mailman-hackers mailing list