Changes in postlfs/security/nss.xml [88fdf09:f59814c]

File:

• postlfs/security/nss.xml (modified) (9 diffs)

postlfs/security/nss.xml

@@ -12 +12 @@
 
 <!-- no micro versions -->
-<!ENTITY nss-download-http "https://&nss-url;/NSS_3_&nss-minor-version;_RTM/src/nss-&nss-version;.tar.gz">
+  <!ENTITY nss-download-http "https://&nss-url;/NSS_3_&nss-minor-version;_RTM/src/nss-&nss-version;.tar.gz">
 
   <!ENTITY nss-download-ftp  " ">
-  <!ENTITY nss-md5sum        "df451e99d09589da6c3d4f103de877bc">
-  <!ENTITY nss-size          "79 MB">
-  <!ENTITY nss-buildsize     "305 MB (add 122 MB for tests)">
-  <!ENTITY nss-time          "5.8 SBU (with parallelism=4, add 17 SBU for tests)">
+  <!ENTITY nss-md5sum        "afbbb03ae4034a55d28de658ba4e18ff">
+  <!ENTITY nss-size          "78 MB">
+  <!-- 50 MB increase is due to new test files, see #12187 -->
+  <!ENTITY nss-buildsize     "294 MB (add 139 MB for tests)">
+  <!ENTITY nss-time          "2.6 SBU (with parallelism=4, add 24 SBU for tests)">
 ]>
 
@@ -25 +26 @@
 
   <sect1info>
+    <othername>$LastChangedBy$</othername>
     <date>$Date$</date>
   </sect1info>
@@ -47 +49 @@
     </para>
 
-    &lfs110a_checked;
+    &lfs10_checked;
 
     <bridgehead renderas="sect3">Package Information</bridgehead>
@@ -118 +120 @@
          for more information. -->
 
-    <!-- And with another rebuild of nss-3.54, all is well again, but broken in 3.60 -->
-    <!-- fixed again in 3.62
+    <!-- And with another rebuild of nss-3.54, all is well again
     <note>
       <para>
         This package does not support parallel build.
       </para>
-    </note>-->
+    </note>
+   -->
 
     <para>
@@ -134 +136 @@
 cd nss &amp;&amp;
 
-make BUILD_OPT=1                  \
+make BUILD_OPT=1                      \
   NSPR_INCLUDE_DIR=/usr/include/nspr  \
   USE_SYSTEM_ZLIB=1                   \
@@ -144 +146 @@
     <para>
       <!-- the unittest files get compiled automatically since nss-3.31.0 -->
-      To run the tests, execute the following commands (1 test is known to fail):
+      <!-- The unit tests were run during the build.-->
+      To run the tests, execute the following commands:
     </para>
 
 <screen remap="test"><userinput>cd tests &amp;&amp;
-HOST=localhost DOMSUF=localdomain ./all.sh
+HOST=localhost DOMSUF=localdomain ./all.sh &amp;&amp;
 cd ../</userinput></screen>
     
-    <note>  
-      <para>Some information about the tests:</para>
-      <itemizedlist spacing="compact">
-      <listitem>
-        <para>
-           HOST=localhost and DOMSUF=localdomain are required 
-           Without these variables, a FQDN is
-           required to specified and this generic way should work for
+    <!--   Some information about the tests:
+         - HOST=localhost and DOMSUF=localdomain require the changes done to
+           /etc/hosts in r11892 (LFS). Without these variables, a FQDN is
+           required to specified, and this generic way should work for
            everyone.
-        </para>
-      </listitem>
-      <listitem>
-        <para>
-           The tests take an extremely long time to run. If desired there is
-           information in the all.sh script about running subsets of the 
-           total test suite.
-        </para>
-      </listitem>
-      <listitem>
-        <para>
-           When interrupting the tests, the test suite
+         - With NSS-3.53, there were 53,866 tests. The tests take an
+           extremely long time to run. 
+         - Another interesting discovery has to do with interrupting the tests.
+           It was discovered that, when interrupting the tests, the test suite
            fails to spin down test servers that are run. This leads to an
            infinite loop in the tests where the test suite tries to kill a server
            that doesn't exist anymore because it pulls the wrong PID.
-        </para>
-      </listitem>
-      <listitem>
-        <para>
-           Test suite results (in HTML format!) can be found at 
-           ../../test_results/security/localhost.1/results.html
-        </para>
-      </listitem>
-      </itemizedlist>
-     </note>
+         - Test suite results (in HTML format!) can be found at 
+           ../../test_results/security/localhost.1/
+     -->
 
     <para>
@@ -327 +311 @@
             or change the password, generate new public and private key pairs,
             display the contents of the key database, or delete key pairs within
-            the key3.db file
+            the key3.db file.
           </para>
           <indexterm zone="nss certutil">
@@ -340 +324 @@
           <para>
             is used to determine the NSS library settings of the installed NSS
-            libraries
+            libraries.
           </para>
           <indexterm zone="nss nss-config">
@@ -354 +338 @@
             is a tool for importing certificates and keys from pkcs #12 files
             into NSS or exporting them. It can also list certificates and keys
-            in such files
+            in such files.
           </para>
           <indexterm zone="nss pk12util">