If you want to track current logcheck development more closely, consider using madduck's test builds. Here's how:
# cat <<_eof >> /etc/apt/sources.list deb http://debian.madduck.net/repo sid main _eof # cat <<_eof >> /etc/apt/preferences Package: * Pin: release a=unstable,o=madduck Pin-Priority: 50 Package: logcheck Pin: release a=unstable,o=madduck Pin-Priority: 600 Package: logcheck-database Pin: release a=unstable,o=madduck Pin-Priority: 600 Package: logtail Pin: release a=unstable,o=madduck Pin-Priority: 600 _eof # apt-get update # apt-get upgrade
Note that you may already have pins for unstable, in which case you do not necessarily need the first stanza.
I also provide backports versioned to integrate nicely with the regular backports.org logcheck packages. Just s/unstable/sarge-backports/g in all of the above instructions, which are then compatible with (and even identical to) the backports instructions: you'll always get the latest package, but when there's an "official" backport, it is favoured over the test builds.