I merged 7.4.1-2ubuntu1 yesterday. Based on Debian's changelog, it looks
like this bug is fixed now in the latest development release. If not,
please reopen.
** Changed in: logwatch (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member o
** Changed in: logwatch (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1281447
Title:
false positive in logwatch report
To manage notifications about
** Bug watch added: Debian Bug tracker #754211
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754211
** Also affects: logwatch (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754211
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: logwatch (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1281447
Title:
f
To my understanding it is normal behaviour that during boot the root filesystem
is first mounted ro and after it has passed some checks it gets remounted.
Logwatch seems to just to check the fstab line in the log file, see the error
option and report it as a false positive.
It is a false positive
