> 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 :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836475 Title: [SRU] update-notifier-common weekly cron job runs at the same time for all computers across the globe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1836475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
