On 6 September 2017 at 14:21, Joshua Watt wrote:
> On Tue, 2017-08-01 at 12:07 +0100, Burton, Ross wrote:
> > Sorry didn't notice the v2. In staging now.
>
> I noticed this hasn't been merged yet, is there something holding it
> up?
It was implicated in a number of the test cases failing. I'l
On Tue, 2017-08-01 at 12:07 +0100, Burton, Ross wrote:
> Sorry didn't notice the v2. In staging now.
I noticed this hasn't been merged yet, is there something holding it
up?
>
> Ross
>
> On 25 July 2017 at 03:23, Joshua Watt wrote:
> > On Mon, 2017-07-03 at 20:18 -0500, Joshua Watt wrote:
> >
Sorry didn't notice the v2. In staging now.
Ross
On 25 July 2017 at 03:23, Joshua Watt wrote:
> On Mon, 2017-07-03 at 20:18 -0500, Joshua Watt wrote:
> > 106b59d9 broke SSH host key generation when systemd and a read-only
> > root file
> > system are in use because there isn't a way for system
On Mon, 2017-07-03 at 20:18 -0500, Joshua Watt wrote:
> 106b59d9 broke SSH host key generation when systemd and a read-only
> root file
> system are in use because there isn't a way for systemd to get the
> optional
> weak assigment of SYSCONFDIR from /etc/default/sshd and still provide
> a default
106b59d9 broke SSH host key generation when systemd and a read-only root file
system are in use because there isn't a way for systemd to get the optional
weak assigment of SYSCONFDIR from /etc/default/sshd and still provide a default
value if it is not specified. Instead, move the logic for determi
