Re: [Mailman-Users] bin/upgrade has been broken since 2.1.5 (orpossibly longer)

2008-09-30 Thread Knut Auvor Grythe
On Fri, Sep 19, 2008 at 07:46:25AM -0500, Barry Finkel wrote: >> This week, when attempting to upgrade further to Ubuntu Hardy, with >> Mailman 2.1.9, the upgrade script crashed as soon as it reached one of >> these lists, without releasing the lock. The attached patch is what I >> used to be able

Re: [Mailman-Users] bin/upgrade has been broken since2.1.5(orpossibly longer)

2008-09-19 Thread Knut Auvor Grythe
On Fri, Sep 19, 2008 at 09:32:18AM -0700, Mark Sapiro wrote: Now, I could probably have recovered in some other way, but that's because I know python. Not all mailman users do, and I suspect they would have severe difficulties recovering from such a situation. >>> >>> The recovery i

Re: [Mailman-Users] bin/upgrade has been broken since 2.1.5(orpossibly longer)

2008-09-19 Thread Knut Auvor Grythe
On Fri, Sep 19, 2008 at 08:40:32AM -0700, Mark Sapiro wrote: >> Now, I could probably have recovered in some other way, but that's >> because I know python. Not all mailman users do, and I suspect they >> would have severe difficulties recovering from such a situation. > > The recovery is somethin

Re: [Mailman-Users] bin/upgrade has been broken since 2.1.5 (orpossibly longer)

2008-09-19 Thread Knut Auvor Grythe
On Thu, Sep 18, 2008 at 09:28:32PM -0700, Mark Sapiro wrote: > I don't see the need to apply the part of the patch that recovers from > the incorect migration. Anyone who migrates with outstanding > subscription approval or held message requests from pre 2.1a4 to > Mailman through 2.1.11 will encou

[Mailman-Users] bin/upgrade has been broken since 2.1.5 (or possibly longer)

2008-09-18 Thread Knut Auvor Grythe
ith a ValueError, since an info typle is not 2 elements long. I think it would be very nice to have this fixed in 2.1.11. But even if that doesn't happen I thought I should notify people about the problem, so they know what to do if their u