[MIR] u-boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
u-boot (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Natty |
Fix Released
|
High
|
Unassigned |
Bug Description
Binary package hint: u-boot
Hi
u-boot's mkimage tool was shipped in the uboot-mkimage source and binary package until recently. This source was an old fork of u-boot and had been promoted to main because mkimage is needed on ARM system booting with u-boot as to convert the kernel zImage to the uImage format.
Debian transitioned to the u-boot source and binary package to ship the mkimage tool, and the removal of uboot-mkimage is pending.
u-boot contains similar source than u-boot-omap4 which we had in main in maverick at some point, but comes from directly from upstream (via Debian) while u-boot-omap4 was an omapzoom fork used in pandaboard images.
Note that while the u-boot package builds bootloaders on various architectures, we would only use mkimage in main; most u-boot binaries we use would probably come from the u-boot-linaro source instead. So I don't see much security risk in
I fixed a minor issue with u-boot recently, and I'm aware of these two things which need fixing:
- fails to build on i386; I identified the cause and am discussing a fix with upstream; this not a blocker as it's currently only installed on ARM systems and used to build debian-installer on ARM, but it is also useful on cdimage to build ARM images, and so it will eventually need to be fixed on i386 as well
- needs to provide a transitional package for systems which have uboot-mkimage installed; hrw proposed a patch adding this which I'll sponsor ASAP.
I didn't scrutinize the packaging too much, it mostly comes from Debian and I expect most of the maintenance to continue in Debian.
I've checked UbuntuMainInclu
Cheers,
Changed in u-boot (Ubuntu): | |
milestone: | none → natty-alpha-2 |
Changed in u-boot (Ubuntu Natty): | |
importance: | Undecided → High |
it is not "also useful" on cdimage, it seems that uboot-mkimage was removed from the archive before this MIR was approved, which results in *all* armel images failing to build now, can this MIR please be approved ASAP so we can make sure to have working images before the sprint ?