This one time, at band camp, Micha Lenk said: > This Bug is still not fixed for me, because there is no sendmail but > nullmailer on my system. > > Wouldn't it be better not to detect sendmail's version via command line > but from any header inclusion?
I have supplied /path/to/sendmail to configure, as it's known on Debian systems. I have also patched clamav-milter.c so that if sendmail's version is undefined previously, it will be defined as the version currently in Debian. > The attached patch takes the version of the package libmilter-dev as the > version of sendmail. Since libmilter-dev is in clamav's build-deps this > should provide a more reliable way of detecting the sendmail version - > even if it's an ugly hack too. :) > +dpkg -s libmilter-dev | sed -n '/^Version:/s/-[^-]*$//p' [EMAIL PROTECTED]:~/Debian/clamav/0.87/clamav-0.87$ ./configure --help | grep sendmail --with-sendmail=PATH specify location of Sendmail binary (default=auto find) So that patch won't work - it will give configure a path to the binary 8.13.5-1, which I'm having trouble imaging exists on most systems :) Let me look at what went wrong ... I don't see it. In my local tree, the patch to supply a sendmail version is there. Checking the buildd logs, I see that none of the build daemons had this problem. Does the build actually fail for you, or do you just see configure generate a warning? If it's just a configure warning, but the build continues, then there is no problem. If you are actually getting failure to build from this, then there is something to investigate. Take care, -- ----------------------------------------------------------------- | ,''`. Stephen Gran | | : :' : [EMAIL PROTECTED] | | `. `' Debian user, admin, and developer | | `- http://www.debian.org | -----------------------------------------------------------------
signature.asc
Description: Digital signature
