Hi Christian
Yes, you have correctly identified the diff.
Just to make sure I understand correctly, you want me to mark the *Mailman*
bug that I linked to as New again?
I don't want to get yelled at by the GNU Mailman people if I'm doing the
wrong thing :)
Regards
Philip
On 18 November 2016
Thanks for your help with this, Christian. Very much appreciated.
Regards
Philip
On 18 November 2016 at 09:57, Christian Ehrhardt <
christian.ehrha...@canonical.com> wrote:
>
> On Fri, Nov 18, 2016 at 10:07 AM, Philip Colmer
> wrote:
>
>> Just to make sure I understand correctly, you want me
On Fri, Nov 18, 2016 at 10:07 AM, Philip Colmer
wrote:
> Just to make sure I understand correctly, you want me to mark the
> *Mailman* bug that I linked to as New again?
>
I'll try to clarify.
The linked bug is a mailman bug you are right on that.
What has to be done is to add an Ubuntu Task for
On Thu, Nov 17, 2016 at 5:18 PM, Philip Colmer
wrote:
> It looks as if https://bugs.launchpad.net/mailman/+bug/1251495 has not
> been applied to the ubuntu package for Mailman. I have checked both
> 1:2.1.16-2ubuntu0.2 and 1:2.1.16-2, and Tagger.py has the bug in it.
> Hand-altering the file to i
Hi
It looks as if https://bugs.launchpad.net/mailman/+bug/1251495 has not been
applied to the ubuntu package for Mailman. I have checked both
1:2.1.16-2ubuntu0.2 and 1:2.1.16-2, and Tagger.py has the bug in it.
Hand-altering the file to implement the fix does correct the problem.
This is a high i
