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

[Steve Langasek]

Ok.  The Ubuntu position is that ubuntu-minimal is the package that
defines the smallest system considered Ubuntu.  If you don't have
ubuntu-minimal installed, you have a pile of packages, but not an Ubuntu
system that we can provide support for.

It's impressive that you had a system that has been working continuously
without ubuntu-minimal since 2008, I'm glad it's worked for you so far.
But the resolution of this bug is that you should install the ubuntu-
minimal package.

We will not add additional dependencies on the usrmerge package in an
already-released LTS.

Also, if when you say "upgrade from Debian to Ubuntu" you mean cross-
grading an existing Debian system, this is not a supported Ubuntu
installation path, but if you happen to know whether you followed a
cross-grading guide somewhere that fails to mention you should install
ubuntu-minimal, I would try to get that guide updated so other users
don't trip on such problems.

** Changed in: debianutils (Ubuntu)
       Status: Incomplete => Won't Fix

** Changed in: systemd-cron (Ubuntu)
       Status: New => Won't Fix

-- 
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:
  Won't Fix
Status in systemd-cron package in Ubuntu:
  Won't Fix

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