[Bug 1743787] Re: FTBFS in Trusty

[Łukasz Zemczak]

Hello Eric, or anyone else affected,

Accepted debian-installer into trusty-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/debian-
installer/20101020ubuntu318.43 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-trusty to verification-done-trusty. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-trusty. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: debian-installer (Ubuntu Trusty)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-trusty

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to debian-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1743787

Title:
  FTBFS in Trusty

Status in debian-installer package in Ubuntu:
  Fix Released
Status in debian-installer source package in Trusty:
  Fix Committed

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_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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1743787/+subscriptions