Package: debian-installer Version: 20161031 Severity: serious Justification: FTBFS(ish)
(X-D-Cc: u-boot Maintainer & Uploaders; please keep them in the loop when replying; also debian-arm@ for good measure.) Hi, Steve noted that the armel build fails on the cdimage side because kirkwood/u-boot stuff is missing for openrd. This isn't entirely surprising because the latest u-boot upload to unstable, which got used to build debian-installer 20161031 had: | u-boot (2016.09+dfsg1-2) unstable; urgency=medium […] | * Remove openrd targets, as they do not boot (Closes: #837629). | | -- Vagrant Cascadian <vagr...@debian.org> Sun, 23 Oct 2016 19:36:36 -0700 I might have missed messages on debian-boot@, but a quick search on kirkwood or openrd doesn't get me any unread messages warning us about their imminent removal. It really would be nice to make sure debian-boot@ knows about such things in advance (even better if I get explicitly cc'ed on this so as to make sure I don't miss something affecting next d-i releases). That being said, there's still the issue of debian-installer's build system not detecting this issue, which is what this bug report is about. Once a fix is implemented for this specific issue, it would be nice to know what to do with the kirkwood/u-boot things for openrd. If they're not going to work (again/at all), the relevant code should go away from debian-installer.git; or am I missing anything? Input welcome. KiBi.