On Sun, 2019-03-10 at 09:51 -0700, Vagrant Cascadian wrote: > 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. [...] > > I've asked the release team (cc-ed), and it was confirmed binNMUing > > debian-installer seems appropriate. This will be done shortly. > > Great!
The updated images for armhf have been available in p-u for a couple of days now. Feedback would be appreciated, as we would like to be able to accept the new kernel upload into p-u, which will block a further rebuild here as it brings an ABI bump. (The existing images should continue to work until the older packages are decrufted in the next point release.) Regards, Adam
