lb_chroot_dpkg doesn't check dpkg version before setting 'unsafe-io' option
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
live-build (Debian) |
Fix Released
|
Unknown
|
|||
live-build (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
The dpkg in the chroot (on a lucid build for example) might not be new enough to handle the 'unsafe-io' option set in the configuration file.
lb_chroot_dpkg should check the chroot's dpkg capability first, e.g.
Chroot chroot dpkg --force-help | grep -q unsafe-io
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: live-build 3.0~a24-1ubuntu17 [modified: usr/share/
ProcVersionSign
Uname: Linux 3.0.0-12-virtual x86_64
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
Date: Thu Oct 27 17:02:24 2011
PackageArchitec
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: live-build
UpgradeStatus: Upgraded to oneiric on 2011-10-14 (13 days ago)
Related branches
Changed in live-build (Ubuntu): | |
assignee: | nobody → Neil Wilson (neil-aldur) |
Changed in live-build (Ubuntu): | |
assignee: | Neil Wilson (neil-aldur) → nobody |
Changed in live-build (Debian): | |
status: | Unknown → New |
Changed in live-build (Debian): | |
status: | New → Fix Released |
I have to say that I somewhat agree with Daniel Baumann in his reply to the Debian bug; we only switched to live-build as of oneiric, and it would not at all surprise me to find that quite a few little things need to be changed to make it work well on lucid. I'm reluctant to embark on that kind of thing when it might well be much easier to simply use an oneiric chroot. Could you elaborate on your requirements here, and why you need to use a lucid chroot?