During the build the following error is issued: You have a known bad version of maildrop (1.0). It is buggy and doesn't work! However, the emerge continues and tries to install the non-built qmail-scanner-queue.pl leaving a *borked* installation. See URL for a details about the error. Sadly it seems like qmail-scanner ./configure doesn't return an non-zero exit code. This issue has been reported upstream and a fix is scheduled for the next release. Meanwhile I think a simple patch should be applied or block against maildrop-2.1.0
Created attachment 193252 [details, diff] Sample patch
Also, this affects all versions of qmail-scanner in tree.
What makes this particularly insidious is that dies silently, instantly turning your mail server into a zombie. Seems to me we've seen similar problems like this before with this package. Would adding a sanity check to the ebuild (qmail-scanner-queue.pl has a file size > 0) be within the guidelines? In the mean time, can we please gets this pushed through.
*** Bug 273583 has been marked as a duplicate of this bug. ***
Fixed in portage. Thanks
I have similar problem with on amd64 [ebuild R ] mail-filter/maildrop-2.2.0 USE="berkdb gdbm mysql -authlib -debug -fam -ldap -postgres" 0 kB [ebuild R ] mail-filter/qmail-scanner-2.05 USE="clamav spamassassin" 0 kB downgrade to maildrop-2.0.4 help me
It's not fixed for qmail-scanner-2.05 yet I'm afraid. The same problem with [ebuild R ] mail-filter/maildrop-2.2.0 USE="berkdb gdbm ldap mysql -authlib -debug -fam -postgres" 0 kB [ebuild R ] mail-filter/qmail-scanner-2.05 USE="clamav spamassassin" 0 kB Anyway maildrop.2.1.0.patch works.
The attached patch was applied by upstream in 2.07. But instead of adding the patch to 2.05 wouldn't it be better to stabilize 2.08?