Systemd upgrades and user-selected auto-start
-----BEGIN PGP SIGNED MESSAGE-----
On 09/20/2011 09:04 AM, Stephen Gallagher wrote:
> Our current scriptlets for systemd result in an unacceptable
> upgrade case. Specifically, it reverts all services to their
> default enabled/disabled status. We should allow packagers to
> include scripts that keep the user-selected auto-start between
As stated before, we argued about this, but this is what we had to
* Lots of packages had services that were enabled by default, but
should not have been
* Certain services used to need to be enabled by default in a
pre-systemd universe, but no longer need to be.
* There is no way to differentiate between a service which is on
because it was set that way by the package and on because the user
made a conscious choice to set it that way.
* Runlevels and ordering in the SysV universe don't have exact
mappings in the systemd model, and we have to assume that it is
possible that both have been customized by the user.
So, for Fedora 16, we decided to force a clean reset of the proper
defaults for services, as decided by FESCo, and:
* Save a copy of the runlevel and priority status of the service being
migrated to systemd
* Provide a simple tool (/usr/bin/systemd-sysv-convert in
systemd-sysv, 150 lines of python) that can take the saved service
status and make an attempt to convert it to systemd, so that if the
user wishes to view or restore the same settings they had prior to the
upgrade, they can do so.
I'm not terribly interested in revisiting this painful discussion, and
to be honest, just want to move past it.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
packaging mailing list