The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: cron (Ubuntu Precise)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
> 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 annoy
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cron (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/1216947
Title:
cron.
@racb yes, the lost+found checking was removed in cron 3.0pl1-123, but
the latest available in precise is 3.0pl1-120:
http://packages.ubuntu.com/precise-updates/cron
Can we get a newer version out in precise please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
cron 3.0pl1-123 has this changelog entry:
* debian/standard.daily: Apply patch from Steve Allison to prevent checking
two times the same filesystem. This prevents bogus warnings about missing
lost+found in schroot bind mounts (Closes: #660879)
I'm also unable to find /etc/cron.daily/s
Sorry, wrong changelog entry. The one I meant was:
* debian/cron.default, debian/standard.daily, debian/rules: Remove
the lost+found check as this is no longer required and causes
issues with some filesystems (e.g. bind mounts, locally mounted USB
drives). Additionally, in some files
