Bug#922199: courier-imap: Upgrade broken on non-systemd installations

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#922199: courier-imap: Upgrade broken on non-systemd installations

Julian Calaby
Package: courier-imap
Version: 5.0.5+1.0.5-2
Severity: important

Dear Maintainer,

Upgrading to courier-imap 5.0.5+1.0.5-2 on systems that use the traditional
sysvinit is broken.

I have an older server which has been upgraded over the years to Buster and has
managed to avoid being switch to use systemd as it's init system.

Upgrading Courier from 4.17.2+0.76.3-5+b1 to 5.0.5+1.0.5-2 failed with errors
in the postinst script.

For some reason, running invoke-rc.d to restart the services through dpkg
failed where running the exact same commands outside of it worked fine.

I was able to complete the upgrade by disabling both services using update-rc.d
however this isn't a particularly nice upgrade experience.

I understand that non-systemd systems are a historical curiosity these days,
but I'd appreciate it if you'd investigate why your package fails to configure
on them.

Thanks,

Julian Calaby

Reply | Threaded
Open this post in threaded view
|

Bug#922199: courier-imap: Upgrade broken on non-systemd installations

Christophe Garault-3
Hi,

I faced the same bug on a similar install yesterday.

After some investigation I have found that file

/usr/lib/courier/imapd contains a bad command

/usr/bin/mkdir -p `dirname $PIDFILE` ; \

whereas the same file in Stretch contains

/bin/mkdir -p `dirname $PIDFILE` ; \

Of course executing a postinst with /usr/bin/mkdir fails.

One could circumvent this by creating a temporary symlink

but solving this bug by correcting the file is certainly
better.

Thanks.