[Bug 1216947] Re: cron.daily/standard reports /tmp/lost+found missing

[Robie Basak]

> Can we get a newer version out in precise please?

No. Cherry-picking just the fix for this bug is the most we would do to
minimise risk to existing users. See
https://wiki.ubuntu.com/StableReleaseUpdates for rationale, policy and
procedure.

The maximum impact of this bug is that users get annoyed with extra
emails, right?

Precise will be end of life in five months, and this bug is fixed in all
newer releases. Is it really worth risking user regressions to fix
Precise now, given that all users affected have been affected for over
four years but haven't requested this change until now?

** Also affects: cron (Ubuntu Precise)
   Importance: Undecided
       Status: New

** Changed in: cron (Ubuntu Precise)
       Status: New => Triaged

** Changed in: cron (Ubuntu)
       Status: Confirmed => Fix Released

** Changed in: cron (Ubuntu Precise)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1216947

Title:
  cron.daily/standard reports /tmp/lost+found missing

Status in cron package in Ubuntu:
  Fix Released
Status in cron source package in Precise:
  Triaged

Bug description:
  If /tmp is a filesystem, /tmp/lost+found will be removed following
  each reboot.  This causes cron.daily/standard to report
  /tmp/lost+found is missing.

  Reporting as a bug because, apart from mounting /tmp as a filesystem
  in /etc/fstab, everything is left at default.

  I would expect default behaviour to be either:

  1. /etc/rcS does not delete lost+found if /tmp is a filesystem; or
  2. cron.daily/standard does not report missing lost+found for a filesystem mounted to /tmp

  This occurs on 3.0pl1-120ubuntu4.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1216947/+subscriptions