FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > ArchLinux > ArchLinux General Discussion

 
 
LinkBack Thread Tools
 
Old 06-17-2012, 07:59 PM
"David C. Rankin"
 
Default makechrootpkg - howto run 'pacman-key --init'?

Guys,

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:

==> Checking runtime dependencies...
==> Installing missing dependencies...
resolving dependencies...
looking for inter-conflicts...

Targets (17): kbproto-1.0.6-1 libjpeg-turbo-1.2.0-2 libx11-1.5.0-1
libxau-1.0.7-1 libxcb-1.8.1-1
libxdmcp-1.1.1-1 pm-quirks-0.20100619-2 polkit-0.105-1
xcb-proto-1.7.1-1 xproto-7.0.23-1
consolekit-0.4.6-4 dbus-glib-0.98-1 dmidecode-2.11-2
eject-2.1.5-7 libusb-compat-0.1.4-1
pm-utils-1.4.1-5 v4l-utils-0.8.8-1

Total Installed Size: 29.00 MiB

Proceed with installation? [Y/n]
(17/17) checking package integrity
[#######################################] 100%
warning: Public keyring not found; have you run 'pacman-key --init'?
error: GPGME error: Inappropriate ioctl for device
<snip same error>
error: GPGME error: Inappropriate ioctl for device
error: dbus-glib: missing required signature
error: libusb-compat: missing required signature
error: eject: missing required signature
error: dmidecode: missing required signature
error: pm-quirks: missing required signature
error: pm-utils: missing required signature
error: polkit: missing required signature
error: xcb-proto: missing required signature
error: xproto: missing required signature
error: libxdmcp: missing required signature
error: libxau: missing required signature
error: libxcb: missing required signature
error: kbproto: missing required signature
error: libx11: missing required signature
error: consolekit: missing required signature
error: libjpeg-turbo: missing required signature
error: v4l-utils: missing required signature
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.
==> ERROR: 'pacman' failed to install missing dependencies.
==> ERROR: Build failed, check /dat_e/ch47/david/build

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.
 
Old 06-17-2012, 08:23 PM
"David C. Rankin"
 
Default 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.
 
Old 06-17-2012, 09:59 PM
Allan McRae
 
Default 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].
 
Old 06-17-2012, 11:39 PM
"David C. Rankin"
 
Default 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.
 
Old 06-18-2012, 04:05 PM
Magnus Therning
 
Default 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:

% 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
 
Old 06-19-2012, 08:13 PM
"David C. Rankin"
 
Default 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.
 
Old 06-19-2012, 08:48 PM
Magnus Therning
 
Default 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] :-)

/M

--
Magnus Therning OpenPGP: 0xAB4DFBA4
email: magnus@therning.org jabber: magnus@therning.org
twitter: magthe http://therning.org/magnus

I invented the term Object-Oriented, and I can tell you I did not have
C++ in mind.
-- Alan Kay
 

Thread Tools




All times are GMT. The time now is 04:44 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org