[Bug 890261] Re: can not execute oem-config in a chrooted environment

[Launchpad Bug Tracker]

[Expired for ubiquity (Ubuntu) because there has been no activity for 60
days.]

** Changed in: ubiquity (Ubuntu)
       Status: Incomplete => Expired

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

Title:
  can not execute oem-config in a chrooted environment

Status in ubiquity package in Ubuntu:
  Expired

Bug description:
  for live-build we would like to be able to add a user, passowrd,
  hostname etc, to certain kinds of image builds. often someone writes a
  custom script using useradd or adduser etc which then is run post
  image build time ... given that we have established and well
  maintained mechanisms to do these tasks in ubuntu it would be good to
  be able to have a live-build option that installs oem-config at the
  end of a build, applies a preseed file, executes oem-config in
  automatic mode to parse the preseed file and apply the settings and in
  the end cleanly removes oem-config and the pulled in dependencies.

  currently oem-config execution inside a chroot fails in various places. for implementing the above this needs to be fixed.
  debug data will be added soon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/890261/+subscriptions