Installing cyrus-imapd with ssl flag doesn't install the default SSL certificates. Reproducible: Always Steps to Reproduce: 1. emerge cyrus-imapd 2. ls /etc/ssl/cyrus 3. Actual Results: srv-smtp # ls /etc/ssl/cyrus ls: cannot access /etc/ssl/cyrus: No such file or directory resulting in: 127.000.000.001.39321-127.000.000.001.00143: A0002 STARTTLS 127.000.000.001.00143-127.000.000.001.39321: A0002 NO Error initializing TLS Mar 13 16:10:52 localhost imap[25697]: unable to get certificate from '/etc/apache2/ssl/server.crt' Mar 13 16:10:52 localhost imap[25697]: TLS server engine: cannot load cert/key data Mar 13 16:10:52 localhost imap[25697]: error initializing TLS Expected Results: srv-smtp ~ # ls /etc/ssl/cyrus/ server.crt server.csr server.key server.pem Patch enclosed: - create the user BEFORE using it - add the missing / for the ROOT directory.
Created attachment 146026 [details, diff] patch for correcting cyrus-imapd 2.3.9-r1 ebuild
Comment on attachment 146026 [details, diff] patch for correcting cyrus-imapd 2.3.9-r1 ebuild I really don't see how's this fixing anything??? - the user has already been created in pkg_setup(), this is just completely redundant in pkg_postinst() - there's no missing / anywhere, ${ROOT} already includes this
Attach a complete emerge log here instead and post emerge --info output; thanks.
Created attachment 146030 [details, diff] $ROOT slash problem Don't know, but it works... BTW: asl@citron /usr/portage/net-mail $ grep -r ROOT * lots with "${ROOT}"/ even in mailman, see the ChangeLog: 16 Feb 2005; Elfyn McBratney <beu@gentoo.org> mailman-2.1.5-r2.ebuild, mailman-2.1.5-r3.ebuild, mailman-2.1.5-r4.ebuild, mailman-2.1.6_beta1.ebuild: Add slash after ${ROOT} in pkg_config. Anyway, the user is created before, so new patch reflecting this.
Hmm, it works on another machine, so I tried reinstalling it and now it does work. I don't get it, anyhow, marking as invalid (well, the redundant enewuser is still here, though). Sorry for the inconvenience.
(In reply to comment #5) > Hmm, it works on another machine, so I tried reinstalling it and now it does > work. > > I don't get it, anyhow, marking as invalid (well, the redundant enewuser is > still here, though). i just removed the redundant enewuser call, thanks for reporting! > Sorry for the inconvenience. No worries ;)