On Fri, Dec 22, Ken Schneider - Factory wrote:
I made no such assumption. I wondered why 'any' SysV code would need to be run on a system without SysV installed.
It does not try to run it, it looks during update, if there is a SysV init script from the old package, and if that configuration needs to be migrated to systemd. Make a fresh installation and you want see that message. Make a second update, and you should not see that message, too.
Better would be (if possible) for the packager to not have any SysV scripts be run at all if SysV is not installed.
Which is the case. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org