Guys, please take care to delete the mailman-users address if you're
using reply-to-all on this thread. Progress on MM3 is undoubtedly of
interest to MM-users, but the gory details of broken tests probably is
not
Reply-to-munging-still-considered-harmful-ly y'rs
P.S. Maybe I should revive th
On Feb 26, 2014, at 02:45 PM, Stephen J. Turnbull wrote:
> > I have no idea what to do next,
This is clearly a bug, although I think it's relatively recent, so it might be
worth seeing if earlier revisions avoid the problem. Yes, I can reproduce it.
The interesting thing is that the test is in
On Wed, Feb 26, 2014 at 3:13 AM, Nicolas Karageuzian
wrote:
> I encountered db lock using sqlite with mailman3 and tools.
> Switching to postgres avoid the db locking states.
> Maybe you should explore that way.
I'll try that.
> Hyperkitty moved to github so the lp ref is quite out of date for t
On Wed, Feb 26, 2014 at 12:45 AM, Stephen J. Turnbull
wrote:
> Tom Browder writes:
...
> Actually, I do have a couple of ideas. First, you should always
> report the whole error trace (if you think that's ugly in an email,
...
Thanks, Steve, for the good advice.
-Tom
---
