[yocto] do_rootfs fails, dpkg host dependency

[Dallas Clement]

Pls disregard.   Something got wonked in my build dir.  I blew it away
and rebuilt everything.  It finished without errors.

On Mon, Jul 23, 2012 at 11:15 AM, Dallas Clement
<dallas.a.clement at gmail.com> wrote:
> do_rootfs is failing when I try to build core-image-minimal on a
> debian squeeze box.  I am surprised it is trying to do something that
> requires root privilege on the host.  Any ideas on how to get past
> this?
>
> NOTE: package core-image-minimal-1.0-r0: task do_rootfs: Started
> ERROR: Function failed: do_rootfs (see
> /development/dallasc/yocto/poky/build/tmp/work/qemuarmada_xp-marvell-linux-gnueabi/core-image-minimal-1.0-r0/temp/log.do_rootfs.9196
> for further information)
> ERROR: Logfile of failure stored in:
> /development/dallasc/yocto/poky/build/tmp/work/qemuarmada_xp-marvell-linux-gnueabi/core-image-minimal-1.0-r0/temp/log.do_rootfs.9196
> Log data follows:
> | ERROR: Function failed: do_rootfs (see
> /development/dallasc/yocto/poky/build/tmp/work/qemuarmada_xp-marvell-linux-gnueabi/core-image-minimal-1.0-r0/temp/log.do_rootfs.9196
> for further information)
> | dpkg-scanpackages: info: Wrote 7 entries to output Packages file.
> | dpkg-scanpackages: info: Wrote 1306 entries to output Packages file.
> | dpkg-scanpackages: info: Wrote 21 entries to output Packages file.
> | dpkg-scanpackages: info: Wrote 7 entries to output Packages file.
> | cat: /development/dallasc/yocto/poky/build/tmp/sysroots/x86_64-linux/etc/apt/apt.conf.sample:
> No such file or directory
> | E: Could not open lock file /var/lib/apt/lists/lock - open (13
> Permission denied)
> | E: Unable to lock the list directory
> | E: Could not open lock file /var/lib/dpkg/lock - open (13 Permission denied)
> | E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?
> NOTE: package core-image-minimal-1.0-r0: task do_rootfs: Failed
> ERROR: Task 8 (/home/dallasc/development/yocto/poky/meta/recipes-core/images/core-image-minimal.bb,
> do_rootfs) failed with exit code '1'