Chris Toomey wrote:
> Great, thanks Mark. Will you or someone else be updating the sourceforge
> patches with these? Would be nice to keep the patches for various mm
> versions consolidated there.
The SourceForge tracker is no longer used for Mailman. The current
tracker is at Launchpad. The s
Great, thanks Mark. Will you or someone else be updating the sourceforge
patches with these? Would be nice to keep the patches for various mm
versions consolidated there.
Chris
On Mon, Dec 6, 2010 at 11:42 AM, Mark Sapiro wrote:
> Chris Toomey wrote:
> >
> >Can somebody update those patches f
Chris Toomey wrote:
>
>Can somebody update those patches for 2.1.14, or should I just go with
>2.1.10? Also, I've not been able to find any documentation on the changes
>made in each mailman release so it's hard to tell what I'd be giving up in
>going w/ 2.1.10 -- can someone point me to where tha
Hi, I'd like to do a fresh install of mailman with the htdig integration as
described at
http://www.mail-archive.com/mailman-users@python.org/msg11713.html .
However, the 2 patches were last updated for mailman 2.1.10 and mailman's
now up to version 2.1.14.
Can somebody update those patches for 2.
On Wed, 22 Jan 2003, Richard Barrett wrote:
> In response to your input I have posted a revised version of patch #444884
> for MM 2.1 on sourceforge as file htdig-2.1-0.3.patch
> Thanks for your heads up on the problem and your observation. Sorry for the
> errors. Your suggested change was not qu
At 16:21 22/01/2003, Todd C. Miller wrote:
After a bit of head scratching I have tracked the problem down to
privoxy (a filtering, ad-blocking proxy). It has the following
rule in its default config:
# The status bar is for displaying link targets, not pointless blahblah
#
s/([\n =;{}]|window\.)
After a bit of head scratching I have tracked the problem down to
privoxy (a filtering, ad-blocking proxy). It has the following
rule in its default config:
# The status bar is for displaying link targets, not pointless blahblah
#
s/([\n =;{}]|window\.)(default)?status\s*=/$1dUmMy=/ig
which is w
Todd
It would help to know which version of the patch file you are using and
where you got it from.
I have grep'ed my copies of the various versions of my htdig patch file and
cannot find a line that reads as you assert yours does; see the grep
results below.
There are three lines containing
I also get the following error from nightly_htdig:
Traceback (most recent call last):
File "/var/mailman/cron/nightly_htdig", line 153, in ?
main()
File "/var/mailman/cron/nightly_htdig", line 138, in main
if status:
NameError: global name 'status' is not defined
Which corresponds to
Steve
In response to your input I have posted a revised version of patch #444884
for MM 2.1 on sourceforge as file htdig-2.1-0.3.patch
Thanks for your heads up on the problem and your observation. Sorry for the
errors. Your suggested change was not quite right; good try but no cigar.:)
I've co
I've applied the patches, but have had a few problems. I emailed Richard
Barrett through sourceforge, and don't know if you got it, so I'll start with
what I've figured out since then.
Should line 1485 of htdig-2.1-0.2.patch read "if (not ctype) or cencode:"
instead of reading "if not (ctype an
If you use my Mailman/htdig integration patches and are using MM 2.1 final
you will definitely find the new version of the #444884 patch I have just
uploaded useful.
This revised patch incorporates a fix for a fairly gross bug in
$prefix/Mailman/Cgi/htdig.py; don't ask: the embarrassment is too
12 matches
Mail list logo
