Description of problem: Installation takes place but displays an error when complete. This applies to both 2.1.23 in cauldron and 2.1.20 in mga5. No such list "mailman" warning: %post(mailman-2.1.20-2.mga5.x86_64) scriptlet failed, exit status 1 ERROR: 'script' failed for mailman-2.1.20-2.mga5 There is also an earlier error message: Bad owner email address: root@box - owner addresses need to be fully-qualified names like "owner@example.com", not just "owner". Version-Release number of selected component (if applicable): mailman-2.1.23-1.mga6 (cauldron) mailman-2.1.20-2.mga5 How reproducible: sudo urpmi mailman Steps to Reproduce: 1. sudo urpmi mailman 2. 3.
Assigning to all packagers collectively, since there is no registered maintainer for this package
CC: (none) => guillomovitch, marja11, olavAssignee: bugsquad => pkg-bugs
FWIW: I think this comment in the spec file is relevant to this bug. "Post-installation script attempts first to integrate mailman aliases file with existing mail aliases. Then the server-wide 'mailman' list is automatically created, with root@hostname as admin, and a randomly generated password. This list is configured with generic default values, but its configuration should be reviewed before usage. The password is available in the notification message sent by mailman upon list creation, and is also used as the site password. The mailman service has to be started, and the SMTP server has to be running for the message to be correctly delivered." When %post was written it appears to assume a fully configured server including host and domain names, smtp via postfix or perhaps sendmail, and probably dns. If these are not the case it appears to result in this post install scriptlet error. I have not seen the aliases added to postfix aliases automatically and have not seen any evidence of the mailman list which is attempted. The system wide random password which is generated is thus also never sent to the user. It would appear to me that it might be better to inform the user that these steps need to be taken (thus educating them of the fact if they do not already know) rather than to take steps out of view with the user never knowing. But I'm new here so perhaps more experienced folks know better. That said, I would be happy to attempt these changes if it is the consensus that they would be good.
You are perfectly right: a good post-installation procedure for a sysadmin would be a safer option than this automation attempt that is known to fail in multiple cases. As the package doesn't have any maintainer, feel free to proceed yourself.
I have a fix pending to address this (so no one wastes time). Luigi12 wants me to have commit rights before the proposed fix is pushed.
Have pushed updates for both cauldron and mga5 to fix the post installation scriptlet error and a couple of other bugs. Also found that this bug is actually a duplicate of https://bugs.mageia.org/show_bug.cgi?id=8759. I will use that bug for the fix and to submit to QA. *** This bug has been marked as a duplicate of bug 8759 ***
Status: NEW => RESOLVEDResolution: (none) => DUPLICATE