Your message dated Wed, 13 May 2026 20:22:26 -0700
with message-id <3999598.FjKLVJYuhi@soren-desktop>
and subject line please consider not stopping daemon on upgrade
has caused the Debian Bug report #568463,
regarding please consider not stopping daemon on upgrade
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
568463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568463
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: courier-pop
Version: 0.63.0-2.1
Severity: wishlist
Currently, the pop daemon (and other courier daemons I suppose) are
stopped for upgrade, and only restarted after an arbitrary delay.
I imagine some courier installations have a many users, and having the
daemon down for a few minutes for an upgrade could be a major hassle for
them.
I don't; I have only a few pop users. But having the daemon taken down
during an upgrade still affected me, apparently because I was unlucky
and a user tried to POP at just the wrong time, and got an unexpected
password prompt shown by evolution. (Strange failure mode.. perhaps
evolution was at the PASS step of logging in when the pop server was
killed, and so thought it rejected the stored password?)
So, have you considered deferring the daemon stop until after upgrade?
Ie, via dh_installinit --no-restart-on-upgrade
For this to be safe, the old daemon needs to be able to continue running
while courier-pop and its dependencies are upgraded. I have not checked
if that is the case.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (x86_64)
Kernel: Linux 2.6.32-trunk-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages courier-pop depends on:
ii courier-base 0.63.0-2.1 Courier mail server - base system
ii libc6 2.10.2-5 Embedded GNU C Library: Shared lib
ii postfix [mail-transport-agent 2.6.5-3 High-performance mail transport ag
courier-pop recommends no packages.
Versions of packages courier-pop suggests:
ii bsd-mailx [mail-re 8.1.2-0.20090911cvs-2 simple mail user agent
ii courier-doc 0.63.0-2.1 Courier mail server - additional d
pn courier-pop-ssl <none> (no description available)
ii emacs21 [mail-read 21.4a+1-5.7 The GNU Emacs editor
ii mutt [mail-reader] 1.5.20-6 text-based mailreader supporting M
ii pine [mail-reader] 4.64-4 An e-mail reader with MIME and IMA
-- no debconf information
--
see shy jo
--- End Message ---
--- Begin Message ---
I have recently become the maintainer of the courier packages. I apologize
that nobody responded to this bug report in a timely manner.
I can imaging a lot of potential error message/data loss problems with
continuing to run the old daemon while upgrading the package. As such, I
think the current behavior is desirable. It is also inline with the way other
packages in Debian handle upgrades. Hence, I am closing this bug. However,
if you think there is some safe way to handle this, feel free to reopen the
bug with an explanation.
--
Soren Stoutner
[email protected]
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
