Arch Linux User Repository

Since the openpgp.org keyserver does not provide identity information for keys that don't have a verified email address as stated on their FAQ, and the arch gnupg package doesn't have a patch for that applied like other distributions, one has to import the key from another keyserver, with e.g.:

gpg --keyserver hkps://keyserver.ubuntu.com --recv-keys 258B6EFA0F209D24

I might contact the upstream maintainer about this issue as they just have to use another key for signing (the one searchable using their email address on keys.openpgp.org) or verify the key used for the package.

@vanyasem and @all: This is my build log

https://pastebin.com/5FnRWQt8

Can you please point out where your issue with root password would show up in this process?

Could it be an issue with upstream in their makefile?

$ grep -ri groupadd
stapbpf/Makefile.am:                             || groupadd -f -g 156 -r stapusr); then \
stapbpf/Makefile.in:@HAVE_BPF_DECLS_TRUE@                                || groupadd -f -g 156 -r stapusr); then \
staprun/Makefile.am:                             || groupadd -f -g 156 -r stapusr); then \
staprun/Makefile.in:                             || groupadd -f -g 156 -r stapusr); then \
systemtap.spec:getent group stapusr >/dev/null || groupadd -f -g 156 -r stapusr
systemtap.spec:getent group stapsys >/dev/null || groupadd -f -g 157 -r stapsys
systemtap.spec:getent group stapdev >/dev/null || groupadd -f -g 158 -r stapdev
systemtap.spec:getent group stap-server >/dev/null || groupadd -f -g 155 -r stap-server

@vanyasem: I'm not refusing to patch this... Can you please a bit less aggressive? Or better yet, be a responsible community member and submit a PR.

https://lists.archlinux.org/pipermail/aur-requests/2019-December/035453.html

I'm checking why this is happening, though.

During build, this package is calling groupadd, leading to asking my root password. That wasn't supposed to happen, building some package shouldn't interfere with your real system, nor play with groups/users (when this is needed, it's added to .install).

copied from systemtap-git

could you address that with a patch maybe?

Adopted the package and updated to 4.1. As upstream's configure doesn't support to exclude SDT headers, I did the ugly way and rm -r them before packaging. So far, it works, but it may have issues.

I won't be able to maintain this for the foreseeable future.

[core]/glibc has SDT headers installed now, which intorduce a conflict with systemtap

@perqin

==> Verifying source file signatures with gpg... systemtap-4.0.tar.gz ... FAILED (unknown public key 7E83610126DCC2E8) ==> ERROR: One or more PGP signatures could not be verified!

$ gpg --receive-keys 7E83610126DCC2E8

==> Verifying source file signatures with gpg...
    systemtap-4.0.tar.gz ... FAILED (unknown public key 7E83610126DCC2E8)
==> ERROR: One or more PGP signatures could not be verified!

I needed to install "python-setuptools" (python3 version) to successfully build this package