I admit that I have some objections: In containers systemd is not available.

"You are not authorized to access bug #1115417."

Could someone give a clear rationale for this change?

hi,

This is coming from https://fate.suse.com/323635 basically, the reason behind this change is that cronie upstream development seems to be slowing down and new issues with it might mean we have to invest more resources in maintaining it while systemd is seeing a lot of activity these days and is well supported.

Michael Ströder (stroeder) - over 5 years ago

It seems I'm not allowed to login to fate.suse.com.

Michael Ströder (stroeder) - over 5 years ago

Would you mind if we proceed with upstream update request (see request #655316) until there is some clarification in bsc#1115417? You would have to rebase your change.

---

Rubén Torrero Marijnissen (rtorrero) - over 5 years ago

author

It shouldn't be a problem as most of the changes in this SR are related to systemd units and not so much to the upstream code itself.

I've move the bug to openSUSE to open it for reading. There is also a tracker bug for openSUSE only packages: https://bugzilla.opensuse.org/show_bug.cgi?id=1115430 See also https://lists.opensuse.org/opensuse-factory/2018-11/msg00157.html

Iow in general the distro is moving cron scripts to systemd timers. This is nothing specific to unbound. Please forward this change to Factory if it's technically correct.

Michael Ströder (stroeder) - over 5 years ago

Thanks. I've added my concerns as a comment in bsc#1115417.

---

Rubén Torrero Marijnissen (rtorrero) - over 5 years ago

author

I think you meant: https://bugzilla.opensuse.org/show_bug.cgi?id=1115430

@deadpoint, @stroeder: review reminder

I just realized I left out a dependency for cron in the unbound-anchor package. Sorry for that, I'll send a new request.