Hi all,
I'd like to note that since 3.2.4-1, the package's maintainer scripts
actually _remove_ /etc/default/puppet if it's unmodified or save it as
/etc/default/puppet.dpkg-bak if it has been modified by the user. The
latter means that even for sysvinit users where the initscript is
Control: severity -1 serious
Rik Theys rik.th...@esat.kuleuven.be writes:
I was under the impression that upgrades from Wheezy to Jessie would
switch the init system to systemd by default, unless a pin was
configured prior to the upgrade (as instructed in the draft release
notes)? Or do you
Hi,
On 02/23/2015 11:56 AM, Stig Sandbeck Mathisen wrote:
I'm not going to add it back, but unless I'm missing something in the
scenario I've outlined above, I don't agree there are no security
implications here.
There is a bug, which should be fixed. I've upgraded it to serious
again, so it
Hi,
On Sat, 21 Feb 2015, Stig Sandbeck Mathisen wrote:
Rik Theys rik.th...@esat.kuleuven.be writes:
During an upgrade from wheezy to jessie, puppet was upgraded to 3.7.2
and systemd became the default init system.
When jessie is released, an upgrade should keep the current init system.
I
Control: severity -1 wishlist wontfix
Control: tags -1 - security
Rik Theys rik.th...@esat.kuleuven.be writes:
During an upgrade from wheezy to jessie, puppet was upgraded to 3.7.2
and systemd became the default init system.
When jessie is released, an upgrade should keep the current init
5 matches
Mail list logo
