[Bug 1993037] Re: hardcoded wrong path to run-parts in cron-*.service

[Wladimir Mutel]

Indeed, I checked debianutils file lists in Debian stable, testing and even unstable, and found run-parts in /bin/ there.
In Ubuntu Jammy, however, debianutils are of version 5.5-1ubuntu2 , and in their changelog, we see :

debianutils (5.0-1) unstable; urgency=medium

  [ Tomas Pospisek ]
  * run-parts.8: document --debug flag introduced in commit 37596c61
  * run-parts.8: mention that run-parts runs parts sequentially

  [ Clint Adams ]
  * run-parts: Apply patch from Christoph Biedl to add --debug flag.
    closes: #243676.
  * Add missing newline to regexp build error, thanks to Christoph Biedl.
  * Remove tempfile.
  * Deprecate which.
  * Move run-parts to /usr/bin and installkernel to /usr/sbin.

 -- Clint Adams <clint at debian.org>  Tue, 17 Aug 2021 17:03:42 -0400

Same note we see in https://metadata.ftp-
master.debian.org/changelogs//main/d/debianutils/debianutils_5.7-0.3_changelog
, but a note about reverting these changes is seen nowhere.

-- 
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:
  hardcoded wrong path to run-parts in cron-*.service

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

Bug description:
  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