On 2017-04-20 12:41, Ruediger Meier wrote:
On Thursday 20 April 2017, Todd Rme wrote:
On Tue, Apr 18, 2017 at 7:07 AM, Carlos E. R.
Deleting the cronjob is not enough, because an update of the rpm reinstalls it.
When dealing with the issue of google chrome sometimes inexplicably deleting its own repositry, the issue seems to be around a cron job the rpm creates to install its repository. The solution someone came up with was to use AppArmor to block the cron job.
Yes, that was me. Another solution is another cronjob that deletes chrome cron job :-p I don't use that solution any longer because the chrome job has a chance to run earlier at least once.
But this seems to be a major workaround for what I would have guessed would be a simple task: disabling cron jobs. Is there really no way to override the cron jobs installed by an rpm?
You can disable all cron jobs of users. But this one is from root.
Note disabling cron is not enough because they also run an at daemon job right after installation. Years ago I've filed a bug at google to disable this aggressive behavior. But they never replied.
Have you tried to install chrome using "rpm --noscripts"?
Next chrome update will reinstall the file stored at the cron.daily directory. It is not a script run during installation. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)