I upgraded from 2.1.12-r1 to 2.1.13 and I previously had placed all my configuration options into Mailman/mm_cfg.py. Upon finishing the upgrade that file was completely replaced by the default from the package and my configuration was totally blown away. Looking at the ebuild it looks like it needs an additional section similiar to the two excerpted below but the new section needs to specifically look to see if there already is a config in the new default location and back that up as well at the very least. # Save the old config into the new package as CONFIG_PROTECT # doesn't work for this package. if [ -f ${ROOT}/var/mailman/Mailman/mm_cfg.py ]; then cp ${ROOT}/var/mailman/Mailman/mm_cfg.py \ ${D}/usr/local/mailman/Mailman/mm_cfg.py einfo "Your old config has been saved as mm_cfg.py" einfo "A new config has been installed as mm_cfg.dist" fi if [ -f ${ROOT}/home/mailman/Mailman/mm_cfg.py ]; then cp ${ROOT}/home/mailman/Mailman/mm_cfg.py \ ${D}/usr/local/mailman/Mailman/mm_cfg.py einfo "Your old config has been saved as mm_cfg.py" einfo "A new config has been installed as mm_cfg.py.dist" fi As this was a test installation (the 2.1.12-r1) the system was not yet functional so I don't know if it blew away important parts of test lists that I was just setting up. I've shown this to be repeatable as well and any reinstall of Mailman at least version 2.1.13 using the current ebuilds will cause mm_cfg.py to be wiped clean.
added in cvs
