| 2018-01-17 14:05:21 |
Eric Desrochers |
bug |
|
|
added bug |
| 2018-01-17 14:05:35 |
Eric Desrochers |
nominated for series |
|
Ubuntu Trusty |
|
| 2018-01-17 14:05:35 |
Eric Desrochers |
bug task added |
|
debian-installer (Ubuntu Trusty) |
|
| 2018-01-17 14:05:40 |
Eric Desrochers |
debian-installer (Ubuntu): status |
New |
Fix Released |
|
| 2018-01-17 14:06:16 |
Eric Desrochers |
tags |
|
ftbfs |
|
| 2018-01-17 14:07:12 |
Eric Desrochers |
bug |
|
|
added subscriber Mathieu Trudel-Lapierre |
| 2018-01-17 14:11:54 |
Eric Desrochers |
debian-installer (Ubuntu Trusty): assignee |
|
Mathieu Trudel-Lapierre (cyphermox) |
|
| 2018-01-17 14:12:24 |
Eric Desrochers |
debian-installer (Ubuntu Trusty): status |
New |
Confirmed |
|
| 2018-01-17 14:23:42 |
Eric Desrochers |
bug |
|
|
added subscriber STS Sponsors |
| 2018-01-17 14:48:55 |
Eric Desrochers |
removed subscriber STS Sponsors |
|
|
|
| 2018-01-17 14:49:14 |
Eric Desrochers |
bug |
|
|
added subscriber Hua Zhang |
| 2018-01-17 14:49:22 |
Eric Desrochers |
tags |
ftbfs |
ftbfs sts |
|
| 2018-01-17 14:51:29 |
Eric Desrochers |
description |
When build d-i on Trusty, I'm getting the following error:
#Buildlog
...
Using signed grub version 2.02~beta2-9ubuntu1.14
cp: cannot stat ‘/usr/lib/shim/shim.efi.signed’: No such file or directory
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>>/build'
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
I think 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/shim/shim.efi.signed" anymore but we see "/usr/lib/shim/shimx64.efi.signed"
https://pastebin.canonical.com/207767/
# debian-installer per release :
t/debian-installer-20101020ubuntu318.42/build/util/efi-image: cp /usr/lib/shim/shim.efi.signed "$workdir/boot$efi_name.efi"
x/debian-installer-20101020ubuntu451.18/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
z/debian-installer-20101020ubuntu504/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
a/debian-installer-20101020ubuntu523.1/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
b/debian-installer-20101020ubuntu527/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
The required shim change in d-i for Trusty never been integrated which explain why it works wel on all releases but Trusty.
Trusty is the only release who still have an hardcoded no longer existing file and not using the "$efi_name" variable. |
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-9ubuntu1.14
cp: cannot stat ‘/usr/lib/shim/shim.efi.signed’: No such file or directory
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>>/build'
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/shim/shim.efi.signed" anymore but we see "/usr/lib/shim/shimx64.efi.signed"
https://pastebin.canonical.com/207767/
# debian-installer src ci=ode per release :
t/debian-installer-20101020ubuntu318.42/build/util/efi-image: cp /usr/lib/shim/shim.efi.signed "$workdir/boot$efi_name.efi"
x/debian-installer-20101020ubuntu451.18/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
z/debian-installer-20101020ubuntu504/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
a/debian-installer-20101020ubuntu523.1/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
b/debian-installer-20101020ubuntu527/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
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. |
|
| 2018-01-17 14:51:38 |
Eric Desrochers |
debian-installer (Ubuntu Trusty): importance |
Undecided |
Medium |
|
| 2018-01-17 15:01:30 |
Eric Desrochers |
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-9ubuntu1.14
cp: cannot stat ‘/usr/lib/shim/shim.efi.signed’: No such file or directory
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>>/build'
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/shim/shim.efi.signed" anymore but we see "/usr/lib/shim/shimx64.efi.signed"
https://pastebin.canonical.com/207767/
# debian-installer src ci=ode per release :
t/debian-installer-20101020ubuntu318.42/build/util/efi-image: cp /usr/lib/shim/shim.efi.signed "$workdir/boot$efi_name.efi"
x/debian-installer-20101020ubuntu451.18/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
z/debian-installer-20101020ubuntu504/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
a/debian-installer-20101020ubuntu523.1/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
b/debian-installer-20101020ubuntu527/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
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. |
[Impact]
d-i FBTFS is a blocker for any future Trusty d-i SRU or 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_LP_ID>:<YOUR_PPA_NAME> ../debian-installer*.source.changes
* The build will fail with the following error in the build log
------------------------------------------------------------------
...
Using signed grub version 2.02~beta2-9ubuntu1.14
cp: cannot stat ‘/usr/lib/shim/shim.efi.signed’: No such file or directory
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>>/build'
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]
[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-9ubuntu1.14
cp: cannot stat ‘/usr/lib/shim/shim.efi.signed’: No such file or directory
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>>/build'
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/shim/shim.efi.signed" anymore but we see "/usr/lib/shim/shimx64.efi.signed"
https://pastebin.canonical.com/207767/
# debian-installer src ci=ode per release :
t/debian-installer-20101020ubuntu318.42/build/util/efi-image: cp /usr/lib/shim/shim.efi.signed "$workdir/boot$efi_name.efi"
x/debian-installer-20101020ubuntu451.18/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
z/debian-installer-20101020ubuntu504/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
a/debian-installer-20101020ubuntu523.1/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
b/debian-installer-20101020ubuntu527/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
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. |
|
| 2018-01-17 15:03:06 |
Eric Desrochers |
description |
[Impact]
d-i FBTFS is a blocker for any future Trusty d-i SRU or 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_LP_ID>:<YOUR_PPA_NAME> ../debian-installer*.source.changes
* The build will fail with the following error in the build log
------------------------------------------------------------------
...
Using signed grub version 2.02~beta2-9ubuntu1.14
cp: cannot stat ‘/usr/lib/shim/shim.efi.signed’: No such file or directory
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>>/build'
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]
[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-9ubuntu1.14
cp: cannot stat ‘/usr/lib/shim/shim.efi.signed’: No such file or directory
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>>/build'
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/shim/shim.efi.signed" anymore but we see "/usr/lib/shim/shimx64.efi.signed"
https://pastebin.canonical.com/207767/
# debian-installer src ci=ode per release :
t/debian-installer-20101020ubuntu318.42/build/util/efi-image: cp /usr/lib/shim/shim.efi.signed "$workdir/boot$efi_name.efi"
x/debian-installer-20101020ubuntu451.18/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
z/debian-installer-20101020ubuntu504/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
a/debian-installer-20101020ubuntu523.1/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
b/debian-installer-20101020ubuntu527/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
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. |
[Impact]
d-i FBTFS is a blocker for any future Trusty d-i SRU or 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_LP_ID>:<YOUR_PPA_NAME> ../debian-installer*.source.changes
* The build will fail with the following error in the build log
------------------------------------------------------------------
...
Using signed grub version 2.02~beta2-9ubuntu1.14
cp: cannot stat ‘/usr/lib/shim/shim.efi.signed’: No such file or directory
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>>/build'
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-9ubuntu1.14
cp: cannot stat ‘/usr/lib/shim/shim.efi.signed’: No such file or directory
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>>/build'
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/shim/shim.efi.signed" anymore but we see "/usr/lib/shim/shimx64.efi.signed"
https://pastebin.canonical.com/207767/
# debian-installer src ci=ode per release :
t/debian-installer-20101020ubuntu318.42/build/util/efi-image: cp /usr/lib/shim/shim.efi.signed "$workdir/boot$efi_name.efi"
x/debian-installer-20101020ubuntu451.18/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
z/debian-installer-20101020ubuntu504/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
a/debian-installer-20101020ubuntu523.1/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
b/debian-installer-20101020ubuntu527/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
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. |
|
| 2018-01-17 15:17:06 |
Eric Desrochers |
description |
[Impact]
d-i FBTFS is a blocker for any future Trusty d-i SRU or 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_LP_ID>:<YOUR_PPA_NAME> ../debian-installer*.source.changes
* The build will fail with the following error in the build log
------------------------------------------------------------------
...
Using signed grub version 2.02~beta2-9ubuntu1.14
cp: cannot stat ‘/usr/lib/shim/shim.efi.signed’: No such file or directory
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>>/build'
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-9ubuntu1.14
cp: cannot stat ‘/usr/lib/shim/shim.efi.signed’: No such file or directory
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>>/build'
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/shim/shim.efi.signed" anymore but we see "/usr/lib/shim/shimx64.efi.signed"
https://pastebin.canonical.com/207767/
# debian-installer src ci=ode per release :
t/debian-installer-20101020ubuntu318.42/build/util/efi-image: cp /usr/lib/shim/shim.efi.signed "$workdir/boot$efi_name.efi"
x/debian-installer-20101020ubuntu451.18/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
z/debian-installer-20101020ubuntu504/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
a/debian-installer-20101020ubuntu523.1/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
b/debian-installer-20101020ubuntu527/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
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. |
[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_LP_ID>:<YOUR_PPA_NAME> ../debian-installer*.source.changes
* The build will fail with the following error in the build log
------------------------------------------------------------------
...
Using signed grub version 2.02~beta2-9ubuntu1.14
cp: cannot stat ‘/usr/lib/shim/shim.efi.signed’: No such file or directory
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>>/build'
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-9ubuntu1.14
cp: cannot stat ‘/usr/lib/shim/shim.efi.signed’: No such file or directory
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>>/build'
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/shim/shim.efi.signed" anymore but we see "/usr/lib/shim/shimx64.efi.signed"
https://pastebin.canonical.com/207767/
# debian-installer src ci=ode per release :
t/debian-installer-20101020ubuntu318.42/build/util/efi-image: cp /usr/lib/shim/shim.efi.signed "$workdir/boot$efi_name.efi"
x/debian-installer-20101020ubuntu451.18/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
z/debian-installer-20101020ubuntu504/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
a/debian-installer-20101020ubuntu523.1/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
b/debian-installer-20101020ubuntu527/build/util/efi-image: cp "/usr/lib/shim/shim$efi_name.efi.signed" "$workdir/boot$efi_name.efi"
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. |
|
| 2018-01-19 14:35:33 |
Eric Desrochers |
attachment added |
|
lp1743787-trusty.debdiff https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1743787/+attachment/5039554/+files/lp1743787-trusty.debdiff |
|
| 2018-01-26 11:31:41 |
Eric Desrochers |
debian-installer (Ubuntu Trusty): assignee |
Mathieu Trudel-Lapierre (cyphermox) |
Eric Desrochers (slashd) |
|
| 2018-01-26 11:31:47 |
Eric Desrochers |
debian-installer (Ubuntu Trusty): status |
Confirmed |
In Progress |
|
| 2018-02-01 14:16:05 |
Eric Desrochers |
bug |
|
|
added subscriber SRU Verification |
| 2018-02-01 14:16:15 |
Eric Desrochers |
bug |
|
|
added subscriber STS Sponsors |
| 2018-02-01 14:16:33 |
Eric Desrochers |
tags |
ftbfs sts |
ftbfs sts sts-sponsor-slashd-done |
|
| 2018-02-06 13:43:55 |
Eric Desrochers |
removed subscriber STS Sponsors |
|
|
|
| 2018-02-08 12:07:40 |
Łukasz Zemczak |
debian-installer (Ubuntu Trusty): status |
In Progress |
Fix Committed |
|
| 2018-02-08 12:07:41 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2018-02-08 12:07:48 |
Łukasz Zemczak |
tags |
ftbfs sts sts-sponsor-slashd-done |
ftbfs sts sts-sponsor-slashd-done verification-needed verification-needed-trusty |
|
| 2018-02-09 18:13:21 |
Eric Desrochers |
tags |
ftbfs sts sts-sponsor-slashd-done verification-needed verification-needed-trusty |
ftbfs sts sts-sponsor-slashd-done verification-done verification-done-trusty |
|
| 2018-02-15 07:43:21 |
Launchpad Janitor |
debian-installer (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2018-02-15 07:43:27 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2018-12-14 09:16:32 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-core-dev/debian-installer/trusty-proposed |
|
