Changeset 28320bf4
- Timestamp:
- 02/02/2016 08:07:17 PM (8 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 7.10, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, nosym, 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:
- 2beaab8
- Parents:
- 3c0eb661
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
general.ent
r3c0eb661 r28320bf4 1 1 <!-- $LastChangedBy$ $Date$ --> 2 2 3 <!ENTITY day "0 1"> <!-- Always 2 digits -->3 <!ENTITY day "02"> <!-- Always 2 digits --> 4 4 <!ENTITY month "02"> <!-- Always 2 digits --> 5 5 <!ENTITY year "2016"> … … 7 7 <!ENTITY copyholder "The BLFS Development Team"> 8 8 <!ENTITY version "&year;-&month;-&day;"> 9 <!ENTITY releasedate "February 1st&year;">9 <!ENTITY releasedate "February 2nd &year;"> 10 10 <!ENTITY pubdate "&year;-&month;-&day;"> <!-- metadata req. by TLDP --> 11 11 <!ENTITY blfs-version "svn"> <!-- svn|[release #] --> -
general/prog/mercurial.xml
r3c0eb661 r28320bf4 5 5 %general-entities; 6 6 7 <!ENTITY mercurial-download-http "http ://mercurial.selenic.com/release/mercurial-&mercurial-version;.tar.gz">7 <!ENTITY mercurial-download-http "https://www.mercurial-scm.org/release/mercurial-&mercurial-version;.tar.gz"> 8 8 <!ENTITY mercurial-download-ftp " "> 9 <!ENTITY mercurial-md5sum " 25b6065487842a7851ba8cfcaa704b1f">10 <!ENTITY mercurial-size "4. 4MB">11 <!ENTITY mercurial-buildsize "5 2 MB (with documentation, additional 297MB for tests)">12 <!ENTITY mercurial-time "less than 0.1 SBU (with documentation, additional 3. 1SBU for tests, using -j8)">9 <!ENTITY mercurial-md5sum "a175ce4f6660d87849589ee7d015db67"> 10 <!ENTITY mercurial-size "4.5 MB"> 11 <!ENTITY mercurial-buildsize "54 MB (with documentation, additional 384 MB for tests)"> 12 <!ENTITY mercurial-time "less than 0.1 SBU (with documentation, additional 3.4 SBU for tests, using -j8)"> 13 13 ]> 14 14 … … 99 99 <screen><userinput>make doc</userinput></screen> 100 100 101 <para>Running the test suite is optional. If there are failures, e.g.102 test-parse-date.t, those tests can be disabled. To test the results in the103 subdiretory <filename class="directory">tests/tmp</filename>, skipping104 failing tests,issue:</para>101 <para>Running the test suite is optional. If some thest fails, it can be 102 disabled. To test the results in the subdiretory <filename 103 class="directory">tests/tmp</filename>, skipping failing tests, 104 issue:</para> 105 105 106 106 <screen><userinput>cat > tests/blacklists/failed-tests << "EOF" … … 108 108 test-convert-svn-source.t 109 109 test-convert-hg-svn.t 110 test-largefiles-update.t111 110 test-gpg.t</literal> 112 111 EOF … … 116 115 117 116 <para>where <replaceable><N></replaceable> is an integer between one 118 and the number of processor threads, inclusive. In order to investigate a 119 particular apparently failing test, e.g <quote>test-parse-date.t</quote>, 120 issue the following commands (notice that omitting <option>--debug</option> 121 sometimes modifies the result):</para> 117 and the number of ( processor X threads ), inclusive. In order to 118 investigate the apparently failing tests, you may use the 119 <command>run-tests.py</command> scrypt. To see the almost forty switches, 120 some of them very useful, issue <command>tests/run-tests.py --help</command>. 121 Running the following commands, you will execute only the tests that failed 122 before:</para> 122 123 123 124 <screen><userinput>pushd tests && 124 125 rm -rf tmp && 125 ./run-tests.py --debug --tmpdir tmp test-parse-date.t && 126 ./run-tests.py --debug --tmpdir tmp \ 127 test-convert-svn-source.t \ 128 test-convert-hg-svn.t \ 129 test-gpg.t && 126 130 popd</userinput></screen> 131 132 <para>Normally, failures will be repeated. However, if you add the switch 133 "--debug" before "--tmpdir", and run again, the failures are gone. Normally, 134 from now on, there will be no more failure whether you use the debug switch 135 or not. An interesting switch is "--time", which will generated at the end 136 of the test suite execution, a table with all executed tests and respective 137 start, end, user, system and real times. Notice that the switches may be 138 used with <command>make check</command>, in the 139 <envar>TESTFLAGS</envar> environment variable.</para> 127 140 128 141 <para>Install <application>Mercurial</application> by running the following … … 160 173 161 174 <para> 162 <filename>/etc/mercurial/hgrc</filename> 175 <filename>/etc/mercurial/hgrc</filename> and 176 <filename>~/.hgrc</filename> 163 177 </para> 164 178 … … 166 180 <primary sortas="e-etc-mercurial-hgrc">/etc/mercurial/hgrc</primary> 167 181 </indexterm> 182 183 <indexterm zone="mercurial mercurial-config"> 184 <primary sortas="e-AA.hgrc">~/.hgrc</primary> 185 </indexterm> 186 187 <para> 188 A great majority of extensions are disabled by default. Run <command>hg 189 help extensions</command> if you need to enable any, e.g. when 190 investigating test failures, and use one of the configuration files to 191 enable it. 192 </para> 168 193 169 194 <para> -
introduction/welcome/changelog.xml
r3c0eb661 r28320bf4 44 44 45 45 --> 46 47 <listitem> 48 <para>February 2nd, 2016</para> 49 <itemizedlist> 50 <listitem> 51 <para>[fernando] - Update to mercurial-3.7. Fixes 52 <ulink url="&blfs-ticket-root;7420 ">#7420 </ulink>.</para> 53 </listitem> 54 </itemizedlist> 55 </listitem> 46 56 47 57 <listitem> -
packages.ent
r3c0eb661 r28320bf4 274 274 <!ENTITY llvm-version "3.7.1"> 275 275 <!ENTITY lua-version "5.3.2"> 276 <!ENTITY mercurial-version "3. 6.3">276 <!ENTITY mercurial-version "3.7"> 277 277 <!ENTITY nasm-version "2.11.08"> 278 278 <!ENTITY npapi-sdk-version "0.27.2">
Note:
See TracChangeset
for help on using the changeset viewer.