[blfs] branch trunk updated: keyutils: fix the test suite for recent File update and add back the known failure

This is an automated email from the git hooks/post-receive script.

git pushed a commit to branch trunk
in repository blfs.

The following commit(s) were added to refs/heads/trunk by this push:
     new 7e906bb6cb keyutils: fix the test suite for recent File update and add back the known failure
7e906bb6cb is described below

commit 7e906bb6cb2febbd51cb6364045f53502741116f
Author: Xi Ruoyao <[email protected]>
AuthorDate: Mon Jul 27 11:07:24 2026 +0800

    keyutils: fix the test suite for recent File update and add back the known failure
    
    Found a clue about the failure reported by renodr in the upstream repo.
---
 general/genlib/keyutils.xml | 28 ++++++++++++++++------------
 1 file changed, 16 insertions(+), 12 deletions(-)

diff --git a/general/genlib/keyutils.xml b/general/genlib/keyutils.xml
index 77478e6711..eaa81fadf9 100644
--- a/general/genlib/keyutils.xml
+++ b/general/genlib/keyutils.xml
@@ -108,32 +108,36 @@
 
 <screen role="root"><userinput>make NO_ARLIB=1 LIBDIR=/usr/lib BINDIR=/usr/bin SBINDIR=/usr/sbin install</userinput></screen>
 
+    <!-- With 5.48, file -L /proc/$$/exe returns "Permission denied,"
+         perhaps some hardening? -->
     <para>
       The test suite can only run after installing this package.
+      A support file in the test suite needs to be adapted for
+      <application>File</application> 5.48 or newer.
       To test the results, issue, as the
       <systemitem class="username">root</systemitem> user:
     </para>
 
-<screen role="root" remap="test"><userinput>make -k test</userinput></screen>
+<screen role="root" remap="test"><userinput>sed 's/\$\$/self/' -i tests/toolbox.inc.sh &amp;&amp;
+make -k test</userinput></screen>
 
+    <!-- The kernel needs to invoke /sbin/request-key sometimes, so
+    running the test suite in a chroot environment will actually test
+    the host distro's request-key program.  Just don't do that. -->
     <para>
       If <xref linkend='lsb-tools'/> is not installed, the test suite will
       output some lines complaining the <command>lsb_release</command>
       command is not available but it won't affect the test result. The tests
       do not work in a chroot environment.
-      <!-- The kernel needs to invoke /sbin/request-key sometimes, so
-      running the test suite in a chroot environment will actually test
-      the host distro's request-key program.  Just don't do that.
-
-      The tests are currently known to fail once it attempts to add user-generated keys
-      to the keyring.
-      I did verify that this occurs on other distros as well, and it seems
-      to be known at Gentoo.
-
-      Is this still a issue if we rule out running the test suite in
-      chroot? -->
     </para>
 
+    <!-- see upstream commit c076dff259e9 -->
+    <para>
+      The tests are currently known to fail once it attempts to add
+      user-generated keys to the keyring if
+      <option>CONFIG_SYSTEM_BLACKLIST_AUTH_UPDATE</option> is enabled in
+      the configuration of the currently running kernel.
+    </para>
   </sect2>
 
   <sect2 role="commands">

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.

-- 
http://lists.linuxfromscratch.org/sympa/info/blfs-book
Unsubscribe: See the above information page