Debian
mailman package

Migration from 2.0.11-1 to 2.1.5-3: update-Script aborts with error

Bug #10158 reported by Debian Bug Importer
6
Affects Status Importance Assigned to Milestone
mailman (Debian)
Fix Released
Unknown
mailman (Ubuntu)
Fix Released
High
Matthias Klose

Bug Description

Automatically imported from Debian bug report #280529 http://bugs.debian.org/280529

See original description

CVE References

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Automatically imported from Debian bug report #280529 http://bugs.debian.org/280529

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Wed, 10 Nov 2004 01:48:05 +0100
From: Markus Amersdorfer <email address hidden>
To: <email address hidden>
Subject: Migration from 2.0.11-1 to 2.1.5-3: update-Script aborts with error

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!

Revision history for this message
In , Steve Langasek (vorlon) wrote :

severity 280529 serious
thanks

> Justification for severity "critical": With the Sarge-release coming
> closer every day, this bug might affect lots of users eventually!

That is not a justification for use of the critical severity. Please
re-read the definitions of bug severities at
<http://www.debian.org/Bugs/Developer#severities>.

--
Steve Langasek
postmodern programmer

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Wed, 10 Nov 2004 04:13:52 -0800
From: Steve Langasek <email address hidden>
To: <email address hidden>
Subject: Re: Migration from 2.0.11-1 to 2.1.5-3: update-Script aborts with error

--qcHopEYAB45HaUaB
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

severity 280529 serious
thanks

> Justification for severity "critical": With the Sarge-release coming
> closer every day, this bug might affect lots of users eventually!

That is not a justification for use of the critical severity. Please
re-read the definitions of bug severities at
<http://www.debian.org/Bugs/Developer#severities>.

--=20
Steve Langasek
postmodern programmer

--qcHopEYAB45HaUaB
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBkgX9KN6ufymYLloRAj0CAJ9CjrEeHbGo97CnMxjL2vGEv/TsYgCgs1RP
1iBmMgMiEUVqyXmOiiugE7A=
=1rPe
-----END PGP SIGNATURE-----

--qcHopEYAB45HaUaB--

Revision history for this message
In , Markus Amersdorfer (der-plusch) wrote : Re: Bug#280529: Migration from 2.0.11-1 to 2.1.5-3: update-Script aborts with error

Hi Steve,

> > Justification for severity "critical": With the Sarge-release coming
> > closer every day, this bug might affect lots of users eventually!
>
> That is not a justification for use of the critical severity. Please
> re-read the definitions of bug severities at
> <http://www.debian.org/Bugs/Developer#severities>.

Thanks for clearing this up for me.
I asked on IRC what severity level to use and one person replied with
"critical".
Though I read the page you mentioned, I must have overseen the
"unsuitable for release" words. Well, it seems one should not file bug
reports in the middle of the night... :)

Thanks again and have a nice day,
Markus

--
Information is always to be treasured, Raul. It is behind only love
and honesty in a person's attempt to understand the universe.
                                            <Dan Simmons, Endymion>
http://homex.subnet.at/~max/

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Wed, 10 Nov 2004 15:52:57 +0100
From: Markus Amersdorfer <email address hidden>
To: Steve Langasek <email address hidden>, <email address hidden>
Subject: Re: Bug#280529: Migration from 2.0.11-1 to 2.1.5-3: update-Script
 aborts with error

--Signature=_Wed__10_Nov_2004_15_52_57_+0100_zY.sDJRrhzXPCWwa
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Hi Steve,

> > Justification for severity "critical": With the Sarge-release coming
> > closer every day, this bug might affect lots of users eventually!
>
> That is not a justification for use of the critical severity. Please
> re-read the definitions of bug severities at
> <http://www.debian.org/Bugs/Developer#severities>.

Thanks for clearing this up for me.
I asked on IRC what severity level to use and one person replied with
"critical".
Though I read the page you mentioned, I must have overseen the
"unsuitable for release" words. Well, it seems one should not file bug
reports in the middle of the night... :)

Thanks again and have a nice day,
Markus

--
Information is always to be treasured, Raul. It is behind only love
and honesty in a person's attempt to understand the universe.
                                            <Dan Simmons, Endymion>
http://homex.subnet.at/~max/

--Signature=_Wed__10_Nov_2004_15_52_57_+0100_zY.sDJRrhzXPCWwa
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBkitN2UG9bWwchaMRAjh3AJ4qYf5+STcF/oejv3b44UkH85UNOACeNRRV
YnKJ2hfs+8CvzxBq/v6jFfM=
=AdYd
-----END PGP SIGNATURE-----

--Signature=_Wed__10_Nov_2004_15_52_57_+0100_zY.sDJRrhzXPCWwa--

Revision history for this message
In , Laszlo Boszormenyi (gcs) wrote : seems to be an upstream problem

Hi,

 At the point you get AttributeError, the update script expects a UserDesc
class, but it does not get that, so data[0] defaults to a string I
believe. Anyway nor the correct UserDesc class has address specified as
I see, so I suspect it is a bad upstream bug. It is rarely hit, only if
you upgrade when someone tries to subscribe to one of your lists, but
not yet answered the confirmation mail when you doing the upgrade.
Will look into it somewhen.

Regards,
Laszlo/GCS

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <20041113210517.GA8161@pooh>
Date: Sat, 13 Nov 2004 22:05:18 +0100
From: Laszlo 'GCS' Boszormenyi <email address hidden>
To: <email address hidden>
Subject: seems to be an upstream problem

Hi,

 At the point you get AttributeError, the update script expects a UserDesc
class, but it does not get that, so data[0] defaults to a string I
believe. Anyway nor the correct UserDesc class has address specified as
I see, so I suspect it is a bad upstream bug. It is rarely hit, only if
you upgrade when someone tries to subscribe to one of your lists, but
not yet answered the confirmation mail when you doing the upgrade.
Will look into it somewhen.

Regards,
Laszlo/GCS

Revision history for this message
In , Bastian Kleineidam (calvin) wrote :

Hi,

can you please try the attached patch? I cannot test it myself.

Regards,
  Bastian

--
  ,''`. Bastian Kleineidam
 : :' : GnuPG Schlüssel
 `. `' gpg --keyserver wwwkeys.pgp.net --recv-keys 32EC6F3E
   `-

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <20041215163214.GA10306@treasure>
Date: Wed, 15 Dec 2004 17:32:14 +0100
From: Bastian Kleineidam <email address hidden>
To: <email address hidden>, <email address hidden>
Subject: Re: Migration from 2.0.11-1 to 2.1.5-3: update-Script aborts with error

--Fba/0zbH8Xs+Fj9o
Content-Type: multipart/mixed; boundary="wac7ysb48OaltWcw"
Content-Disposition: inline

--wac7ysb48OaltWcw
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

can you please try the attached patch? I cannot test it myself.

Regards,
  Bastian

--=20
  ,''`. Bastian Kleineidam
 : :' : GnuPG Schl=FCssel
 `. `' gpg --keyserver wwwkeys.pgp.net --recv-keys 32EC6F3E
   `-

--wac7ysb48OaltWcw
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="mailman_update.diff"

--- update.orig 2004-12-15 17:25:41.000000000 +0100
+++ update 2004-12-15 17:29:09.000000000 +0100
@@ -532,9 +532,11 @@
     file20 = os.path.join(mm_cfg.DATA_DIR, 'pending_subscriptions.db')
     file214 = os.path.join(mm_cfg.DATA_DIR, 'pending.pck')
     db = None
+ ver = None
     # Try to load the Mailman 2.0 file
     try:
         fp = open(file20)
+ ver = "20"
     except IOError, e:
         if e.errno <> errno.ENOENT: raise
     else:
@@ -546,6 +548,7 @@
         # Try to load the Mailman 2.1.x where x < 5, file
         try:
             fp = open(file214)
+ ver = "214"
         except IOError, e:
             if e.errno <> errno.ENOENT: raise
         else:
@@ -579,8 +582,12 @@
             # data[0] is the address being unsubscribed
             addrops_by_address.setdefault(data[0], []).append((key, val))
         elif op == Pending.SUBSCRIPTION:
- # data[0] is a UserDesc object
- addr = data[0].address
+ if ver == "20":
+ # data is tuple (emailaddr, password, digest)
+ addr = data[0]
+ else:
+ # data[0] is a UserDesc object
+ addr = data[0].address
             subs_by_address.setdefault(addr, []).append((key, val))
         elif op == Pending.RE_ENABLE:
             # data[0] is the mailing list's internal name

--wac7ysb48OaltWcw--

--Fba/0zbH8Xs+Fj9o
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBwGcOeBwlBDLsbz4RAql7AJ9fAPHa2VwqHP+mcLcYbbsyfGjOdQCgz5P9
Q750qyO3wEqcE96Y64Yu/SA=
=dBUI
-----END PGP SIGNATURE-----

--Fba/0zbH8Xs+Fj9o--

Revision history for this message
In , Bastian Kleineidam (calvin) wrote : tagging 280529

# Automatically generated email from bts, devscripts version 2.8.5
tags 280529 + patch

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Thu, 16 Dec 2004 12:22:52 +0100
From: Bastian Kleineidam <email address hidden>
To: <email address hidden>
Subject: tagging 280529

# Automatically generated email from bts, devscripts version 2.8.5
tags 280529 + patch

Revision history for this message
In , Tollef Fog Heen (tfheen) wrote : Bug#280529: fixed in mailman 2.1.5-5

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 address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tollef Fog Heen <email address hidden> (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 address hidden>)

-----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 address hidden>
Changed-By: Tollef Fog Heen <email address hidden>
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-----

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Fri, 14 Jan 2005 04:47:08 -0500
From: Tollef Fog Heen <email address hidden>
To: <email address hidden>
Subject: Bug#280529: fixed in mailman 2.1.5-5

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 address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tollef Fog Heen <email address hidden> (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 address hidden>)

-----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 address hidden>
Changed-By: Tollef Fog Heen <email address hidden>
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-----

Revision history for this message
Matthias Klose (doko) wrote :

fixed in mailman (2.1.5-5)

Revision history for this message
Matthias Klose (doko) wrote :

reopen, mailman (2.1.5-5) is not yet synced.

Revision history for this message
In , Xabbu (xabbu) wrote : mailman: bug remains for 2.1.5-5

Package: mailman
Version: 2.1.5-5
Followup-For: Bug #280529

I get the exact same error during an upgrade from woody
in my mixed woody/sarge system with the new package 2.1.5-5.
I upgraded to exim4 directly before and did not yet configure
it properly for mailman.

I don't think I had any open subscriptions. And I don't see any
after downgrading to 2.0.11-1woody8 and checking the administrative
request of all my mailing lists.

a dumpdb of pending_subscriptions.db gives me the following result:
{ 509670: ('<email address hidden>', 'runway18', 0, 1093890902),
    'lastculltime': 1094104249}
<email address hidden> is subscribed to one of my mailing lists, but
I don't think this subscription is pending (he seems to be normally
subscribed in the membership management webpage) but I send him
a mail asking if he got any list-mails anyway.

I have a empty pending_subscriptions.db.new in the same directory.
I copied the .new one over the pending_subscriptions.db and could
then upgrade without a problem. I still have the old file around
in case you need it.

Greetings and Thanks for you work
Nathan Gass

-- System Information:
Debian Release: 3.0
  APT prefers testing
  APT policy: (190, 'testing'), (90, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.26-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages mailman depends on:
ii apache [httpd] 1.3.33-3 versatile, high-performance HTTP s
ii cron 3.0pl1-72 management of regular background p
ii debconf 1.4.30.11 Debian configuration management sy
ii exim4 4.34-10 An MTA (Mail Transport Agent)
ii exim4-daemon-light [mail-tr 4.34-10 Lightweight version of the Exim (v
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
ii logrotate 3.5.9-8 Log rotation utility
ii pwgen 2.03-1 Automatic Password generation
ii python 2.3.4-5 An interactive high-level object-o
ii ucf 1.13 Update Configuration File: preserv

-- debconf information:
  mailman/queue_files_present:
* mailman/default_server_language: en
* mailman/gate_news: false
* mailman/site_languages: en
* mailman/used_languages: en
* mailman/create_site_list:

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <E1Cto7V-0008CJ-I2@ghost>
Date: Wed, 26 Jan 2005 15:26:09 +0100
From: <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: mailman: bug remains for 2.1.5-5

Package: mailman
Version: 2.1.5-5
Followup-For: Bug #280529

I get the exact same error during an upgrade from woody
in my mixed woody/sarge system with the new package 2.1.5-5.
I upgraded to exim4 directly before and did not yet configure
it properly for mailman.

I don't think I had any open subscriptions. And I don't see any
after downgrading to 2.0.11-1woody8 and checking the administrative
request of all my mailing lists.

a dumpdb of pending_subscriptions.db gives me the following result:
{ 509670: ('<email address hidden>', 'runway18', 0, 1093890902),
    'lastculltime': 1094104249}
<email address hidden> is subscribed to one of my mailing lists, but
I don't think this subscription is pending (he seems to be normally
subscribed in the membership management webpage) but I send him
a mail asking if he got any list-mails anyway.

I have a empty pending_subscriptions.db.new in the same directory.
I copied the .new one over the pending_subscriptions.db and could
then upgrade without a problem. I still have the old file around
in case you need it.

Greetings and Thanks for you work
Nathan Gass

-- System Information:
Debian Release: 3.0
  APT prefers testing
  APT policy: (190, 'testing'), (90, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.26-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages mailman depends on:
ii apache [httpd] 1.3.33-3 versatile, high-performance HTTP s
ii cron 3.0pl1-72 management of regular background p
ii debconf 1.4.30.11 Debian configuration management sy
ii exim4 4.34-10 An MTA (Mail Transport Agent)
ii exim4-daemon-light [mail-tr 4.34-10 Lightweight version of the Exim (v
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
ii logrotate 3.5.9-8 Log rotation utility
ii pwgen 2.03-1 Automatic Password generation
ii python 2.3.4-5 An interactive high-level object-o
ii ucf 1.13 Update Configuration File: preserv

-- debconf information:
  mailman/queue_files_present:
* mailman/default_server_language: en
* mailman/gate_news: false
* mailman/site_languages: en
* mailman/used_languages: en
* mailman/create_site_list:

Revision history for this message
Matt Zimmerman (mdz) wrote :

   mailman | 2.1.5-7 | http://us.archive.ubuntu.com hoary/main Packages

Bug Watch Updater (bug-watch-updater)
Changed in mailman:
status: Unknown → Fix Released
Revision history for this message
In , Don Armstrong (don-debian) wrote : Re: [Fwd: Re: Bug#280529: fixed in mailman 2.1.5-5]

# upstream maintainer has more complete patch
unarchive 280529
thanks

On Sat, 14 Mar 2009, Mark Sapiro wrote:
> I attempted to reply to this bug with the message below by following the
> the 'reply' link in the bug report which is
> <mailto:<email address hidden>> with the result:
>
> 2009-03-14 14:06:58 KGILBL-000110-KL ** <email address hidden>
> R=dnslookup T=remote_smtp: SMTP error from remote mail server after RCPT
> TO:<email address hidden>: host rietz.debian.org [140.211.166.43]: 550
> unknown user

That bug is archived, you'll need to unarchive it before mailing it.
I've done that with this message; feel free to respond to it in a few
minutes.

Don Armstrong

--
Three little words. (In descending order of importance.)
I
love
you
 -- hugh macleod http://www.gapingvoid.com/graphics/batch35.php

http://www.donarmstrong.com http://rzlab.ucr.edu

Revision history for this message
In , Mark Sapiro (msapiro) wrote : Re: Bug#280529: fixed in mailman 2.1.5-5

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This is a message from the upstream Mailman maintainer.

The fix for this bug at
<http://patch-tracking.debian.net/patch/series/view/mailman/1:2.1.11-11/67_update_handle_old_versions.patch>
is incomplete. It recognizes when it is looking at a tuple vs. a
UserDesc instance for purposes of extracting the address, but in the
case of a tuple, it pends a new request containing the tuple rather than
a UserDesc instance. This merely postpones the problem until the request
is confirmed.

The correct fix is to change Pending._update() to return a UserDesc
instance. This fix will be in Mailman 2.2.

- --
Mark Sapiro <email address hidden> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)

iD8DBQFJvGx/VVuXXpU7hpMRAs48AKDHseVIlkMCNLVxIBu6hqDB3PGG1ACg2ndZ
3GFKtryt/YGlXRYEfl2qTZQ=
=P8HG
-----END PGP SIGNATURE-----

Revision history for this message
In , Thijs Kinkhorst (kink) wrote : Re: [Pkg-mailman-hackers] Bug#280529: fixed in mailman 2.1.5-5

Hi Mark,

On snein 15 Maart 2009, Mark Sapiro wrote:
> This is a message from the upstream Mailman maintainer.
>
> The fix for this bug at
> <http://patch-tracking.debian.net/patch/series/view/mailman/1:2.1.11-11/67_
>update_handle_old_versions.patch> is incomplete. It recognizes when it is
> looking at a tuple vs. a
> UserDesc instance for purposes of extracting the address, but in the
> case of a tuple, it pends a new request containing the tuple rather than
> a UserDesc instance. This merely postpones the problem until the request
> is confirmed.
>
> The correct fix is to change Pending._update() to return a UserDesc
> instance. This fix will be in Mailman 2.2.

Thanks for your help. I think however that we can close this bug since version
1:2.1.12-1 of the package no longer includes that patch - we dont' support
upgrades from the 2.0.x series anymore.

cheers,
Thijs

Revision history for this message
In , Mark Sapiro (msapiro) wrote : Re: Re: [Pkg-mailman-hackers] Bug#280529: fixed in mailman 2.1.5-5

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thijs Kinkhorst wrote:
>
> On snein 15 Maart 2009, Mark Sapiro wrote:
>> This is a message from the upstream Mailman maintainer.
>>
>> The fix for this bug at
>> <http://patch-tracking.debian.net/patch/series/view/mailman/1:2.1.11-11/67_
>> update_handle_old_versions.patch> is incomplete. It recognizes when it is
>> looking at a tuple vs. a
>> UserDesc instance for purposes of extracting the address, but in the
>> case of a tuple, it pends a new request containing the tuple rather than
>> a UserDesc instance. This merely postpones the problem until the request
>> is confirmed.
>>
>> The correct fix is to change Pending._update() to return a UserDesc
>> instance. This fix will be in Mailman 2.2.
>
> Thanks for your help. I think however that we can close this bug since version
> 1:2.1.12-1 of the package no longer includes that patch - we dont' support
> upgrades from the 2.0.x series anymore.

It's fine with me if the bug is closed. My only point in reporting what
I did is there is a Debian patch to bin/update at
<http://patch-tracking.debian.net/patch/series/view/mailman/1:2.1.11-11/67_update_handle_old_versions.patch>
which is still being applied, at least to Mailman 2.1.11.

I have committed a change to Pending.py on the 2.2 branch which
conflicts with 67_update_handle_old_versions.patch, and I wanted you to
know this.

- --
Mark Sapiro <email address hidden> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)

iD8DBQFJvUqKVVuXXpU7hpMRAnZGAKD7NmcruyoweuPdwob9DIkHKmLz7QCff4m3
WO5ATWYqNmcMDkefW0RF5eU=
=4jLA
-----END PGP SIGNATURE-----

Revision history for this message
In , Thijs Kinkhorst (kink) wrote : Re: [Pkg-mailman-hackers] Bug#280529: fixed in mailman 2.1.5-5

On snein 15 Maart 2009, Mark Sapiro wrote:
> It's fine with me if the bug is closed. My only point in reporting what
> I did is there is a Debian patch to bin/update at
> <http://patch-tracking.debian.net/patch/series/view/mailman/1:2.1.11-11/67_
>update_handle_old_versions.patch> which is still being applied, at least to
> Mailman 2.1.11.
>
> I have committed a change to Pending.py on the 2.2 branch which
> conflicts with 67_update_handle_old_versions.patch, and I wanted you to
> know this.

Excellent, it is now well documented and the bug is not listed as affecting
our current version, so that's exactly where we want to be :-)

Thijs

Revision history for this message
In , Lionel Elie Mamane (lionel-mamane) wrote :

On Sun, Mar 15, 2009 at 08:03:22PM +0100, Thijs Kinkhorst wrote:
> On snein 15 Maart 2009, Mark Sapiro wrote:
>> It's fine with me if the bug is closed. My only point in reporting what
>> I did is there is a Debian patch to bin/update at
>> <http://patch-tracking.debian.net/patch/series/view/mailman/1:2.1.11-11/67_
>>update_handle_old_versions.patch> which is still being applied, at least to
>> Mailman 2.1.11.

>> I have committed a change to Pending.py on the 2.2 branch which
>> conflicts with 67_update_handle_old_versions.patch, and I wanted you to
>> know this.

> Excellent, it is now well documented and the bug is not listed as
> affecting our current version, so that's exactly where we want to be
> :-)

Well, the version graph on the top of the bug page shows all versions
as red, I'm not sure why.

--
Lionel

Revision history for this message
In , Thomas Viehmann (tv-beamnet) wrote : bug housekeeping

Version: 1:2.1.12-1

Hi Thijs,

Thijs Kinkhorst:
 > Excellent, it is now well documented and the bug is not listed as
 > affecting our current version, so that's exactly where we want to be
 > :-)

Actually, it is marked a affecting the current version. From the bug log
I think you wanted a versioned close, so I'm trying that.

Kind regards

T.
--
Thomas Viehmann, http://thomas.viehmann.net/

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.