[Note: This email was originally sent on 28.7.2005, but it might have got
lost because it didn't appear on bugs.debian.org and the reporter didn't
answer up to now.]
I saw this problem on a server with the Sarge version, but I was using my
unstable
desktop to fill the bug report.
That explains all. However, it's always better if you write the exact
version as shown by the output of dpkg -l packagename.
I will try, but none of our server is running unstable, so I will test that on
my
desktop and I am not sure to obtain the same behaviour.
You should be able to just grab the package from unstable and install it on
stable, because there are no differences concerning logwatch. The only thing
you need to take care of: If you want to go back to 5.2.2-5, you need to
save the /usr/share/doc/logwatch/examples/clean_config_files.sh script from
6.1.2-1, to remove the unneeded configuration files. Otherwise logwatch will
complain.
Willi
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
