Re: lb build stop after setting up the dctrl-tools package

[chals <chals@chalsattack.com>]

On Thu, Dec 4, 2014 at 9:25 AM, Atar <atar.yosef@gmail.com> wrote:
> Hi there!
>
> I try to build a wheezy live system from within my wheezy distro and when I
> run the "lb build" command the build process is stopped after it sets up the
> dctrl-tools. it doesn't emit any error message. I've attached here
> (http://pastebin.com/WunNPBtH) the auto/config and the build.log files and
> will be happy if someone here can help me figure out what's the problem.
>

Hi,

Sometimes it is really hard to tell why a build process fails.
However, I found too many "inconsistencies" in your configuration
which could be the reason for your problem. This is usually caused by
an unclean build environment. So the logical step would be to run a

 # lb clean

and then try to build again

 # lb build

Or you could also start your build system in a brand new directory (up
to you to decide).

The inconsistencies I'm talking about are, for example:

In your auto/config you have (I copy and paste just part of it):

--cache-indices true \
--debug \

BUT your config/common says:


config/common: # $LB_CACHE_INDICES: control if downloaded package
indices should be cached
config/common: # (Default: false)
config/common: LB_CACHE_INDICES="false"

OR

config/common: # $_DEBUG: enable debug
config/common: # (Default: false)
config/common: #_DEBUG="false"


Hence I supposed you were "re-using" your build system after changing
some variables. Not a good idea :)

Apart from that, in your auto/config, most of your options are already
defaults, so you do not need to set them, since live-build already
does it for you. These are all defaults:

--binary-images iso-hybrid \
--chroot-filesystem squashfs \
--apt-recommends true \
--bootloader syslinux \
[...]
--firmware-chroot true \
--updates true \
--backports true \
--system live \

Cleaning your auto scripts is a good idea because it helps you
identify your failing cases faster and more easily for you and for
everybody else.

Also, I noticed you are using live-build 4.0.3-1. I haven't tried to
build wheezy with this version, but I guess there should be no problem
with that. But again, I haven't tried it.

So please, revise your config and start again from a clean state and
see if you succeed.

Good luck.

-- 
chals
www.chalsattack.com
chals@chalsattack.com