On 13/02/2015 14:08, Michal Suchanek wrote: > the build still fails when multiple kernel flavours are installed and > multiple kernels of the same flavour are installed. Live-build contains > this code: > mv binary/${_INITRAMFS}/vmlinuz-*-${_FLAVOUR} > binary/${_INITRAMFS}/vmlinuz${_NUMBER} > Obvoiusly, in case vmlinuz-*-${_FLAVOUR} expands to multiple files > this command fails.
I have just recently completed a large chunk of work improving the existing bootloader code in live-build. You will find an archive containing a set of 73 commits attached to the last post of bug #775322 (which I used for tracking this work). While I have not specifically tackled support for multiple versions of the same kernel flavour (perhaps you could actually help me understand the use case for this), I have improved the piece of code you refer to here, which now applies the same logic as when a single kernel flavour is requested (using only the latest version for each flavour). You will find this change specifically in patch #29 in the above mentioned set of 73 bootloader improvement patches. I then moved this logic directly into binary_linux-image in patch #34, thus applying simple kernel file renaming to all bootloaders, thus helping pave the way to the introduction of EFI bootloader support (which I have a done a lot of the work for already on my local system). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org