[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#870615: debian-installer: FTBFS on armhf: missing firefly-rk3288/u-boot.img



Control: tags 870615 pending

On 2017-08-03, Vagrant Cascadian wrote:
> Control: severity 870615 important
>
> On 2017-08-03, Vagrant Cascadian wrote:
>> On 2017-08-03, Cyril Brulebois wrote:
>>> d-i now FTBFSes on armhf, due to:
>>> ,---[ hd-media ]---
>>> | gen-hd-image: Installing /usr/lib/u-boot/firefly-rk3288/u-boot-spl.rksd at sector 64 ...
>>> | gen-hd-image: Installing /usr/lib/u-boot/firefly-rk3288/u-boot.img at sector 256 ...
>>> | config/armhf//hd-media.cfg:33: recipe for target 'hd-media_images_concatenateable' failed
> ...
>>> I suppose this is due to this change in u-boot on 2017-08-01:
>>> |  u-boot (2017.07+dfsg1-2) unstable; urgency=medium
>>> |  .
>>> |    * u-boot-rockchip:
>>> |      - Ship u-boot.bin in firefly-rk3288 instead of u-boot.img.
>>> |      - Add NEWS file explaining the change for firefly-rk3288.
>>>
>>> See https://tracker.debian.org/news/860117
> ...
>> This may actually require changing the d-i code(the new method requires
>> appending two things together before dd'ing them, rather that dd'ing two
>> things at specific locations), or more changes to u-boot (I could
>> pregenerate that part in u-boot, though that means shipping redundant
>> bits).

I went with the latter approach, so u-boot-rockchip includes a single
binary that debian-installer can use.


>> Might be best to temporarily disable the firefly-rk3288 in d-i until I
>> figure out what's best to do...
>
> I've disabled it in git for now, will explore a proper fix soon.

And now fixed in u-boot 2017.07+dfsg1-3 (just uploaded), corresponding
fix in debian-installer pushed to git.


live well,
  vagrant

Attachment: signature.asc
Description: PGP signature


Reply to: