[ mailman-Bugs-1395683 ] UnicodeError running arch

SourceForge.net noreply at sourceforge.net
Sat Jan 14 14:11:56 CET 2006


Bugs item #1395683, was opened at 2006-01-03 01:12
Message generated for change (Comment added) made by tkikuchi
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1395683&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Pipermail
Group: 2.1 (stable)
>Status: Closed
Resolution: Fixed
Priority: 7
Submitted By: Michael Wallis (kf6spf)
Assigned to: Tokio Kikuchi (tkikuchi)
Summary: UnicodeError running arch

Initial Comment:
I just deployed the latest release (2.1.7 stable) and
decided to rebuild an archive. I'm getting the
following error trace caused by it hitting high-order
byte characters. These were not a problem when I first
built the archive from 2.1.6 so something may have changed.

Pickling archive state into
/usr/local/mailman/archives/private/basfa/pipermail.pck
Traceback (most recent call last):
  File "bin/arch", line 200, in ?
    main()
  File "bin/arch", line 188, in main
    archiver.processUnixMailbox(fp, start, end)
  File
"/usr/local/mailman/Mailman/Archiver/pipermail.py",
line 585, in processUnixMailbox
    self.add_article(a)
  File
"/usr/local/mailman/Mailman/Archiver/pipermail.py",
line 626, in add_article
    filename))
  File
"/usr/local/mailman/Mailman/Archiver/HyperArch.py",
line 1116, in write_article
    f.write(article.as_text())
  File
"/usr/local/mailman/Mailman/Archiver/HyperArch.py",
line 579, in as_text
    '\g<1>' + _(' at ') + '\g<2>', body)
  File "/usr/lib/python2.2/sre.py", line 143, in sub
    return _compile(pattern, 0).sub(repl, string, count)
UnicodeError: ASCII decoding error: ordinal not in
range(128)

----------------------------------------------------------------------

>Comment By: Tokio Kikuchi (tkikuchi)
Date: 2006-01-14 13:11

Message:
Logged In: YES 
user_id=67709

Closing now bcause this is included in a new patch.


----------------------------------------------------------------------

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2006-01-10 21:34

Message:
Logged In: YES 
user_id=67709

Re-open for visitors can find this.

----------------------------------------------------------------------

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2006-01-09 07:41

Message:
Logged In: YES 
user_id=67709

Hi, I've just committed this patch in the CVS.

I'll be releasing 2.1.8 but, in the meantime, please use
this patch.

Sorry for the inconvenience.


----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-01-06 05:43

Message:
Logged In: YES 
user_id=1123998

I have deleted my patch # 161995 to avoid confusion as patch
# 162200 is the correct one.

----------------------------------------------------------------------

Comment By: Tokio Kikuchi (tkikuchi)
Date: 2006-01-05 02:50

Message:
Logged In: YES 
user_id=67709

Here is a revised patch to incorporate non-ascii '_at_'
replacement.


----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-01-03 18:20

Message:
Logged In: YES 
user_id=1123998

One other followup note on this.  The problem can also occur
when archiving an individual post to a list. In this case,
the HTML file for the post will be written but not indexed;
the post will not be added to the .txt file; the error will
be logged in the 'error' log, and the message will be shunted.

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-01-03 17:28

Message:
Logged In: YES 
user_id=1123998

The previous patch wasn't effective in all circumstances. I
have replaced it again.

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-01-03 05:21

Message:
Logged In: YES 
user_id=1123998

I've developed a new patch which I've attached here in place
of the previous one. I think the new patch actually fixes
the problem. Please try it and report.

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2006-01-03 01:54

Message:
Logged In: YES 
user_id=1123998

I also observed this problem. It will be properly fixed. In
the mean time, I have attached a patch - HyperArch.patch -
which will allow you to rebuild the full archive. The patch
is not a real fix for the problem however, as the problem
messages will not have email addresses obscured in the body
of the message in the monthly .txt files. The HTML archive
will be OK.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1395683&group_id=103


More information about the Mailman-coders mailing list