Bug#387699: exim4: Should create /var/run/exim4/ if it is missing

[Andreas Metzler]

On 2006-09-16 Petter Reinholdtsen <pere at hungry.com> wrote:
> [Andreas Metzler]
> > I was talking about *partial* upgrades, i.e. upgrading sysvinit
> > without upgrading e.g. exim4.

> Right.  I see.  I guess we need to add conflicts on the packages
> expecting persistense in /var/run/.  Conflict: exim4-base (<= 4.62-4)
> might do it, if a updated exim4 version is uploaded now.

I have made the necessary changes in SVN, they should be in 4.63-4,
Conflicts: exim4-base (<= 4.63-3)
would do the trick for exim4.

Just to make you reconsider, this is the other stuff that would break
just on my two sarge systems:

hotplug: /var/run/usb (unknown purpose)
mpd: /var/run/mpd for pid file.
pppconfig: /var/run/pppconfig is used by /etc/ppp/ip-up.d/0dns-up
alsa-base: uses /var/run/alsa/modules-removed to keep a tab of loaded
modules.
cupsys: pidfile and printcap
pident: writes pidfile to /var/run/identd/ but is started via inetd!
greylistd: used for socket and pid file.
clamav-daemon: pidfile and socket

cu andreas
-- 
The 'Galactic Cleaning' policy undertaken by Emperor Zhark is a personal
vision of the emperor's, and its inclusion in this work does not constitute
tacit approval by the author or the publisher for any such projects,
howsoever undertaken.                                (c) Jasper Ffforde