Merge lp:~pitti/ubiquity/ubuntu-drivers-common into lp:ubiquity
Status: | Merged |
---|---|
Merged at revision: | 5493 |
Proposed branch: | lp:~pitti/ubiquity/ubuntu-drivers-common |
Merge into: | lp:ubiquity |
Diff against target: |
140 lines (+18/-52) 5 files modified
debian/changelog (+9/-0) debian/control (+1/-1) scripts/plugininstall.py (+0/-37) scripts/simple-plugins (+4/-2) ubiquity/plugins/ubi-prepare.py (+4/-12) |
To merge this branch: | bzr merge lp:~pitti/ubiquity/ubuntu-drivers-common |
Related bugs: | |
Related blueprints: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Evan (community) | Approve | ||
Martin Pitt (community) | Needs Resubmitting | ||
Review via email: mp+107744@code.launchpad.net |
Description of the change
As per https:/
The main change is in scripts/
scripts/
Unfortunately I cannot test this on real iron, as the current quantal daily gets a kernel oops when I select "install 3rd party drivers" and click continue (oopsing on rmmod, presumably it tries to install bcmwl-kernel-
May 29 09:04:04 ubuntu ubiquity: The following NEW packages will be installed:
May 29 09:04:04 ubuntu ubiquity: bcmwl-kernel-source dkms fakeroot
May 29 09:04:04 ubuntu ubiquity: debconf: DbDriver "config": /var/cache/
process: Resource temporarily unavailable
[...]
May 29 09:04:05 ubuntu ubiquity: Processing triggers for man-db ...
May 29 09:04:05 ubuntu ubiquity: /var/lib/
May 29 09:04:05 ubuntu ubiquity: 3: Bad file descriptor
May 29 09:04:05 ubuntu ubiquity: dpkg: error processing man-db (--unpack):
May 29 09:04:05 ubuntu ubiquity: subprocess installed post-installation script returned error exit status 2
May 29 09:04:05 ubuntu ubiquity: No apport report written because MaxReports is reached already
May 29 09:04:05 ubuntu ubiquity: Errors were encountered while processing:
May 29 09:04:05 ubuntu ubiquity: man-db
May 29 09:04:05 ubuntu ubiquity: E: Sub-process /usr/bin/dpkg returned an error code (1)
May 29 09:04:05 ubuntu ubiquity: ubuntu-drivers autoinstall failed with code: 100
After that, bcmwl-kernel-source is installed but unconfigured; sudo dpkg --configure -a fixes that. However, bcmwl-kernel-source is not installed in the target system after ubiquity finishes; is ubiquity meant to copy the installed package from the live system, or does the plugin get called again in the /target/ chroot for a fresh install? (In that case that would use the unhacked ubuntu-drivers in /target, which of course would not pull in bcmwl for a KVM system).
Repeating this from IRC, so we have a record.
Debconf does not like multiple things talking to it. Since ubiquity is already talking to it, you need to do something like:
DEBCONF_ DB_REPLACE= configdb DEBCONF_ DB_OVERRIDE= "Pipe{infd: none outfd:none}" ubuntu-drivers autoinstall
You'll also need to replicate jockey/ debian/ jockey. ubiquity to get the installed packages in /target. Colin mentioned that you can subclass plugin. InstallPlugin to have post-install tasks, though he also suggested that target-config hooks (like the existing Jockey one) are preferable.
Thanks for this work!