The ebuild edits the example configuration file to include: <spooldir>/var/spool/jabber/pymsn-t</spooldir> ewarn messages from ebuild: einfo "You also need to create a directory msn.yourdomain.com in" einfo "/var/spool/jabber/ and chown it to jabber:jabber." This last instruction would make me create /var/spool/jabber/msn.yourdomain.com/ while the configuration file expects /var/spool/jabber/pymsn-t/msn.yourdomain. com/. Reproducible: Always Steps to Reproduce: Expected Results: I can't tell from bug #98452 which of these that would be correct but they should atleast be consistent with eachother and all other jabber-base packages.
Fixed in portage thanks for reporting this one.
I also believe the directory was automatically created when I started pymsn-t. Before I started it I did configure it properly with the configuration file. The ewarn messages are still nice as upgrading instructions.
