FTBFS in Trusty
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
debian-installer (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Trusty |
Fix Released
|
Medium
|
Eric Desrochers |
Bug Description
[Impact]
d-i FBTFS is a blocker for any future preseed SRU that require a d-i rebuild to create for instance a new mini.iso (Minimal image of Ubuntu).
[Test Case]
* Perform the following :
$ pull-lp-source debian-installer trusty
$ cd debian-installer-*
$ dch -i # Bump version in debian/changelog
$ debuild -S -k<YOUR_LP_GPG_KEY>
$ dput ppa:<YOUR_
* The build will fail with the following error in the build log
-------
...
Using signed grub version 2.02~beta2-
cp: cannot stat ‘/usr/lib/
make[7]: *** [x86_grub_efi] Error 1
make[6]: *** [_build] Error 2
make[5]: *** [flavour_build] Error 2
make[4]: *** [medium_build] Error 2
make[3]: *** [subarch_build] Error 2
make[2]: *** [all_build] Error 2
make[2]: Leaving directory `/<<PKGBUILDDIR
make[1]: *** [build-images] Error 2
make[1]: Leaving directory `/<<PKGBUILDDIR>>'
make: *** [install] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit status 2
-------
[Regression Potential]
No regression anticipated, it will simply fix the FTBFS by making sure d-i reflect new shim-signed package reality.
[Other Info]
Only trusty is impacted.
[Original Description]
When building d-i on Trusty as-is, we are getting a FBTFS situation with the following error:
# Launchpad Buildlog
...
Using signed grub version 2.02~beta2-
cp: cannot stat ‘/usr/lib/
make[7]: *** [x86_grub_efi] Error 1
make[6]: *** [_build] Error 2
make[5]: *** [flavour_build] Error 2
make[4]: *** [medium_build] Error 2
make[3]: *** [subarch_build] Error 2
make[2]: *** [all_build] Error 2
make[2]: Leaving directory `/<<PKGBUILDDIR
make[1]: *** [build-images] Error 2
make[1]: Leaving directory `/<<PKGBUILDDIR>>'
make: *** [install] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit status 2
The problem is that d-i for Trusty hasn't been built for a long time and recent shim-signed change never been adapt into d-i for Trusty which explain why it no longer build properly anymore.
When looking shim-signed pkg on Trusty, there is no presence of "/usr/lib/
https:/
# debian-installer src ci=ode per release :
t/debian-
x/debian-
z/debian-
a/debian-
b/debian-
The required shim change in d-i for Trusty never been integrated which explain why it works as expected on all releases but Trusty.
Trusty is the only release who still have an hard-coded no longer existing file and not using the "$efi_name" variable.
Related branches
Changed in debian-installer (Ubuntu): | |
status: | New → Fix Released |
tags: | added: ftbfs |
tags: | added: sts |
description: | updated |
Changed in debian-installer (Ubuntu Trusty): | |
importance: | Undecided → Medium |
description: | updated |
description: | updated |
description: | updated |
Changed in debian-installer (Ubuntu Trusty): | |
assignee: | Mathieu Trudel-Lapierre (cyphermox) → Eric Desrochers (slashd) |
status: | Confirmed → In Progress |
tags: | added: sts-sponsor-slashd-done |
As per my conversation with cyphermox, he is agree with the above analysis and will take care of the SRU for this.
Thanks cyphermox.