← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1730642] Re: Support generating a rootfs tree only

 

This bug was fixed in the package livecd-rootfs - 2.478.1

---------------
livecd-rootfs (2.478.1) artful; urgency=medium

  [ Gary Wang ]
  * Add the IMAGEFORMAT=none to support generating a single rootfs
    (LP: #1730642)

 -- Łukasz 'sil2100' Zemczak <lukasz.zemczak@xxxxxxxxxx>  Wed, 08 Nov
2017 12:02:04 +0100

** Changed in: livecd-rootfs (Ubuntu Artful)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1730642

Title:
  Support generating a rootfs tree only

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Committed
Status in livecd-rootfs source package in Zesty:
  Fix Committed
Status in livecd-rootfs source package in Artful:
  Fix Released

Bug description:
  [Impact]

  For the use of ubuntu-image classic image generation, it is required
  that livecd-rootfs supports a way to only generate the rootfs tree for
  a selected set of arguments (project, architecture etc.). By design
  ubuntu-image will use livecd-rootfs for preparation of the rootfs
  contents and then continue with building the image. Since ubuntu-image
  is backported feature-complete into artful, zesty and xenial, we would
  need the same change to be propagated to those stable series.

  [Test Case]

   * Install livecd-rootfs from -proposed
   * Create a temporary directory, cd into it
   * cp -a `dpkg -L livecd-rootfs | grep "auto$"` .
   * PROJECT="ubuntu-cpc" ARCH=amd64 IMAGEFORMAT=none SUITE=<SERIES> lb config
   * PROJECT="ubuntu-cpc" ARCH=amd64 IMAGEFORMAT=none SUITE=<SERIES> lb build
   * Make sure the build succeeds and that the current directory will have a chroot/ with the build rootfs contents

  [Regression Potential]

  The proposed change should be self-contained and not affecting any
  other code paths, but in the case of a very unlikely situation regular
  image builds could be broken by binary hooks not being executed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1730642/+subscriptions


References