update exits at this point, but the next time it is run, the error does not
appear any more (- I have to run 'update' three times to get rid of all these
errors). These errors always appear, when 'update' is run after MM 2.1.2 has
been used.
OK. You have done with update to 2.1.5.
Hi,
Frank Thommen wrote:
Hello list members,
while updating MM from 2.1.2 to 2.1.5, the process of updating gets
stucked at one specific maillist. I added a 'print mlist' in 'def
...and here the process waits/loops forever (at least more then three
hours...). I ^C-stopped the update several
Hi
...and here the process waits/loops forever (at least more then three
hours...). I ^C-stopped the update several times, but it gets always
stucked at the same list.
Examin the locks directory if there are lock files remained before
executing bin/update. Make sure you stop qrunner and
update exits at this point, but the next time it is run, the error does not
appear any more (- I have to run 'update' three times to get rid of all these
errors). These errors always appear, when 'update' is run after MM 2.1.2 has
been used.
OK. You have done with update to 2.1.5. Don't go back
Hello list members,
while updating MM from 2.1.2 to 2.1.5, the process of updating gets
stucked at one specific maillist. I added a 'print mlist' in 'def
update_pending()' after
'for listname in Utils.list_names():
mlist = MailList.MailList(listname)'
to know where it happens:
#
