Bug#719316: postinst scripts cannot tell whether this is the first installation

2013-08-10 Thread Michael Stapelberg
Hi Guillem, Guillem Jover writes: > I'd be curious to know about that workaround. One of the features of deb-systemd-helper is that it can reconstruct this state (first install or not) from the state file it keeps for other reasons (the fact that systemd might or might not be running all the time

Bug#719316: postinst scripts cannot tell whether this is the first installation

2013-08-10 Thread Guillem Jover
Control: severity -1 wishlist On Sat, 2013-08-10 at 18:07:03 +0200, Michael Stapelberg wrote: > First of all, we have a workaround for this issue which works well, but > in the future it would be nice to migrate away from that. I'd be curious to know about that workaround. > Packages that ship a

Bug#719316: postinst scripts cannot tell whether this is the first installation

2013-08-10 Thread Adam D. Barratt
On Sat, 2013-08-10 at 18:07 +0200, Michael Stapelberg wrote: > Now, we want to preserve the enabled/disabled state, i.e. on package > upgrades, we do _not_ want to re-enable the file and overwrite the > user’s choice. > > The best way to do this is: > > 1) call systemctl enable on the _initial_ p

Bug#719316: postinst scripts cannot tell whether this is the first installation

2013-08-10 Thread Michael Stapelberg
Package: dpkg Version: 1.16.10 Severity: normal First of all, we have a workaround for this issue which works well, but in the future it would be nice to migrate away from that. Packages that ship a systemd service file (let’s use thinkfan.service as an example) need to enable that file on the in