Your message dated Wed, 25 Oct 2006 11:02:10 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#393596: fixed in cyrus-imapd-2.2 2.2.13-9 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---Package: cyrus-common-2.2 Version: 2.2.13-7 Severity: minor Severity note: I don't think this problem is doing any harm, except perhaps some wasted effort. If my analysis is wrong/incomplete, a higher severity might be appropriate. Scope: Fixing this may involve changes to other versions (e.g., 2.1). PROBLEM I had Cyrus 2.1 installed, and upgraded to 2.2. However, some of the scripts from 2.1 appear to remain active. In particular, both the 2.1 and 2.2 init scripts do DAEMON=/usr/sbin/cyrmaster test -x ${DAEMON} || exit 0 Since /usr/sbin/cyrmaster is in both the 2.1 and 2.2 packages (as well as kolab-cyrus-common) this test does not suffice to disable the script when the corresponding package is removed. HMH suggested one possible solution would be to install some flag file and test on it. That file would need to be a regular file, not a conf file, so that it would be removed when the package is removed. Because the init scripts are conf files, policy requires they be left when the package is removed (AFAIK). There is also a daily cron job associated with the package. It may need a similar flag file check. SIGNIFICANCE The central operation of the init script is usually to start-stop-daemon; since the pid file will exist after the first init script runs, the 2nd run may (I'm not sure) be a no-op. However, there is other code in the init files (especially about checking for upgrades) that looks as if it will still run. I suspect that the duplicate cron scripts will simply do 2 backups in a row. Even if there is no problem now, it seems possible that future 2.2 or 2.3 scripts might change enough so that there would be a problem. I think the cyrus2.2 scripts will run before the cyrus21 scripts in init because of alphabetical sorting. So at the moment, 2.2 runs first, which is probably good. AUDIENCES There are at least 2 groups that might be affected by this issue: those who have already upgraded, and those who do so in the future. Each group may require a separate solution. To the extent automatic solutions are not possible, new upgraders could be clued in by the appropriate upgrading README (and maybe messages at upgrade time, though I suspect that would be debconf abuse). Those who have already upgraded may be best addressed through a NEWS items (I believe those doing a new install will not see such items, so they won't help or confuse the first group). Solutions which involve altering previous packages will not help those who have already removed those packages (i.e., people who already upgraded). WORK-AROUND dpkg --purge cyrus21-common seems to have worked for me. I suspect it is not OK to do this automatically on installation of 2.2; a suggestion to do this manually could go in the upgrade notes. The purge did not remove /etc/cyrus.conf or imapd.conf, which are now owned by cyrus-common-2.2 (I was worried that they'd be swept away too). However, the purge has a very big risk: it asks if you want to delete the spools. The default is no, but if someone puts the wrong answer (yes) here in confusion the result would be disastrous. That's one reason alternate solutions/recommendations might be better. OTHER VERSIONS I've been focussed on 2.1 -> 2.2; older or later versions may raise other issues. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (50, 'unstable'), (40, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-k7-smp Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages cyrus-common-2.2 depends on: ii adduser 3.97 Add and remove users and groups ii debconf [debcon 1.5.5 Debian configuration management sy ii dpkg 1.13.22 package maintenance system for Deb ii exim4-daemon-he 4.63-3 exim MTA (v4) daemon with extended ii gawk 1:3.1.5.dfsg-4 GNU awk, a pattern scanning and pr ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries ii libdb4.2 4.2.52+dfsg-1 Berkeley v4.2 Database Libraries [ ii libsasl2 2.1.19.dfsg1-0.5 Authentication abstraction library ii libsnmp9 5.2.3-1 NET SNMP (Simple Network Managemen ii libssl0.9.8 0.9.8c-3 SSL shared libraries ii libwrap0 7.6.dbs-11 Wietse Venema's TCP wrappers libra ii libzephyr3 2.1.20010518.SNAPSHOT-15 The original "Instant Message" sys ii netbase 4.25 Basic TCP/IP networking system ii perl 5.8.8-6.1 Larry Wall's Practical Extraction Versions of packages cyrus-common-2.2 recommends: ii cyrus-admin-2.2 2.2.13-7 Cyrus mail system (administration ii cyrus-imapd-2.2 2.2.13-7 Cyrus mail system (IMAP support) -- debconf information: cyrus-common-2.2/warnbackendchange: cyrus-common-2.2/removespools: false
--- End Message ---
--- Begin Message ---Source: cyrus-imapd-2.2 Source-Version: 2.2.13-9 We believe that the bug you reported is fixed in the latest version of cyrus-imapd-2.2, which is due to be installed in the Debian FTP archive: cyrus-admin-2.2_2.2.13-9_all.deb to pool/main/c/cyrus-imapd-2.2/cyrus-admin-2.2_2.2.13-9_all.deb cyrus-clients-2.2_2.2.13-9_amd64.deb to pool/main/c/cyrus-imapd-2.2/cyrus-clients-2.2_2.2.13-9_amd64.deb cyrus-common-2.2_2.2.13-9_amd64.deb to pool/main/c/cyrus-imapd-2.2/cyrus-common-2.2_2.2.13-9_amd64.deb cyrus-dev-2.2_2.2.13-9_amd64.deb to pool/main/c/cyrus-imapd-2.2/cyrus-dev-2.2_2.2.13-9_amd64.deb cyrus-doc-2.2_2.2.13-9_all.deb to pool/main/c/cyrus-imapd-2.2/cyrus-doc-2.2_2.2.13-9_all.deb cyrus-imapd-2.2_2.2.13-9.diff.gz to pool/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13-9.diff.gz cyrus-imapd-2.2_2.2.13-9.dsc to pool/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13-9.dsc cyrus-imapd-2.2_2.2.13-9_amd64.deb to pool/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13-9_amd64.deb cyrus-murder-2.2_2.2.13-9_amd64.deb to pool/main/c/cyrus-imapd-2.2/cyrus-murder-2.2_2.2.13-9_amd64.deb cyrus-nntpd-2.2_2.2.13-9_amd64.deb to pool/main/c/cyrus-imapd-2.2/cyrus-nntpd-2.2_2.2.13-9_amd64.deb cyrus-pop3d-2.2_2.2.13-9_amd64.deb to pool/main/c/cyrus-imapd-2.2/cyrus-pop3d-2.2_2.2.13-9_amd64.deb libcyrus-imap-perl22_2.2.13-9_amd64.deb to pool/main/c/cyrus-imapd-2.2/libcyrus-imap-perl22_2.2.13-9_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Benjamin Seidenberg <[EMAIL PROTECTED]> (supplier of updated cyrus-imapd-2.2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Wed, 25 Oct 2006 13:39:08 -0400 Source: cyrus-imapd-2.2 Binary: cyrus-dev-2.2 libcyrus-imap-perl22 cyrus-common-2.2 cyrus-doc-2.2 cyrus-clients-2.2 cyrus-pop3d-2.2 cyrus-imapd-2.2 cyrus-admin-2.2 cyrus-nntpd-2.2 cyrus-murder-2.2 Architecture: source amd64 all Version: 2.2.13-9 Distribution: unstable Urgency: high Maintainer: [EMAIL PROTECTED] Changed-By: Benjamin Seidenberg <[EMAIL PROTECTED]> Description: cyrus-admin-2.2 - Cyrus mail system (administration tools) cyrus-clients-2.2 - Cyrus mail system (test clients) cyrus-common-2.2 - Cyrus mail system (common files) cyrus-dev-2.2 - Cyrus mail system (developer files) cyrus-doc-2.2 - Cyrus mail system (documentation files) cyrus-imapd-2.2 - Cyrus mail system (IMAP support) cyrus-murder-2.2 - Cyrus mail system (proxies and aggregator) cyrus-nntpd-2.2 - Cyrus mail system (NNTP support) cyrus-pop3d-2.2 - Cyrus mail system (POP3 support) libcyrus-imap-perl22 - Interface to Cyrus imap client imclient library Closes: 393596 Changes: cyrus-imapd-2.2 (2.2.13-9) unstable; urgency=high . * The "Benjamin made it in time for etch" release. * High urgency upload with simple fixes for Etch . [ Henrique de Moraes Holschuh ] * Prevent cronjobs and initscript from working when another version of Cyrus IMAPD is installed and 2.2 is in removed but not purged state (Closes: #393596) Files: 472f4f63615e420728286394e5770039 1276 mail extra cyrus-imapd-2.2_2.2.13-9.dsc 75ee864d7093e77d013d2c3e56e340dc 256030 mail extra cyrus-imapd-2.2_2.2.13-9.diff.gz 1eaaee09231834c9ac8ae2cb4fd7cd05 222388 doc extra cyrus-doc-2.2_2.2.13-9_all.deb 8f9a7dac2fb54e9892185d912a2dc7a5 80140 mail extra cyrus-admin-2.2_2.2.13-9_all.deb c7460e28f6de430705c9262c8aeb9760 5742092 mail extra cyrus-common-2.2_2.2.13-9_amd64.deb c5cf3d068c21cdbba41a33d816d7992c 945414 mail extra cyrus-imapd-2.2_2.2.13-9_amd64.deb 7dee207f9a5c199e736efaf45d8ca5e2 283218 mail extra cyrus-pop3d-2.2_2.2.13-9_amd64.deb 22ab10bb93aa130ba88d961da7682b04 1145570 mail extra cyrus-murder-2.2_2.2.13-9_amd64.deb 910943529629cdf683d2bc2c1d29425f 613646 mail extra cyrus-nntpd-2.2_2.2.13-9_amd64.deb d50a35933d84de4835a1be270a8b17a5 132218 mail extra cyrus-clients-2.2_2.2.13-9_amd64.deb 04bb3f7c2ac177425eded32c20538752 270240 devel extra cyrus-dev-2.2_2.2.13-9_amd64.deb 21dc3d7236def739848c739623d7cc6d 185046 perl extra libcyrus-imap-perl22_2.2.13-9_amd64.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFP6Tbev9LOsNKpIQRApYcAKDY3zOuGRgg8YFIwbk9Ymr9NvsPKQCgktqI 82om0HmeL1Cm29ItQoQKFkU= =4eto -----END PGP SIGNATURE-----
--- End Message ---
