On 2019-03-10, Cyril Brulebois wrote: > Vagrant Cascadian <vagr...@debian.org> (2019-03-09): >> >> Thanks for your report; that's known and fixed on the kernel side >> >> already; how to deal with d-i is discussed in: >> >> https://lists.debian.org/debian-boot/2019/03/msg00165.html >> >> >> >> Currently waiting on some input from Vagrant: >> >> https://lists.debian.org/debian-boot/2019/03/msg00179.html >> >> I rebuilt the package from the stretch git branch on armhf against >> stretch+stretch-updates, and the build went fine. I tested the netboot >> image and it too seems to be working. > > Thanks for checking. > > Assuming you meant stretch + stretch-proposed-updates, meaning an > unchanged source package
No changes from the git branch, other than a changelog entry to bump the version. I had to double-check since stretch-proposed-updates wasn't in my apt sources in the chroot... INFO: using 'http://deb.debian.org/debian' for stretch-proposed-updates Using generated sources.list.udeb: deb [trusted=yes] copy:/<<PKGBUILDDIR>>/build/ localudebs/ deb http://deb.debian.org/debian stretch main/debian-installer deb http://deb.debian.org/debian stretch-proposed-updates main/debian-installer make[8]: 'sources.list.udeb' is up to date. >From the build log, Looks like it did indeed pull in from stretch-proposed-updates. > I've asked the release team (cc-ed), and it was confirmed binNMUing > debian-installer seems appropriate. This will be done shortly. Great! live well, vagrant