Bug#682342: Latest patch successfully tested

2019-10-09 Thread Nishanth Aravamudan
On 22.08.2019 [21:45:26 +0200], Philipp Kern wrote: > On 8/16/2019 8:34 PM, Nishanth Aravamudan wrote: > > On 15.08.2019 [17:08:39 +0200], Cyril Brulebois wrote: > >> Nishanth Aravamudan (2019-08-14): > >>> We are able to reproduce this issue at will in Ubuntu Bionic's > >>> installer (not

Bug#682342: Latest patch successfully tested

2019-08-22 Thread Philipp Kern
On 8/16/2019 8:34 PM, Nishanth Aravamudan wrote: > On 15.08.2019 [17:08:39 +0200], Cyril Brulebois wrote: >> Nishanth Aravamudan (2019-08-14): >>> We are able to reproduce this issue at will in Ubuntu Bionic's >>> installer (not identical to Debian's, but code-wise in this path the >>> same).

Bug#682342: Latest patch successfully tested

2019-08-16 Thread Nishanth Aravamudan
On 15.08.2019 [17:08:39 +0200], Cyril Brulebois wrote: > Hi, > > Nishanth Aravamudan (2019-08-14): > > We are able to reproduce this issue at will in Ubuntu Bionic's > > installer (not identical to Debian's, but code-wise in this path the > > same). While quite a while after the last update

Bug#682342: Latest patch successfully tested

2019-08-15 Thread Cyril Brulebois
Hi, Nishanth Aravamudan (2019-08-14): > We are able to reproduce this issue at will in Ubuntu Bionic's > installer (not identical to Debian's, but code-wise in this path the > same). While quite a while after the last update from Philipp, we > tested the patch (netcfg_dhcp_domain.patch) after

Bug#682342: Latest patch successfully tested

2019-08-14 Thread Nishanth Aravamudan
We are able to reproduce this issue at will in Ubuntu Bionic's installer (not identical to Debian's, but code-wise in this path the same). While quite a while after the last update from Philipp, we tested the patch (netcfg_dhcp_domain.patch) after updating it to avoid a compilation issue, we found