[Bug 900526] Re: d-i fails to divert initctl when upgrading packages during install

Martin Pitt martin.pitt at ubuntu.com
Fri Feb 10 06:27:38 UTC 2012

Resetting verification tags for the other releases.

** Tags removed: verification-done
** Tags added: verification-done-lucid verification-needed

You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to debian-installer-utils in

  d-i fails to divert initctl when upgrading packages during install

Status in “debian-installer-utils” package in Ubuntu:
  Fix Released
Status in “debian-installer-utils” source package in Lucid:
  Fix Released
Status in “debian-installer-utils” source package in Maverick:
  Won't Fix
Status in “debian-installer-utils” source package in Natty:
  Fix Committed
Status in “debian-installer-utils” source package in Oneiric:
  Fix Committed
Status in “debian-installer-utils” source package in Precise:
  Fix Released
Status in “debian-installer-utils” source package in Hardy:
  Fix Committed
Status in “debian-installer-utils” package in Debian:
  Fix Released

Bug description:
  TEST CASE: Run a netboot installation with apt-setup/proposed=true.
  Watch 'ls -l /target/sbin/start-stop-daemon* /target/sbin/initctl*'
  after the base system is installed and ensure that there's no period
  when both start-stop-daemon and start-stop-daemon.REAL (similarly
  initctl and initctl.REAL) are non-fake versions - you can tell by the
  size - and that if there's an update available for dpkg or upstart
  that the timestamp of the relevant binaries get updated.  In the hardy
  case, don't worry about initctl, and dpkg probably won't be upgraded
  but it's still worth checking that start-stop-daemon is diverted

  Regression potential: Checking whether installs with apt-
  setup/proposed=true work should be sufficient.

  Original report follows:

  The SRU verification for bug #771372 in maverick has revealed that
  debian-installer's chroot setup handling when installing/upgrading
  packages at install time is different than the chroot setup used by
  debootstrap.  When initially bootstrapping a maverick system, the
  postinst script of the maverick procps package has its call to 'start'
  successfully intercepted; however, when *upgrading* the procps package
  after debootstrap, the start call is not intercepted, resulting in
  install failures.

  Since this is impossible to fix in the maverick installer post-
  release, I'll backport the fix for bug #602896 in a subsequent procps
  SRU; but investigation is needed here to find out why d-i isn't
  handling initctl correctly and make sure this is properly resolved for

  15:03 < cjwatson> chroot-setup.sh is supposed to divert initctl too
  15:08 < cjwatson> slangasek: There is something odd there, indeed.  I don't quite see what; visually, the code seems right
  15:08 < slangasek> cjwatson: should I raise a bug on debian-installer?
  15:08 < cjwatson> slangasek: yes please
  15:09 < slangasek> ok
  15:09 < cjwatson> (probably belongs on either pkgsel or debian-installer-utils, but debian-installer is the place to start)

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: debian-installer (not installed)
  ProcVersionSignature: Ubuntu 3.2.0-2.6-generic 3.2.0-rc3
  Uname: Linux 3.2.0-2-generic x86_64
  ApportVersion: 1.90-0ubuntu1
  Architecture: amd64
  Date: Mon Dec  5 15:19:29 2011
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
  MachineType: LENOVO 3249CTO
   total       used       free     shared    buffers     cached
   Mem:       3908928    3711928     197000          0     101976    1062528
   -/+ buffers/cache:    2547424    1361504
   Swap:      6291452     257140    6034312
   PATH=(custom, user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-2-generic root=/dev/mapper/hostname-root ro pcie_aspm=force quiet splash vt.handoff=7
  SourcePackage: debian-installer
  UpgradeStatus: Upgraded to precise on 2011-11-08 (27 days ago)
  dmi.bios.date: 08/23/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET52WW (1.22 )
  dmi.board.name: 3249CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: dmi:bvnLENOVO:bvr6QET52WW(1.22):bd08/23/2010:svnLENOVO:pn3249CTO:pvrThinkPadX201:rvnLENOVO:rn3249CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3249CTO
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:

More information about the foundations-bugs mailing list