polystrap: dpkg: error: unable to access dpkg status area: No such file or directory

Geert Stappers <[email protected]>
Newsgroups gmane.linux.debian.devel.embedded
Message-ID <[email protected]>
Hello,

While test driving polystrap did I encount this error message
dpkg: error: unable to access dpkg status area: No such file or directory

To find out what is causing the error did I made these changes

--- a/polystrap
+++ b/polystrap
@@ -142,8 +142,9 @@ for script in $ROOTDIR/var/lib/dpkg/info/*.preinst; do
         fakechroot chroot $ROOTDIR ${script##$ROOTDIR} install
 done

+set -x
 # run dpkg --configure -a twice because of errors during the first run
-fakechroot chroot $ROOTDIR /usr/bin/dpkg --configure -a || fakechroot chroot $ROOTDIR /usr/bin/dpkg --configure -a
+fakechroot chroot $ROOTDIR /usr/bin/dpkg --debug=1 --configure -a || fakechroot chroot $ROOTDIR /usr/bin/dpkg --confi

 # source hooks


The error output again, now in context

I: Preinstall script: debian-sid-armel/var/lib/dpkg/info/util-linux.preinst
I: Preinstall script: debian-sid-armel/var/lib/dpkg/info/vim-common.preinst
I: Preinstall script: debian-sid-armel/var/lib/dpkg/info/vim-runtime.preinst
Leaving 'diversion of /usr/share/vim/vim73/doc/help.txt to /usr/share/vim/vim73/doc/help.txt.vim-tiny by vim-runtime'
Leaving 'diversion of /usr/share/vim/vim73/doc/tags to /usr/share/vim/vim73/doc/tags.vim-tiny by vim-runtime'
+ fakechroot chroot debian-sid-armel /usr/bin/dpkg --debug=1 --configure -a
dpkg: error: unable to access dpkg status area: No such file or directory
+ fakechroot chroot debian-sid-armel /usr/bin/dpkg --configure -a
dpkg: error: unable to access dpkg status area: No such file or directory


What should I do, so that dpkg in the chroot environment
does see the "dpkg status area"?


Groeten
Geert Stappers
Running a build host that is an fairly up-to-date amd64 unstable
-- 
> And is there a policy on top-posting vs. bottom-posting?
Yes.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.