Comment 14 for bug 1836475

> Sorry, I should have communicated this better.

> With the proposed patch for Focal, users who have customised the file in /etc/cron.* (eg. by
> removing it) won't have that customisation transferred to the systemd timer. This needs
> consideration, so we're removing it from the SRU so as not to block the SRU for bug 1901627.

Would it be sufficient to add some logic to the postinst disabling the new systemd timer if the existing cron-job didn't exist? Or add a warning message in the event that the existing cron-job didn't match some hash of a default?

I'm keen to try and avoid handling any more complex (arbitrary) customisations :)