Hi Tiago, The fix you are using for 524169 is broken, because you now call /usr/bin/bsd-mailx, but this does not necessarily exist. See: Depends: bsd-mailx | mailutils
How about making apticron compatible to all three mailx implementations currently in debian again? The attached (untested) patch could serve as an inspiration... Regards, Nis
--- apticron 2009-05-02 16:08:11.000000000 +0200 +++ apticron.modified 2009-05-02 16:04:13.000000000 +0200 @@ -143,6 +143,19 @@ # do the upgrade downloads /usr/bin/apt-get -qq -d --allow-unauthenticated --force-yes dist-upgrade >& /dev/null + # different mailx implementations accept different options: make + # sure we are using proper charset declarations + if [ -x "/usr/bin/bsd-mailx" ]; then + # bsd-mailx needs -a <...> + MAILX="/usr/bin/bsd-mailx -a \"Content-type: text/plain; charset=UTF-8\"" + elif [ -x "/usr/bin/heirloom-mailx" ]; then + # heirloom-mailx detects charset correctly by itself + MAILX="/usr/bin/heirloom-mailx" + else + # assume mailutils-mailx, which needs -a <...> + MAILX="/usr/bin/mailx -a \"Content-type: text/plain; charset=UTF-8\"" + fi + ( /bin/cat <<EOF apticron report [`/bin/date -R`] @@ -237,7 +250,7 @@ apticron EOF - ) 2>&1 | /usr/bin/bsd-mailx -a "Content-type: text/plain; charset=UTF-8" -s "$DISTRIB_ID package updates on $SYSTEM" $EMAIL + ) 2>&1 | $MAILX -s "$DISTRIB_ID package updates on $SYSTEM" $EMAIL fi
