Bug 1116012

Summary:	Please convert SysV init scripts by firebird into native systemd services
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Franck Bui <fbui>
Component:	Other	Assignee:	Michal Kubeček <mkubecek>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	dimstar, opensusefactory
Version:	Current
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Franck Bui 2018-11-14 14:48:50 UTC

It would be great if the SysV init scrips shipped by this package could
be converted into systemd native services.

Indeed most packages shipped by openSUSE Factory switched to native
systemd unit files years ago and we plan to drop the obsolete/limited
SysV compat support in the future.

If this appears to be a big task, one quick way to solve it is to copy
and ship (as is) the .service unit wrappers generated automatically by
systemd-sysv-generator at boot. Indeed such wrappers are generated by
systemd in order to support SysV init scripts similarly to native
units.

You can see the content of a wrapper unit with:

 $ systemctl cat <sysvinit-script>.service

As you could see the wrapper unit simply calls the SysV script, which
should be moved out of /etc/init.d, probably in a directory owned by
your package.

In all cases we would be glad to provide any help if needed in this
task.

Thanks in advance.

Comment 1 Michal Kubeček 2018-11-19 09:29:30 UTC

To be honest, I don't see the point of doing such formal exercise just to
satisfy some check that we are "100% systemd pure distribution". And I'm
certainly not going to replace init scripts with actual systemd unit files
as I would not be able to maintain those.

I would also like to remind that when systemd proponents pushed it into
openSUSE, one of their arguments was "you don't have to do anything, the
init scripts will keep working". I did not really believe that and predicted
that it would be only matter of time before package maintainers are pushed into
switching from init scripts to systemd unit files. The answer was "no, that's
not going to happen".

Comment 2 Franck Bui 2018-11-19 09:41:34 UTC

(In reply to Michal Kubeček from comment #1)
> To be honest, I don't see the point of doing such formal exercise just to
> satisfy some check that we are "100% systemd pure distribution".

It's not about to be 100% systemd pure distro, it's about to convert the few remaining packages that still ships sysv init scripts that would force us to maintain this (deprecated) support forever. And you do that for no good reasons since you can *easily* achieve the conversion.

Sadly you're the first one who doesn't see the point...

Anyway you've been kindly reminded.

Comment 3 Michal Kubeček 2018-11-19 10:01:33 UTC

> Sadly you're the first one who doesn't see the point...

I see the point very well. The point is to break the (false) promise given
when systemd people still needed distributions to switch to systemd. I never
trusted they did really mean it and suspected it was only given to silence
the opposition. But that doesn't mean I won't request them to keep it.

> Anyway you've been kindly reminded.

I'm pretty sure distribution maintainers would be more than happy in assisting
you with either forcing the unit files into the package against my will or with
making distribution wide changes breaking packages which do not conform. But if
you do, you'll also need to find a new maintainer because I'm getting more and
more tired of all these annoying (and needless) new requirements in the name
of brave new systemd world - and this is where I'm going to draw the line.

Comment 4 Franck Bui 2020-12-01 08:24:29 UTC


*** This bug has been marked as a duplicate of bug 1179203 ***