On 09/28/2016 09:34 PM, Christopher Adams wrote:
> I did patch the installed instance of Mailman
> (/usr/local/mailman/Mailman/Cgi/admin.py). I can see the changes that
> it made, but the result is the same when looking at the subscriber list.
The patch converts a unicode URL to the character se
I did patch the installed instance of Mailman
(/usr/local/mailman/Mailman/Cgi/admin.py). I can see the changes that it
made, but the result is the same when looking at the subscriber list.
On Sep 28, 2016 4:37 PM, "Mark Sapiro" wrote:
> On 09/28/2016 04:28 PM, Christopher Adams wrote:
> > Thank
On 09/28/2016 04:58 PM, willi uebelherr wrote:
> 2016-09-28 19:12 GMT-04:00 Mark Sapiro :
>> ,,,
>> You could, but it isn't necessary.
>
> Dear
>
> i follow your discussion with Christopher. Your short answer " it
> isn't necessary". Can you explain this?
He asked if he should apply the patch t
2016-09-28 19:12 GMT-04:00 Mark Sapiro :
> ,,,
> You could, but it isn't necessary.
Dear
i follow your discussion with Christopher. Your short answer " it
isn't necessary". Can you explain this?
greetings, willi
Asuncion, Paraguay
--
Mailman-Us
On 09/28/2016 04:28 PM, Christopher Adams wrote:
> Thank you. I did patch the admin.py file and I can see the changes.
> However, if I go to the list subscribers, the link to the next group of
> addresses takes me back to the main admin page.
>
> I did notice that the URL includes < u'http://
On 09/28/2016 01:29 PM, Mark Graves wrote:
> I'm using Mailman v2.1.21 on openSUSE Leap 42.1 and received the following
> email from Cron Daemon:
>
> [Mailman] Cron /usr/bin/python -S
> /usr/lib/mailman/cron/cull_bad_shunt
>
>
> Traceback (most recent call last):
>
> File "/usr/lib/mailman
Thank you. I did patch the admin.py file and I can see the changes.
However, if I go to the list subscribers, the link to the next group of
addresses takes me back to the main admin page.
I did notice that the URL includes < u'http:// > which I thought was
the problem that this was supposed
On 09/28/2016 11:04 AM, Christopher Adams wrote:
>
> Do I need to patch Mailman and then follow the process as I would for
> installing/upgrading Mailman ?
You could, but it isn't necessary.
> When I patch, should I be in the Mailman build/source directory and not
> in the current Mailman dire
I'm using Mailman v2.1.21 on openSUSE Leap 42.1 and received the following
email from Cron Daemon:
[Mailman] Cron /usr/bin/python -S
/usr/lib/mailman/cron/cull_bad_shunt
Traceback (most recent call last):
File "/usr/lib/mailman/cron/cull_bad_shunt", line 126, in
main()
File "/usr/
Thank you for the reply and the attached patch.
Do I need to patch Mailman and then follow the process as I would for
installing/upgrading Mailman ?
When I patch, should I be in the Mailman build/source directory and not in
the current Mailman directory ?
Would 'patch < admin.patch' work ?
Many
10 matches
Mail list logo