tags 715267 + wontfix thanks Following up on the discussion we had between Stefan, Michael S. and me, I'm marking the bug as wontfix. For completeness sake I'm copying the relevant parts
> d/ Most importantly, I don't think we actually want to use dh-systemd. > This generates code to > - start/restart wpasupplicant on installation and upgrades > - enable the wpa_supplicant.service and hooks it up in multi-user.target > > I don't think we should start/restart wpasupplicant on upgrades, as most > of the time it will be under control of either ifupdown or > NetworkManager and this would potentially break the network connection. > > Also, unconditionally starting the service on boot via multi-user.target > doesn't seem like a good idea to me, this might e.g. conflict with > wpa_supplicant being started via ifupdown. > and > We *should* continute to ship the .service files, this is important, so > D-Bus activation works properly under systemd (NM e.g. relies on D-Bus > activation). > I just wouldn't register the service using dh-systemd given the reasons > I mentioned -- 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
