control: reassign -1 dh-systemd Am 05.01.2015 um 14:52 schrieb Wolodja Wentland: > Package: systemd > Version: 215-8 > Severity: important > > Dear Maintainer, > > services that have explicitly been disabled in sysvinit with "update-rc.d > disable $SERVICE" are enabled/started in systemd after the transition. This > requires users to keep track of the service status before the > upgrade/transition > and might cause serious problems if service that weren't supposed to run are > started unintentionally.
This needs a clarification: if a package ships only a SysV init script, the enabled/disabled state is respected by systemd. I think what Wolodja wanted to say is, that if a package starts shipping a native systemd service file (alongside the SysV init script), the state of this systemd service is not based on the state of the SysV init script, but rather whatever the package default is. > If this cannot be solved technically then it would probably make sense to > reassign this bug to release-notes and warn users about this behaviour so that > they can take appropriate actions. It would, in that case, still be unclear > how > users could prevent services from being started though. I don't think there is anything that can be done in systemd about this. This would have to be dealt with in the maintainer scripts of the individual packages. dh-systemd *might* help with this, but since we are lacking basic functionality like [1], it seems unlikely that we find a clean and automated solution for this. Michael [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705254 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
