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:
The GPGME error is one I haven't encountered before, I'm not sure what to do
with that one. For the missing required signature errors, I have tried setting
SigLevel = Never, but same result. What say the experts? Let me know what you
think and I'll update the DeveloperWiki:Building in a Clean Chroot page.
--
David C. Rankin, J.D.,P.E.
06-17-2012, 08:23 PM
"David C. Rankin"
makechrootpkg - howto run 'pacman-key --init'?
On 06/17/2012 02:59 PM, David C. Rankin wrote:
> Proceed with installation? [Y/n]
> (17/17) checking package integrity
> [#######################################] 100%
> warning: Public keyring not found; have you run 'pacman-key --init'?
As a workaround, I just copied /etc/pacman.d/gnupg into the chroot pacman.d dir
and that eliminated the 'warning' above. However, all of the errors remained. I
have built everything I'm trying to build before, but not in a brand new
archroot since the last pacman update. I've checked the developer wiki and I
don't find anything new. What am I missing? Thanks for any help you can give.
--
David C. Rankin, J.D.,P.E.
06-17-2012, 09:59 PM
Allan McRae
makechrootpkg - howto run 'pacman-key --init'?
On 18/06/12 06:23, David C. Rankin wrote:
> On 06/17/2012 02:59 PM, David C. Rankin wrote:
>> Proceed with installation? [Y/n]
>> (17/17) checking package integrity
>> [#######################################] 100%
>> warning: Public keyring not found; have you run 'pacman-key --init'?
>
> As a workaround, I just copied /etc/pacman.d/gnupg into the chroot pacman.d dir
> and that eliminated the 'warning' above. However, all of the errors remained. I
> have built everything I'm trying to build before, but not in a brand new
> archroot since the last pacman update. I've checked the developer wiki and I
> don't find anything new. What am I missing? Thanks for any help you can give.
>
Use devtools from [testing].
06-17-2012, 11:39 PM
"David C. Rankin"
makechrootpkg - howto run 'pacman-key --init'?
On 06/17/2012 04:59 PM, Allan McRae wrote:
> Use devtools from [testing].
Thanks Allan
--
David C. Rankin, J.D.,P.E.
06-18-2012, 04:05 PM
Magnus Therning
makechrootpkg - howto run 'pacman-key --init'?
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:
Perl is another example of filling a tiny, short-term need, and then
being a real problem in the longer term.
-- Alan Kay
06-19-2012, 08:13 PM
"David C. Rankin"
makechrootpkg - howto run 'pacman-key --init'?
On 06/18/2012 11:05 AM, Magnus Therning wrote:
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
Thanks Magnus!
Looks like the Arch wizards solved this in the updates today. Created a new
chroot mkarchroot V2 and kicked off the trinity build in the chroot with gcc
4.7.1 and it is churning away. So from what I can tell, all issues are solved.
I didn't have any pacmankey --init issues and all ioctl device errors are gone.
Great job wizards!
--
David C. Rankin, J.D.,P.E.
06-19-2012, 08:48 PM
Magnus Therning
makechrootpkg - howto run 'pacman-key --init'?
On Tue, Jun 19, 2012 at 03:13:52PM -0500, David C. Rankin wrote:
>On 06/18/2012 11:05 AM, Magnus Therning wrote:
>>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
>
>Thanks Magnus!
>
>Looks like the Arch wizards solved this in the updates today.
>Created a new chroot mkarchroot V2 and kicked off the trinity build
>in the chroot with gcc 4.7.1 and it is churning away. So from what I
>can tell, all issues are solved. I didn't have any pacmankey --init
>issues and all ioctl device errors are gone.
That's great to hear, then I can stop worrying about any issues for
new users of the build-in-chroot scripts used to build [haskell] :-)
makechrootpkg - howto run 'pacman-key --init'?
