Bug#511037: Looks very similar to that last one ...

2009-01-12 Thread Jason Long
dkimsign is not called by dkimproxy, so it is safe to rename it, omit it from the package, or put it in a different location. In the future, dkimsign and dkimverify will probably not be installed to $bindir. Jason -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a sub

Bug#511037: Looks very similar to that last one ...

2009-01-09 Thread Thomas Goirand
This is in reference to: http://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no&bug=511037 I'm adding the upstream author of dkimproxy for this bug. How can subscribe an email address to all bugs of a package? It would be nice if Jason was receiving the messages. This time this might have more

Bug#511037: Looks very similar to that last one ...

2009-01-09 Thread Scott Kitterman
I did go ahead and check and the only file name conflicts are: /usr/share/man/man1/dkimsign.1.gz usr/bin/dkimsign So this should be the last time we have to do this. At a glance, it appears similar to the last one. Are you willing to rename the script in dkimproxy again? Scott K signature.