Bug#772983: kirkwood kernel image is too big

2014-12-16 Thread Ian Campbell
On Sun, 2014-12-14 at 19:26 +, Ben Hutchings wrote: I think it would be better to add an unconditional warning, rather than an error, when there is 1% free space left. I realise this will be easy to ignore but it's still better than an unnecessary failure. OK, makes sense. Here's what

Bug#772983: kirkwood kernel image is too big

2014-12-15 Thread Ben Hutchings
On Sun, 2014-12-14 at 17:56 +, Ian Campbell wrote: On Fri, 2014-12-12 at 20:59 +, Ben Hutchings wrote: That implies we want to allow for about 1% growth from the size in the .0 release. I'm considering something like this. What do you think? diff --git a/debian/bin/buildcheck.py

Bug#772983: kirkwood kernel image is too big

2014-12-14 Thread Ian Campbell
On Sat, 2014-12-13 at 18:09 +, Ben Hutchings wrote: On Sat, 2014-12-13 at 07:57 +, Ian Campbell wrote: On Fri, 2014-12-12 at 20:59 +, Ben Hutchings wrote: [...] I misread earlier - kirkwood is about 2.5 KB below the limit, not 1. Anyway, both kirkwood and orion5x have much

Bug#772983: kirkwood kernel image is too big

2014-12-14 Thread Ian Campbell
On Fri, 2014-12-12 at 20:59 +, Ben Hutchings wrote: That implies we want to allow for about 1% growth from the size in the .0 release. I'm considering something like this. What do you think? diff --git a/debian/bin/buildcheck.py b/debian/bin/buildcheck.py index a6f6f06..5bb815c 100755 ---

Bug#772983: kirkwood kernel image is too big

2014-12-13 Thread Ian Campbell
On Fri, 2014-12-12 at 20:59 +, Ben Hutchings wrote: I had originally planned to switch QNAP over for 3.16 but it wasn't quite ready upstream (I've forgotten why). The board files went away in 3.17 so in experimental (v3.18) appending is necessary. Once I've worked out some kinks with

Bug#772983: kirkwood kernel image is too big

2014-12-13 Thread Ben Hutchings
On Sat, 2014-12-13 at 07:57 +, Ian Campbell wrote: On Fri, 2014-12-12 at 20:59 +, Ben Hutchings wrote: [...] I misread earlier - kirkwood is about 2.5 KB below the limit, not 1. Anyway, both kirkwood and orion5x have much less than 1% of growth room and ixp4xx has slightly less. I

Bug#772983: kirkwood kernel image is too big

2014-12-12 Thread Ben Hutchings
Package: src:linux Version: 3.16.7-2 Severity: serious The kirkwood and orion5x kernel images generally have to be installed in flash partitions with a fixed size. Currently we check at build time that vmlinuz is small enough to fit. However, these platforms now require Device Tree blobs, and

Bug#772983: kirkwood kernel image is too big

2014-12-12 Thread Ian Campbell
On Fri, 2014-12-12 at 18:12 +, Ben Hutchings wrote: Package: src:linux Version: 3.16.7-2 Severity: serious The kirkwood and orion5x kernel images generally have to be installed in flash partitions with a fixed size. Currently we check at build time that vmlinuz is small enough to fit.

Bug#772983: kirkwood kernel image is too big

2014-12-12 Thread Ben Hutchings
Control: severity -1 important Control: retitle -1 armel kernel images are close to size limits On Fri, 2014-12-12 at 19:36 +, Ian Campbell wrote: On Fri, 2014-12-12 at 18:12 +, Ben Hutchings wrote: Package: src:linux Version: 3.16.7-2 Severity: serious The kirkwood and