Hi,
On 09/28/2012 05:03 AM, R. Tolga Korkunckaya wrote:
Severity: grave
Justification: renders package unusable
I can't agree that this "renders package unusable". I've been using
dkimproxy in hundreds of servers without problem. I don't think this is
an RC bug (eg: severity normal would be more appropriate).
init script of Debian package of dkimproxy do not parse/read
/etc/dkimproxy/dkimproxy_out.conf to override default settings,
it reads /etc/default/dkimproxy file only. However, this is not
written in Debian.README file of the package.
In dkimproxy docs these overrides are addressed to the
/etc/dkimproxy/dkimproxy_in.conf and /etc/dkimproxy/dkimproxyoutn.conf
I believe the problem you are facing is that the init script
uses --conf_file ${DKOUT_CONF} when it should really be using:
--conf_file=${DKOUT_CONF} (eg = sign instead of space). This has already
been fixed in the SID version, only the stable version of this package
doesn't have the fix, but it certainly does not "renders package unusable".
Cheers,
Thomas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
