Your message dated Fri, 14 Jan 2005 04:47:08 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#280529: fixed in mailman 2.1.5-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)
--------------------------------------
Received: (at submit) by bugs.debian.org; 10 Nov 2004 00:48:41 +0000
>From [EMAIL PROTECTED] Tue Nov 09 16:48:40 2004
Return-path: <[EMAIL PROTECTED]>
Received: from warsl404pip8.highway.telekom.at (email10.aon.at) [195.3.96.102]
by spohr.debian.org with smtp (Exim 3.35 1 (Debian))
id 1CRgfA-0001Ex-00; Tue, 09 Nov 2004 16:48:40 -0800
Received: (qmail 60528 invoked from network); 10 Nov 2004 00:48:06 -0000
Received: from l0651p29.dipool.highway.telekom.at (HELO forest)
([62.46.145.93]) (envelope-sender <[EMAIL PROTECTED]>)
by email10.aon.at (qmail-ldap-1.03) with SMTP
for <[EMAIL PROTECTED]>; 10 Nov 2004 00:48:06 -0000
Date: Wed, 10 Nov 2004 01:48:05 +0100
From: Markus Amersdorfer <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Migration from 2.0.11-1 to 2.1.5-3: update-Script aborts with error
Message-Id: <[EMAIL PROTECTED]>
X-Mailer: Sylpheed version 1.0.0beta2 (GTK+ 1.2.10; i686-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-7.0 required=4.0 tests=BAYES_00,DATING,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
Package: Mailman
Version: 2.1.5-3
Severity: critical
As part of a complete dist-upgrade, I tried to upgrade Mailman from
Woody's Mailman 2.0.11-1woody8 to the current Sarge version, 2.1.5-3.
Near the end of the update script, there's an AttributeError that keeps
the package from being installed correctly.
Here's a log-transcript for one of the configuration-reruns (thus the
mbox files "seem to be up-to-date" already).
--------------------------------
Setting up mailman (2.1.5-3) ...
Installing site language en ............................................
done.
Upgrading from version 0x2000bf0 to 0x20105f0
getting rid of old source files
Updating mailing list: ganymed-dev
Updating the held requests database.
- updating old private mbox file
Your installation seems up-to-date, great!
- updating old public mbox file
Fixing language templates: ganymed-dev
Updating mailing list: mailman
Updating the held requests database.
- updating old private mbox file
Your installation seems up-to-date, great!
- updating old public mbox file
Your installation seems up-to-date, great!
Fixing language templates: mailman
[... other mailing-lists similar to "mailman" above ...]
Updating Usenet watermarks
- nothing to update here
Updating Mailman 2.0 pending_subscriptions.db database
Traceback (most recent call last):
File "/usr/lib/mailman/bin/update", line 753, in ?
errors =3D main()
File "/usr/lib/mailman/bin/update", line 677, in main
update_pending()
File "/usr/lib/mailman/bin/update", line 556, in update_pending
addr =3D data[0].address
AttributeError: 'str' object has no attribute 'address'
dpkg: error processing mailman (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
mailman
--------------------------------
At the time of initially trying to install Mailman 2.1.5-3, python2.1
"2.1.3-25" and python2.3 "2.3.4-13" were installed on the system.
As a temporary workaround in order to get a working 2.1-based Mailman,
installing mailman_2.1.4-4.backports.org.1 worked just fine =AD no errors
occured.
(For the backports-Package, python2.2 "2.2.3-10" needed to be installed
too later...)
Justification for severity "critical": With the Sarge-release coming
closer every day, this bug might affect lots of users eventually!
---------------------------------------
Received: (at 280529-close) by bugs.debian.org; 14 Jan 2005 09:53:30 +0000
>From [EMAIL PROTECTED] Fri Jan 14 01:53:30 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CpO93-0004UM-00; Fri, 14 Jan 2005 01:53:30 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1CpO2u-0003Ov-00; Fri, 14 Jan 2005 04:47:08 -0500
From: Tollef Fog Heen <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.54 $
Subject: Bug#280529: fixed in mailman 2.1.5-5
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Fri, 14 Jan 2005 04:47:08 -0500
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-5.0 required=4.0 tests=BAYES_00,DATING,
HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Source: mailman
Source-Version: 2.1.5-5
We believe that the bug you reported is fixed in the latest version of
mailman, which is due to be installed in the Debian FTP archive:
mailman_2.1.5-5.diff.gz
to pool/main/m/mailman/mailman_2.1.5-5.diff.gz
mailman_2.1.5-5.dsc
to pool/main/m/mailman/mailman_2.1.5-5.dsc
mailman_2.1.5-5_i386.deb
to pool/main/m/mailman/mailman_2.1.5-5_i386.deb
mailman_2.1.5.orig.tar.gz
to pool/main/m/mailman/mailman_2.1.5.orig.tar.gz
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.
Tollef Fog Heen <[EMAIL PROTECTED]> (supplier of updated mailman 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, 10 Jan 2005 17:12:58 +0100
Source: mailman
Binary: mailman
Architecture: source i386
Version: 2.1.5-5
Distribution: unstable
Urgency: high
Maintainer: Tollef Fog Heen <[EMAIL PROTECTED]>
Changed-By: Tollef Fog Heen <[EMAIL PROTECTED]>
Description:
mailman - Powerful, web-based mailing list manager
Closes: 280529 284771 285839 286796 287555
Changes:
mailman (2.1.5-5) unstable; urgency=high
.
* Fix CAN-2004-1143 (weak auto-generated passwords) by pulling the
appropriate CVS change from upstream. Thanks to Florian Weimer for
finding and producing a patch for this bug. (closes: #286796)
* Fix CAN-2004-1177 (CSS problem in scripts/driver) by pulling the
appropriate patch from upstream CVS. Thanks to Florian Weimer for
discovering and producing a patch for this bug. (closes: #287555)
* Handle the case of upgrading from Mailman 2.0 where we have
pending subscriptions. This should hopefully fix #280529. Thanks to
Bastian Kleinedam for the patch. (closes: #280529)
* Skip directories when updating templates, to make the life easier for
people who have their configuration in Subversion or Arch.
(closes: #284771)
* Remove 55_options_traceback.dpatch as this problem seems to have been
fixed upstream and it causes other problems. (closes: #285839)
Files:
211e90f80573d909d805e2b9d40dd21e 640 mail optional mailman_2.1.5-5.dsc
f5f56f04747cd4aff67427e7a45631af 5745912 mail optional
mailman_2.1.5.orig.tar.gz
7c0131c39ae93621120673b94cde9be7 174358 mail optional mailman_2.1.5-5.diff.gz
997fd482d1a92d751c132a449d150fc9 6607802 mail optional mailman_2.1.5-5_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQFB55BlQSseMYF6mWoRAkzVAKDa2oVG7RsLLZ/P2rUFQj2pkporAwCaA+t/
6oqxdXJcck5pDz8V85oMpPw=
=af3J
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
