On Sun, Jun 17, 2012 at 02:59:28PM -0500, David C. Rankin wrote:
Doing a major rebuild with new archroot and I've run into an error either due to needing to run 'pacman-key --init' or due to GPGME -- or both. Do I need to manually chroot the archroot and run pacman-key --init, or can I pass it to the chroot with makechrootpkg -- (some option).
What's the best way to handle this?
After running 'sudo mkarchroot -u $CHROOT/root', when I go to build a package requiring dependencies with 'sudo makechrootpkg -r $CHROOT -u', I get the following:
I've been running into this lately too and the only way I could think of was to manually chroot and run the commands myself: % sudo mkarchroot -r /bin/bash path/to/my/root /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus Perl is another example of filling a tiny, short-term need, and then being a real problem in the longer term. -- Alan Kay