Bug#560186: The bug is still there...

2010-02-03 Thread Micha vor dem Berge
Hi, > I'd just fixed this bug on SF - it was triggered when a (Debian) host > didn't have a stock Debian kernel installed. SVN HEAD contains a > apt-dater-host script which fixes this issue. it works for me with the recent svn version of apt-dater-host and apt-dater 0.8.1+svn450-1 from debian s

Bug#560186: The bug is still there...

2010-01-30 Thread Thomas Liske
Hi Micha, Micha vor dem Berge schrieb: Hi all, I followed the discussion about this bug, updated apt-dater and apt-dater-host to version 0.8.1+svn450-1 (available in sid) and still get the hosts placed in "unknown" no matter which status they should have (updates pending or up to date or whatev

Bug#560186: The bug is still there...

2010-01-28 Thread Patrick Matthäi
On 28.01.2010 10:54, Micha vor dem Berge wrote: Hi all, I followed the discussion about this bug, updated apt-dater and apt-dater-host to version 0.8.1+svn450-1 (available in sid) and still get the hosts placed in "unknown" no matter which status they should have (updates pending or up to date o

Bug#560186: The bug is still there...

2010-01-28 Thread Micha vor dem Berge
Hi all, I followed the discussion about this bug, updated apt-dater and apt-dater-host to version 0.8.1+svn450-1 (available in sid) and still get the hosts placed in "unknown" no matter which status they should have (updates pending or up to date or whatever). If you look at the project bug track