Thanks, Steve. On Wed, Oct 13, 2010 at 12:45 PM, Steve Langasek <steve.langa...@linaro.org> wrote: > Hi Shawn, > > On Mon, Oct 04, 2010 at 04:20:30PM +0800, Shawn Guo wrote: >> I'm using lp:~linaro-maintainers/linaro/live-helper.config.maverick.headless >> to build the rootfs image for imx51, and running into the following >> problems. > >> - Need --force-yes apt option >> I have to get APT_OPTIONS="--yes --force-yes" in common to keep the >> build going, otherwise it will end up with the following error. >> E: There are problems and -y was used without --force-yes >> Build log is attached for your checking. > > Are you still seeing this problem? From the log, I notice the following: > >> P: Setting up cleanup function >> P: Begin caching bootstrap stage... >> P: Begin bootstrapping system... >> W: skipping bootstrap >> P: Begin caching bootstrap stage... >> P: Begin unmounting filesystems... >> P: Setting up cleanup function >> P: Begin caching chroot stage... > > You appear to have a cached bootstrap result here that lh is using. Is the > problem reproducible after running 'lh clean --all'? > Yes, "lh clean --all" removed the problem.
>> W: GPG error: http://ports.ubuntu.com maverick Release: The following >> signatures couldn't be verified because the public key is not available: >> NO_PUBKEY 40976EAF437D05B5 >> W: GPG error: http://ports.ubuntu.com maverick-security Release: The >> following signatures couldn't be verified because the public key is not >> available: NO_PUBKEY 40976EAF437D05B5 >> W: GPG error: http://ports.ubuntu.com maverick-updates Release: The >> following signatures couldn't be verified because the public key is not >> available: NO_PUBKEY 40976EAF437D05B5 > > This is supposed to be addressed by the inclusion of the ubuntu-keyring > package in the chroot; however, this package is only included by the > 'chroot_sources' script *after* running 'apt-get update; apt-get upgrade', > which means that if the bootstrapped chroot is out of date (for instance, if > you're using a cached chroot), this will fail *before* the keyring package > is installed. > > So clearing out your cache will probably fix this problem for you. > That's because I'm behind a proxy. And the http_proxy setting in my shell does not work for sudo context. I have to do following to fix it. - sudo bash - export http_proxy=...... - lh build >> - OMAP build binding >> The current config is binding to OMAP build without hwpack. What is >> the plan to support hwpack build and other platforms like imx51 as far >> as I'm concerned right now? > > I believe that's been addressed now :) > I have seen that. Thanks. -- Regards, Shawn _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
