-v causes stacktrace, in-target doesnt' read TARGET_MOUNT_POINT

Bug #1237139 reported by Scott Moser on 2013-10-08
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
curtin
Medium
Unassigned
curtin (Ubuntu)
Undecided
Unassigned

Bug Description

In some local testing, I found 2 issues:
 a.) -v (--verbose) to main, causes stacktrace because it tries to set os.environ[CURTIN_VERBOSITY] to int(1).
 b.) curtin in-target does not read TARGET_MOUNT_POINT

Scott Moser (smoser) wrote :

fixed in upstream commits 91 and 92.

Changed in curtin:
importance: Undecided → Medium
status: New → Fix Released
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package curtin - 0.1.0~bzr93-0ubuntu1

---------------
curtin (0.1.0~bzr93-0ubuntu1) saucy; urgency=low

  * New upstream snapshot.
    * curtin/commands/in_target.py, curtin/commands/main.py:
      fix 'curtin -v' and 'curtin in-target' (LP: #1237139)
    * non-production / development changes:
      * doc/devel/README.txt: development doc update
      * tools/build-deb, tools/export-tarball:
        trunk development changes for creating tarball and building debs.
      * tools/launch: support '--add' for adding files such as config files
 -- Scott Moser <email address hidden> Tue, 08 Oct 2013 20:20:11 -0400

Changed in curtin (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers