During dist upgrade from 8.10 to 9.04 with mailman got exit status 1

[Craig Van Degrift]

Binary package hint: mailman

Error
Could not install
/var/cache/apt/archives/mailman_1%3a2.1.12-1_i386.deb
The upgrade will continue but the ... mailman package may be in a not working state.

subprocess pre-installation script returned error exit status 1

The Details report suggests two problems:

/var/lib/mailman/Mailman/Utils.py:32: DeprecationWarning: the sha module is deprecated; use the hashlib module instead import sha

I fixed this in several files but still had a different error:

File "/usr/lib/python2.6/mailbox.py", line 19, in import email.message ImportError: No module named message

It appears that there are two email directories, one provided by Python and one by the earlier version of Mailman and
the earlier version has email.Message while the Python one has email.message. The search path seems mixed up.

[Chuck Short (zulcss)]

Thanks for the reporting the bug, I was wondering if this is still a problem for you?

Thanks
chuck.

[Craig Van Degrift (craig-yosemitefoothills)]

Chuck,

After seeing no response to my bug report, I concluded that the problem was a
serious one that must be well known. I think that mailman was updated to use
python version 3.0 while Kubuntu was was still using 2.6. I decided to simply
run my small mail server operation by hand and wait until kubuntu 9.10 when I
assume the problem will be resolved. So, for now, I am no longer using
mailman.

Craig

On Wednesday 09 September 2009 11:29:55 Chuck Short wrote:
> Thanks for the reporting the bug, I was wondering if this is still a
> problem for you?
>
> Thanks
> chuck.
>
> ** Changed in: mailman (Ubuntu)
> Status: New => Incomplete

[Chuck Short (zulcss)]

Closing as per above comment.

Regards
chuck

[AlainKnaff (kubuntu-misc)]

Chuck, the comment you replied to didn't really confirm that the problem was solved. More to the contrary, the problem still exists, and even was so bad that Craig gave up on it and decided to just wait for the next version...

... which eventually turned out to be as broken as 9.04 because nobody would fix this bug as it was marked invalid.

This is still a problem while upgrading from 8.04 to 10.04 .

These are consecutive LTS versions, so this upgrade path should be feasible.