Your message dated Tue, 15 Aug 2006 09:17:30 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#382422: fixed in pymsnt 0.11.1-5 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: pymsnt Version: 0.11.1-4 Severity: normal /etc/cron.daily/logrotate reports the following: error: pymsnt:1 duplicate log entry for /var/log/jabber/pymsnt.log run-parts: /etc/cron.daily/logrotate exited with return code 1 (pymsnt's log is referenced both by /etc/logrotate.d/jabber and /etc/logrotate.d/pysmnt) It is debatable whether to file this under jabberd or pymsnt, but some form of coordination with the main package is welcome, not only wrt logs. For example, jabberd restarts the jabber-* transport it knows about but not pymsnt. Count me in for testing, anyway. -- System Information: Debian Release: testing/unstable APT prefers testing-proposed-updates APT policy: (500, 'testing-proposed-updates'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.5 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages pymsnt depends on: ii jabber-common 0.4 Jabber server and transport (commo ii python 2.3.5-11 An interactive high-level object-o ii python-central 0.5.1 register and build utility for Pyt ii python-crypto 2.0.1+dfsg1-1.2 cryptographic algorithms and proto ii python-pyopenssl 0.6-2.3 Python wrapper around the OpenSSL ii python-twisted 2.4.0-2 Event-based framework for internet Versions of packages pymsnt recommends: ii python-imaging 1.1.5-10 Python Imaging Library -- no debconf information
--- End Message ---
--- Begin Message ---Source: pymsnt Source-Version: 0.11.1-5 We believe that the bug you reported is fixed in the latest version of pymsnt, which is due to be installed in the Debian FTP archive: pymsnt_0.11.1-5.diff.gz to pool/main/p/pymsnt/pymsnt_0.11.1-5.diff.gz pymsnt_0.11.1-5.dsc to pool/main/p/pymsnt/pymsnt_0.11.1-5.dsc pymsnt_0.11.1-5_all.deb to pool/main/p/pymsnt/pymsnt_0.11.1-5_all.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. Sam Morris <[EMAIL PROTECTED]> (supplier of updated pymsnt 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: Mon, 14 Aug 2006 01:15:51 +0100 Source: pymsnt Binary: pymsnt Architecture: source all Version: 0.11.1-5 Distribution: unstable Urgency: low Maintainer: Sam Morris <[EMAIL PROTECTED]> Changed-By: Sam Morris <[EMAIL PROTECTED]> Description: pymsnt - MSN transport for Jabber Closes: 382422 Changes: pymsnt (0.11.1-5) unstable; urgency=low . * No longer depend on jabber-common; give pymsnt its own user (closes: #382422) Files: aaf9f829671985b84cef1ddfa73ed984 683 net optional pymsnt_0.11.1-5.dsc aed6b973ec209e3ff968517285950aa7 5971 net optional pymsnt_0.11.1-5.diff.gz f03eaf1120b55771f7072698527dddf5 156712 net optional pymsnt_0.11.1-5_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFE4fArqbb3MLg9dhwRAogTAJ45+hH3pM72IBjPIOrbzAp2KIzuOwCZAeIM b/xZCfQUpGaP/l43GNfa4Yc= =BTFe -----END PGP SIGNATURE-----
--- End Message ---
