Closed denisse-dev closed 4 years ago
The problem was that I need a GPG key on the machine where I want to install SELinux, the test proceeds to sign a commit with that GPG key and then it continues without issues.
I don't think we should have this test as mandatory as you may want to install SELinux in a machine that doesn't have a GPG key, but maybe I'm wrong.
Should this test be skipped or should I document that this is required in the Arch Wiki?
Hello, the test succeeds on my test virtual machine that has no GPG key, and the source code of the failing test does not invoke GPG, and : https://git.savannah.gnu.org/cgit/gnulib.git/tree/tests/test-vc-list-files-git.sh?id=1968c439d9077a1b5a846a86b98b1a5e60e0ed08
This test creates a git commit, and if your git configuration includes git config commit.gpgsign
, creating a git commit would require a GPG key to sign it.
Did you modify the ~/.gitconfig
of the user that builds packages? Do you build packages using a clean chroot
-ed environment?
You're right @fishilico ! After using a clean chroot
the problem is no longer present, it was a conflicting .gitconfig
.
Thank you!
When attempting to install SELinux using the
linux-zen
kernel thetest-vc-list-files-git.sh
fails, these are the contents ofgnulib-tests/test-suite.log
: