Bug 697535

Summary:	The old SysV initscript should be packaged into subpackage when replaced with systemd one
Product:	[Fedora] Fedora	Reporter:	Jóhann B. Guðmundsson <johannbg>
Component:	initscripts	Assignee:	Bill Nottingham <notting>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	15	CC:	iarlyy, jonathan, notting, plautrba, rvokal
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-04-18 15:14:06 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jóhann B. Guðmundsson 2011-04-18 14:33:05 UTC

Description of problem:

The old SysV initscript should be package into seperate subpackage when replaced with a native systemd one to avoid confusion amongs end users since systemd will use the native systemd service file when it exist by default thus rendering the old sysv obsolete and keeping it around will only confuse users that for one reason or another are editing the sysv init script.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Bill Nottingham 2011-04-18 15:14:06 UTC

... Don't have any of those here.

Comment 2 Bill Nottingham 2011-04-18 16:02:17 UTC

Also, that's a REALLY BAD idea for making upgrades sane with respect to migrating service state. I'm surprised you think we should do this.

Comment 3 Jóhann B. Guðmundsson 2011-04-18 16:36:25 UTC

If i'm not mistaken then users need to manually preserve service state. 

From https://fedoraproject.org/wiki/User:Toshio/Systemd_scriptlet_options

# Save the current service runlevel info
# User must manually run systemd-sysv-convert --apply httpd
# to migrate them to systemd targets

so what's the problem with updating with/usr/bin/systemd-sysv-convert --save $service and then remove the old sysv script and have it packed seperatly since, since end users must manually run systemd-sysv-convert --apply $service to migrate the service state? 

I'm not following your reasoning on why y

Comment 4 Jóhann B. Guðmundsson 2011-04-18 16:37:46 UTC

Dam enter button 

I'm not following why your are so surpriced that I suggest we should do this.

Comment 5 Jóhann B. Guðmundsson 2011-04-18 17:33:04 UTC

(In reply to comment #1)
> ... Don't have any of those here.

We have

/etc/init.d/single 

which is provided by initscripts 

And we also have

/lib/systemd/system/single.service

Which is provided by systemd-units and gets picked up and used by systemd 
( which is the reason I filed this bug in the first place )

So what's the plan here between you and Lennart?

Comment 6 Bill Nottingham 2011-04-18 18:00:45 UTC

(In reply to comment #3)
> If i'm not mistaken then users need to manually preserve service state. 
> 
> From https://fedoraproject.org/wiki/User:Toshio/Systemd_scriptlet_options

Hadn't seen these guidelines yet - that alleviates it somewhat. https://fedorahosted.org/fpc/ticket/31#comment:37 is most of my reasoning - any time a SysV script moves from package A to package B, it greatly complicates the state tracking. Hence, unless you want to explicitly disavow keeping consistent state, it's best to keep it in the same package and deal with the consequences there.

With respect to 'single', that's not a service that we support administrator overrides of in SysV, so it's less of a concern with state tracking. I'll move it to -legacy in any case - fixed in git commit b4bdede.