Ran into this when updating from the stable Mailman 2.1.9 to the testing/unstable Mailman 2.1.9-r2... The docs say that installing Mailman by default installs to /usr/local/mailman. This is where my current install of 2.1.9 was installed - all of it. Took me a little while to figure out what happened... Reproducible: Always Steps to Reproduce: 1. Install Mailman 2.1.9-r2 2. Note the main program is installed in /usr/lib64/mailman instead of /usr/local/mailman 3. The following directories are installed in /var/lib/mailman: archives data lists locks logs qfiles spam Expected Results: According to the docs, it should have ALL been installed in /usr/local/mailman. I tried this on a test system - installing stable mailman 2.1.9 installs everything in /usr/local/mailman Uninstall 2.1.9, install 2.1.9-r2 - it installs in /usr/lib64/mailman, except for the aforementioned directories, which are installed in /var/lib/mailman. I'm still trying to get my web interface to work - and I get an error (!!) when trying to start mailman using /etc/init.d/mailman start, but it is apparently running, because it is working. To restart it (ie, to get it to see changes to mm_cfg.py) I have to execute the mailmanctl commands manually.
Excuse me, but this is a MAJOR issue, since it results in BREAKAGE. I agree it is easily fixed by simply updating the README - AND providing major warnings about what things are moved and where... and since this is an unstable ebuild, hopefully only people capable of figuring out what went wrong will be installing it, but... As it stands, anyone updating to this ebuild WILL experience breakage that they will then have to unravel themselves without any help from the docs.
*** Bug 204914 has been marked as a duplicate of this bug. ***
*** Bug 204931 has been marked as a duplicate of this bug. ***
docs are now changed. The big warning IS there (a couple of ewarn lines and an ebeep, there isn't much more I can do).
