Changeset 9f5dcb97 for general/prog

Timestamp:

03/16/2018 11:59:47 PM (6 years ago)

Author:

Bruce Dubbs <bdubbs@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

2fb1e2b

Parents:

c0ee00e

Message:

Update to cryptsetup-2.0.2.
Update to mercurial-4.5.2.
Update to exempi-2.4.5.
Update to nspr-4.19.

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@19961 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:

• general/prog/mercurial.xml (modified) (2 diffs)

general/prog/mercurial.xml

@@ -7 +7 @@
   <!ENTITY mercurial-download-http "https://www.mercurial-scm.org/release/mercurial-&mercurial-version;.tar.gz">
   <!ENTITY mercurial-download-ftp  " ">
-  <!ENTITY mercurial-md5sum        "5ca07ebb0c7f7eeb7b5a8ca9822cb8f1">
-  <!ENTITY mercurial-size          "5.6 MB">
-  <!ENTITY mercurial-buildsize     "52 MB (add 523 MB for tests)">
+  <!ENTITY mercurial-md5sum        "35ff3213307420f5615d4ac7139537cd">
+  <!ENTITY mercurial-size          "5.5 MB">
+  <!ENTITY mercurial-buildsize     "52 MB (add 3 MB for tests)">
   <!ENTITY mercurial-time          "0.2 SBU (add 6.2 SBU for tests using -j4)">
 ]>
@@ -121 +121 @@
 
     <para>where <replaceable>&lt;N&gt;</replaceable> is an integer between one
-    and the number of ( processor X threads ), inclusive. One test, 
-    test-gpg.t, fails if <xref linkend="gnupg2"/> is not installed. In order to
-    investigate any other apparently failing tests, you may use the
+    and the number of ( processor X threads ), inclusive. One test, test-gpg.t,
+    fails if <xref linkend="gnupg2"/> is not installed. One other test,
+    test-bundle2-exchange.t, is known to fail.  In order to investigate any
+    other apparently failing tests, you may use the
     <command>run-tests.py</command> script. To see the almost forty switches,
-    some of them very useful, issue <command>tests/run-tests.py --help</command>.
-    Running the following commands, you will execute only the tests that failed
-    before:</para>
+    some of them very useful, issue <command>tests/run-tests.py
+    --help</command>.  Running the following commands, you will execute only
+    the tests that failed before:</para>
 
 <screen><userinput>pushd tests  &amp;&amp;