Arch Linux User Repository

This PKGBUILD verifies the authenticity of the source via PGP signatures which are not part of the Arch Linux keyring. In order to complete the process it is necessary to import the key(s) from the ‘validpgpkeys’ array into the user’s keyring before calling makepkg. There is a helpful article explaining this process by one of Arch Linux's developers located here: http://allanmcrae.com/2015/01/two-pgp-keyrings-for-package-management-in-arch-linux/

Instructions on importing keys from a keyserver and how to automate the retrieval process can be found in the Arch Linux wiki here: https://wiki.archlinux.org/index.php/GnuPG#Use_a_keyserver This article also contains helpful information describing the installation of GnuPG, its configuration and usage.

Execute the following to import keys using gpg:

gpg --recv-keys <KEYID - See 'validpgpkeys' array in PKGBUILD>

The PGP signature check can be skipped by passing --skippgpcheck to makepkg.

Consult the makepkg manual page for a full list of options. [https://www.archlinux.org/pacman/makepkg.8.html]

StefanMajonez:The pacman keyring and your personal gpg keyring are two different things as explained in the two keyring article in the pinned post. The error you're receiving is because gpg can't reach a keyserver. Check out dirmngr and ~/.gnupg/gpg.conf and have a look at the keyserver entries to ensure that the basics are in order. One of them needs to be uncommented and there are alternatives if you can't reach that one. I've had little trouble with: keyserver hkp://keys.gnupg.net Check the GnuPG article in the wiki for more information about keyservers. The green /tip/ box contains some especially helpful tidbits on configuring gpg.

Hi! I have a problem which probably stems from my lack of Linux understanding, but it took me +2 hours to try to find a solution and so I decided to post a comment. When trying to make: One or more PGP signatures could not be verified! Inputting gpg --recv-keys 1DCF2659 gives me this: gpg: keyserver receive failed: No keyserver available I downloaded and signed the key using pacman-key, didn't help.

oi_wtf: It's what I'm here for. Glad it is working for you as well.

thanks. build works now.

It appears as though I've located the missing dependencies and included them where appropriate. I am able to build this package in an initial pacstrap of base and base-devel after enabling multilib to satisfy dependencies from the repo and building lib32-libical. I'll have the package updated shortly. UPDATE: All my local build tests are complete and the updated package is now live. Good luck.

I will take a look at this in a clean environment and see if I can't track down the issue you're experiencing. Our builds definitely diverge rather early in the process; however, I'm unsure if this is due to missing dependencies or something less transparent. While our configure outputs are identical your build is reaching profiles/sap/bluetoothd-sap-dummy.o and crashing quite early where as on my local system it builds a great many other pieces before reaching the same point. It is possible it is skipping those components because of a missing dependency. It is just as likely to be something else simple as well or a complicated mess neither of us has imagined yet. If you could edit the PKGBUILD to disable parallel building by suffixing the make command in build() with -j1 I'd appreciate the additional test data to eliminate other possibilities. EDIT: I seem to have produced a complaint about something missing by the linker in one test. Investigating further. I've succeeded in reproducing the error and generated an identical build output. I'll see if I can't track down what is broken or missing and get it mended. Thanks for finding the issue. UPDATE: As this package is derived from the bluez split package in the extra repo I'm going to investigate to see if the error is shared between them. RESULTS: As I expected bluez from the extra repos builds just fine. This is likely because all of its requirements are met by a basic pacstrap of base and base-devel. I suspect this will narrow my search quite a bit to one of the core glibc components in lib32 that isn't getting pulled in but should likely exist before building any lib32 package.

It fails to build in a clean chroot. Probably because some dependency is missing. Could you look into it? Buildlog: https://ptpb.pw/g1QB

This PKGBUILD verifies the authenticity of the source via PGP signatures which are not part of the Arch Linux keyring. In order to complete the process it is necessary to import the key(s) from the ‘validpgpkeys’ array into the user’s keyring before calling makepkg. There is a helpful article explaining this process by one of Arch Linux's developers located here: http://allanmcrae.com/2015/01/two-pgp-keyrings-for-package-management-in-arch-linux/

Instructions on importing keys from a keyserver and how to automate the retrieval process can be found in the Arch Linux wiki here: https://wiki.archlinux.org/index.php/GnuPG#Use_a_keyserver This article also contains helpful information describing the installation of GnuPG, its configuration and usage.

Execute the following to import keys using gpg:

gpg --recv-keys <KEYID - See 'validpgpkeys' array in PKGBUILD>

The PGP signature check can be skipped by passing --skippgpcheck to makepkg.

Consult the makepkg manual page for a full list of options. [https://www.archlinux.org/pacman/makepkg.8.html]