[Bug 1993037] Re: Ubuntu 22.04, debianutils moved run-parts into /usr/bin, breaking systemd-cron in the course

[Lukas Märdian]

Is this a clean installation of Ubuntu 22.04, or have you been upgrading
your system from an older installation?

I wonder if you have the `usrmerge` package installed correctly?

** Changed in: debianutils (Ubuntu)
       Status: New => Incomplete

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

Title:
  Ubuntu 22.04, debianutils moved run-parts into /usr/bin, breaking
  systemd-cron in the course

Status in debianutils package in Ubuntu:
  Incomplete
Status in systemd-cron package in Ubuntu:
  New

Bug description:
  (Found in Ubuntu 22.04 LTS)
  package debianutils keeps run-parts executable in /usr/bin/
  while package systemd-cron tries to find it in /bin/

  $ which run-parts
  /usr/bin/run-parts

  $ dpkg -S `which run-parts`
  debianutils: /usr/bin/run-parts

  $ grep =/bin/run /lib/systemd/system/cron*
  /lib/systemd/system/cron-daily.service:ExecStart=/bin/run-parts --report /etc/cron.daily
  /lib/systemd/system/cron-hourly.service:ExecStart=/bin/run-parts --report /etc/cron.hourly
  /lib/systemd/system/cron-monthly.service:ExecStart=/bin/run-parts --report /etc/cron.monthly
  /lib/systemd/system/cron-weekly.service:ExecStart=/bin/run-parts --report /etc/cron.weekly

  Because of that, cron-daily.serice gets info "failed" state soon after
  system reboot.

  Please resolve the problem to make systemd-cron more usable.
  Thanks in advance for your help.

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