[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#412340: marked as done (mailman: upgrade may break archiving)

Your message dated Wed, 28 Feb 2007 07:23:19 +0100
with message-id <20070228062319.GA13159@capsaicin.mamane.lu>
and subject line Forget it
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: release-notes

A mailman issue has come up for the sarge -> etch upgrade which we may
not be able to fix in time for etch (as upstream has been aware of the
issue for more than a year but still hasn't fixed it; we have been
aware of that issue only for a few days). An accurate description of
the current situation is:

 If you upgrade mailman at a moment such that a message with non-ASCII
 encodable subject or sender got archived (i.e. sent to a mailing list
 that is archived with the built-in pipermail) in the current archive
 volume, then after the upgrade new messages will fail to be archived
 with an error like:

 Uncaught runner exception: 'ascii' codec can't decode byte 0xae in position 6: ordinal not in range(128)
 Traceback (most recent call last):
  File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 112, in _oneloop
    self._onefile(msg, msgdata)
  File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 170, in _onefile
    keepqueued = self._dispose(mlist, msg, msgdata)
  File "/usr/lib/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose
  File "/usr/lib/mailman/Mailman/Archiver/Archiver.py", line 214, in ArchiveMail
  File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 580, in processUnixMailbox
  File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 632, in add_article

 If you were keeping both mbox and HTML archives (even if the mbox
 archives were not made available over HTTP), then you can cure that
 issue by regenerating the HTML archives (and current-volume pickle
 database, which is the root of the problem) from scratch with:

 /var/lib/mailman/bin/arch --wipe <listname>


--- End Message ---
--- Begin Message ---
I managed to mostly fix the problem, so no mention in release notes


--- End Message ---

Reply to: