[arch-general] [Solved] Re: difference between arch-nspawn and mkarchroot?

David C. Rankin drankinatty at suddenlinkmail.com
Fri Jan 17 05:42:07 EST 2014


On 01/16/2014 09:12 PM, David C. Rankin wrote:
> ==> ERROR: 'pacman' failed to install missing dependencies.
> ==> ERROR: Build failed, check /dat_e/ch14/david/build
> 
> 
>   The error at issue is: warning: database file for 'local' does not exist,
> however, I have never seen that before. Especially with:
> 
> 21:10 phoinix:/dat_e/tmp> l1 /dat_e/ch14/root/repo/
> apetag-git-1.13-1-x86_64.pkg.tar.xz
> libkarma-0.1.2-1-x86_64.pkg.tar.xz
> libnjb-2.2.7-3-x86_64.pkg.tar.xz
> libutempter-1.1.6-2-x86_64.pkg.tar.xz
> local.db
> local.db.tar.gz
<snip>

It seems the following in $CHROOT/root/etc/pacman.conf

# By default, pacman accepts packages signed by keys that its local keyring
# trusts (see pacman-key and its man page), as well as unsigned packages.
SigLevel    = Required DatabaseOptional
LocalFileSigLevel = Optional

Were preventing the build from seeing the local repository files, because of the
lack of a key on a ring provided by the packages. So to make the build use the
files I had just built, I had to add an option to my local repository definition:

[local]
SigLevel = Never
Server = file:///repo

Now building can resume in a somewhat normal manner - I hope...  Removing all
the content from Building in a Clean Chroot#Handling Major Rebuilds concerning
this process in exchange for the [staging] recipe may not have been a good
trandeoff ;p

-- 
David C. Rankin, J.D.,P.E.


More information about the arch-general mailing list