REMINDER: System V to systemd unit migration

[Jan Kurik]

At the FESCo meeting on October 14th [1], it was decided that the time
has come to finally complete the migration away from System V init
scripts.

This email is a reminder about this Change, following the announcement
sent by Stephen Gallagher [2].
You might also want to check the list of possibly affected packages [2].

The branch of F24 from rawhide is currently scheduled on 2016-02-23.
As previously announced, any package that has not been migrated from
System V init scripts to systemd units before this date will be
retired from the Fedora package collection. Exceptions to this must be
requested by FESCo ticket no later than February 2nd.

[1] https://meetbot.fedoraproject.org/teams/fesco/fesco.2015-10-14-18.01.html
[2] bit.ly/1ZBEqhc

-- 
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: System V to systemd unit migration

[Zbigniew Jędrzejewski-Szmek]

On Wed, Oct 28, 2015 at 10:39:53PM +0100, Reindl Harald wrote:
> 
> 
> Am 28.10.2015 um 22:27 schrieb Tom Hughes:
> >On 28/10/15 19:47, Adam Jackson wrote:
> >
> >>As a quick audit (based on 'grep _initrddir' and 'grep _initddir' over
> >>a fairly recent checkout of the spec files in pkg git, and then some
> >>manual inspection) I think the following packages will be affected:
> >
> >...and initscripts for network and netconsole ;-)
> 
> if network.service (/etc/rc.d/init.d/network) goes away i consider
> after 20 releases so far plan a migration to whatever distribution
> or even operating system because it would be the same pain than
> migrate all the customized stuff inside Fedora
IMHO /etc/init.d/network is a good candidate for an exception...
The alternatives aren't there yet for various reasons.

There's always the possibility of repackaging it to be a script
called from a systemd unit, instead of using the sysv compat interface.
But it's just a big script anyway, and changing how it is called
seems to be work without much gain.

Zbyszek
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: System V to systemd unit migration

[Adam Jackson]

On Wed, 2015-10-28 at 14:12 -0400, Stephen Gallagher wrote:
> At the FESCo meeting on October 14th, it was decided that the time
> has come to finally complete the migration away from System V init
> scripts. What does this mean for you as a packager?
> 
> When we branch from Rawhide for Fedora 24 (currently scheduled for
> February 2nd, 2016), we will be immediately retiring any package in
> the Fedora collection that relies on a System V init script instead of
> a systemd unit file to start. We will consider reasonable requests to
> delay this action on a case-by-case basis for anyone who submits a
> ticket to FESCo no later than 23:59 UTC on January 12, 2016.

As a quick audit (based on 'grep _initrddir' and 'grep _initddir' over
a fairly recent checkout of the spec files in pkg git, and then some
manual inspection) I think the following packages will be affected:

athcool
bdii *
ceph *
cfengine
clement
dahdi-tools
dhcp_probe
dpm-dsi *
fts *
globus-gatekeeper *
globus-gridftp-server *
globus-scheduler-event-generator *
greylistd
imagefactory *
ip-sentinel
mysql-proxy *
ncid
nessus-core
nightview *
noip
nordugrid-arc *
nxtvepg
openscada
opentracker
orbited
Perlbal
perl-mogilefs-server
pnp4nagios *
popfile
psad
qpid-qmf *
RabbIT *
ris-linux
root *
roundup
sagator *
ser
sigul
smstools *
sys_basher *
tabled
tetrinetx
tmda
ulogd
vmpsd
voms *
Vuurmuur
vzctl
xtide
yum-utils *

At least ceph appears to have systemd support upstream already,
possibly others do too.  At least yum-utils only needs sysvinit scripts
for one particular subpackage.  Packages with a * are also built in
either RHEL7 or EPEL7.

Also, pdsh and w3c-markup-validator are calling sysinit-style "reload"
commands in scriptlets, so probably that's already broken.

- ajax
___
devel-announce mailing list
devel-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce

Re: System V to systemd unit migration

[Robert Scheck]

Hello Adam,

On Wed, 28 Oct 2015, Adam Jackson wrote:
> As a quick audit (based on 'grep _initrddir' and 'grep _initddir' over
> a fairly recent checkout of the spec files in pkg git, and then some
> manual inspection) I think the following packages will be affected:

your grep calls should include %{_sysconfdir}/rc.d/init.d/, too.


Greetings,
  Robert


pgpOR1RpHnhcE.pgp
Description: PGP signature
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

System V to systemd unit migration

[Stephen Gallagher]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

At the FESCo meeting on October 14th, it was ​decided that the time
has come to finally complete the migration away from System V init
scripts. What does this mean for you as a packager?

When we branch from Rawhide for Fedora 24 (currently ​scheduled for
February 2nd, 2016), we will be immediately retiring any package in
the Fedora collection that relies on a System V init script instead of
a systemd unit file to start. We will consider reasonable requests to
delay this action on a case-by-case basis for anyone who ​submits a
ticket to FESCo no later than 23:59 UTC on January 12, 2016.

There is no plan to remove System V compatibility from Fedora, due to
the necessity of supporting legacy third-party software. We are also
not making any changes at all to the EPEL project. EPEL packages may
continue to use System V init scripts (in the case of EPEL 5 and EPEL
6, there is no other option).

We will be going through the Wiki packaging documentation over the
next month and updating all related entries to reflect this change in
policy.

This will be the first such announcement. The Change Wrangler will be
sending additional reminders from now until February 2nd, so no one
will be surprised by this event.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlYxEAAACgkQeiVVYja6o6NmxwCeI7gSKCwmQ7AtBqoM3MoB8Q7a
SlgAniagJ8mrWWmr/BTqEyltF21FRbBd
=U6rs
-END PGP SIGNATURE-
___
devel-announce mailing list
devel-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

System V to systemd unit migration

[Stephen Gallagher]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

At the FESCo meeting on October 14th, it was ​decided that the time
has come to finally complete the migration away from System V init
scripts. What does this mean for you as a packager?

When we branch from Rawhide for Fedora 24 (currently ​scheduled for
February 2nd, 2016), we will be immediately retiring any package in
the Fedora collection that relies on a System V init script instead of
a systemd unit file to start. We will consider reasonable requests to
delay this action on a case-by-case basis for anyone who ​submits a
ticket to FESCo no later than 23:59 UTC on January 12, 2016.

There is no plan to remove System V compatibility from Fedora, due to
the necessity of supporting legacy third-party software. We are also
not making any changes at all to the EPEL project. EPEL packages may
continue to use System V init scripts (in the case of EPEL 5 and EPEL
6, there is no other option).

We will be going through the Wiki packaging documentation over the
next month and updating all related entries to reflect this change in
policy.

This will be the first such announcement. The Change Wrangler will be
sending additional reminders from now until February 2nd, so no one
will be surprised by this event.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlYxEAAACgkQeiVVYja6o6NmxwCeI7gSKCwmQ7AtBqoM3MoB8Q7a
SlgAniagJ8mrWWmr/BTqEyltF21FRbBd
=U6rs
-END PGP SIGNATURE-
___
devel-announce mailing list
devel-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce

Re: System V to systemd unit migration

[Stephen Gallagher]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 10/28/2015 03:54 PM, Richard Shaw wrote:
> On Wed, Oct 28, 2015 at 1:12 PM, Stephen Gallagher
> > wrote:
> 
> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
> 
> At the FESCo meeting on October 14th, it was ​decided that the
> time has come to finally complete the migration away from System V
> init scripts. What does this mean for you as a packager?
> 
> When we branch from Rawhide for Fedora 24 (currently ​scheduled
> for February 2nd, 2016), we will be immediately retiring any
> package in the Fedora collection that relies on a System V init
> script instead of a systemd unit file to start. We will consider
> reasonable requests to delay this action on a case-by-case basis
> for anyone who ​submits a ticket to FESCo no later than 23:59 UTC
> on January 12, 2016.
> 
> 
> Since we have some time between now and 2/2/16, would it be prudent
> to see if we could setup a tracker/blocker bug and file bugs
> against each package still shipping SysV init files?


As it happens, we already have such a thing:
https://bugzilla.redhat.com/show_bug.cgi?id=SysVtoSystemd

We *should* make sure it's up-to-date, however.

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlYxKh4ACgkQeiVVYja6o6MehACeN89Ya4PODnjpUm/+Eu9yYSDB
ztQAoIroUMSBV8re5ZiKOaMFLOKcDCMs
=hyCb
-END PGP SIGNATURE-
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: System V to systemd unit migration

[Ken Dreyer]

On Wed, Oct 28, 2015 at 1:47 PM, Adam Jackson  wrote:
> At least ceph appears to have systemd support upstream already,

Yep! We're waiting for Ceph upstream to release a stable version of
the 9.x series (codenamed "Infernalis"), and then we can ship this in
Rawhide.

I anticipate that Ceph upstream will ship the first stable release of
9.x within a month, so we should be well ahead of the Feb 2nd date.

- Ken
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: System V to systemd unit migration

[Richard Shaw]

On Wed, Oct 28, 2015 at 1:12 PM, Stephen Gallagher 
wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> At the FESCo meeting on October 14th, it was ​decided that the time
> has come to finally complete the migration away from System V init
> scripts. What does this mean for you as a packager?
>
> When we branch from Rawhide for Fedora 24 (currently ​scheduled for
> February 2nd, 2016), we will be immediately retiring any package in
> the Fedora collection that relies on a System V init script instead of
> a systemd unit file to start. We will consider reasonable requests to
> delay this action on a case-by-case basis for anyone who ​submits a
> ticket to FESCo no later than 23:59 UTC on January 12, 2016.


Since we have some time between now and 2/2/16, would it be prudent to see
if we could setup a tracker/blocker bug and file bugs against each package
still shipping SysV init files?

Thanks,
Richard
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: System V to systemd unit migration

[Adam Jackson]

On Wed, 2015-10-28 at 14:12 -0400, Stephen Gallagher wrote:
> At the FESCo meeting on October 14th, it was decided that the time
> has come to finally complete the migration away from System V init
> scripts. What does this mean for you as a packager?
> 
> When we branch from Rawhide for Fedora 24 (currently scheduled for
> February 2nd, 2016), we will be immediately retiring any package in
> the Fedora collection that relies on a System V init script instead of
> a systemd unit file to start. We will consider reasonable requests to
> delay this action on a case-by-case basis for anyone who submits a
> ticket to FESCo no later than 23:59 UTC on January 12, 2016.

As a quick audit (based on 'grep _initrddir' and 'grep _initddir' over
a fairly recent checkout of the spec files in pkg git, and then some
manual inspection) I think the following packages will be affected:

athcool
bdii *
ceph *
cfengine
clement
dahdi-tools
dhcp_probe
dpm-dsi *
fts *
globus-gatekeeper *
globus-gridftp-server *
globus-scheduler-event-generator *
greylistd
imagefactory *
ip-sentinel
mysql-proxy *
ncid
nessus-core
nightview *
noip
nordugrid-arc *
nxtvepg
openscada
opentracker
orbited
Perlbal
perl-mogilefs-server
pnp4nagios *
popfile
psad
qpid-qmf *
RabbIT *
ris-linux
root *
roundup
sagator *
ser
sigul
smstools *
sys_basher *
tabled
tetrinetx
tmda
ulogd
vmpsd
voms *
Vuurmuur
vzctl
xtide
yum-utils *

At least ceph appears to have systemd support upstream already,
possibly others do too.  At least yum-utils only needs sysvinit scripts
for one particular subpackage.  Packages with a * are also built in
either RHEL7 or EPEL7.

Also, pdsh and w3c-markup-validator are calling sysinit-style "reload"
commands in scriptlets, so probably that's already broken.

- ajax
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: System V to systemd unit migration

[Tom Hughes]

On 28/10/15 19:47, Adam Jackson wrote:


As a quick audit (based on 'grep _initrddir' and 'grep _initddir' over
a fairly recent checkout of the spec files in pkg git, and then some
manual inspection) I think the following packages will be affected:


...and initscripts for network and netconsole ;-)

Tom

--
Tom Hughes (t...@compton.nu)
http://compton.nu/
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: System V to systemd unit migration

[Reindl Harald]

Am 28.10.2015 um 22:27 schrieb Tom Hughes:

On 28/10/15 19:47, Adam Jackson wrote:


As a quick audit (based on 'grep _initrddir' and 'grep _initddir' over
a fairly recent checkout of the spec files in pkg git, and then some
manual inspection) I think the following packages will be affected:


...and initscripts for network and netconsole ;-)


if network.service (/etc/rc.d/init.d/network) goes away i consider after 
20 releases so far plan a migration to whatever distribution or even 
operating system because it would be the same pain than migrate all the 
customized stuff inside Fedora


static configured machines don't need anything else then 
ifup/ifdown/ifconfig and some oneshot-services for routings, vpn and 
what not else


that said from a machine with a network setup systemd-entworkd could not 
support and NM most likely also




signature.asc
Description: OpenPGP digital signature
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: System V to systemd unit migration

[Lennart Poettering]

On Wed, 28.10.15 14:12, Stephen Gallagher (sgall...@redhat.com) wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> At the FESCo meeting on October 14th, it was ​decided that the time
> has come to finally complete the migration away from System V init
> scripts. What does this mean for you as a packager?

Excellent!

Thank you very much for working towards this! I think it would be
great to ship without sysv scripts!

Thanks!

Lennart

-- 
Lennart Poettering, Red Hat
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct