@vanyasem and @all: This is my build log
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
Pinned Comments
SunRed commented on 2024-04-24 16:31 (UTC) (edited on 2024-04-24 16:32 (UTC) by SunRed)
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.:
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.