Ubuntu
ubiquity package

The /bin/in-target script fails because udpkg is not in PATH

Bug #1836734 reported by Paride Legovini
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
New
Undecided
Unassigned

Bug Description

The /bin/in-target script provided by the ubiquity package fails because it sources /lib/chroot-setup.sh (provided by the ubiquity package, but originally part of debian-installer-utils), and chroot-setup.sh relies on `udpkg` being in the PATH, while this is not the case when installing with ubiquity.

chroot-setup.sh assumes the installer is the d-i, where the 'udpkg' package provides /usr/bin/udpkg, which in ubiquity installs is relegated to /usr/lib/ubiquity/compat/udpkg.

Related branches

~paride/utah/+git/utah:latecommand-fixes
Jean-Baptiste Lallement: Approve
Diff: 26 lines (+8/-1)
2 files modified
templates/latecommand-wrapper.jinja2 (+3/-0)
templates/log-function.jinja2 (+5/-1)
Paride Legovini (paride)
summary: - in-target script fails because dpkg is not in PATH
+ The /bin/in-target script fails because dpkg is not in PATH
summary: - The /bin/in-target script fails because dpkg is not in PATH
+ The /bin/in-target script fails because udpkg is not in PATH
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.