Your message dated Wed, 02 Nov 2011 13:33:39 +0100
with message-id <[email protected]>
and subject line Re: Bug#647402: live-build: Check version of dpkg before
activating 'unsafe-io'
has caused the Debian Bug report #647402,
regarding live-build: Check version of dpkg before activating 'unsafe-io'
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
647402: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647402
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: live-build
Version: 3.0
Severity: normal
Tags: patch
-- System Information:
Debian Release: squeeze/sid
APT prefers natty-updates
APT policy: (500, 'natty-updates'), (500, 'natty-security'), (500, 'natty')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.38-12-generic (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
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
See https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/882670
--- End Message ---
--- Begin Message ---
On 11/02/2011 11:05 AM, Neil Wilson wrote:
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
first, let me reassure that there's no contra-ubuntu attitude here and
we encourage people from debian derivatives and forks to use live-build,
it's an important use case for live-build. we also very much welcome
getting things required for derivatives and forks integrated
into/implemented in live-build itself and avoid the need of local
patches by having them all mainlined.
having said that..
* live-build is oriented on debian, means, in general, in order to
not have too much hacks and workarounds for $whatever distribution,
live-build 3.x is targeted for wheezy but providing legacy support
for squeeze. oiow: whatever is necessary in order to make squeeze
and newer distributions work as a build *target*, we make sure it's
in live-build. see also http://live.debian.net/project/lifespan/
(to avoid misunderstandings, that is unrelated to the build *host*
requirements, that is, still, supposedly to be any linux-2.6 based
distribution.)
* since most people working on live-build are building debian or
derivatives, and we ourselfs don't test live-build regularily for
building ubuntu, we relay on people using/from ubuntu to send
patches. that means, ubuntu support in live-build is from a debian
point of view 'best effort'.
* lucid, although being as a LTS release still supported until april
2015, it's not the default ubuntu release in live-build 3.x
(that being oneiric atm).
* ubuntu switched to use live-build as of oneiric, for any previous
release, the official build method is to use livecd-rootfs,
therefore, eventhough it might look stupid to not apply such a two line
patch, i prefere to keep being able to draw the clear line of 'squeeze
and newer'.
Regards,
Daniel
--
Address: Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email: [email protected]
Internet: http://people.progress-technologies.net/~daniel.baumann/
--- End Message ---
