Changeset e43a4270


Ignore:
Timestamp:
08/13/2021 07:39:02 PM (3 years ago)
Author:
Bruce Dubbs <bdubbs@…>
Branches:
11.0, 11.1, 11.2, 11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, 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:
51a7abb7
Parents:
decb4415
Message:

Update to LVM2-2.03.13.

Files:
3 edited

Legend:

Unmodified
Added
Removed
  • introduction/welcome/changelog.xml

    rdecb4415 re43a4270  
    4545      <para>August 13th, 2021</para>
    4646      <itemizedlist>
     47        <listitem>
     48          <para>[bdubbs] - Update to LVM2-2.03.13. Fixes
     49          <ulink url="&blfs-ticket-root;15383">#15383</ulink>.</para>
     50        </listitem>
    4751        <listitem>
    4852          <para>[renodr] - Update to epiphany-40.3. Fixes
  • packages.ent

    rdecb4415 re43a4270  
    4545<!ENTITY fuse3-version                "3.10.4">
    4646<!ENTITY jfsutils-version             "1.1.15">
    47 <!ENTITY lvm2-version                 "2.03.12">
     47<!ENTITY lvm2-version                 "2.03.13">
    4848<!ENTITY mdadm-version                "4.1">
    4949<!ENTITY ntfs-3g-version              "2017.3.23">
  • postlfs/filesystems/lvm2.xml

    rdecb4415 re43a4270  
    77  <!ENTITY lvm2-download-http "https://sourceware.org/ftp/lvm2/LVM2.&lvm2-version;.tgz">
    88  <!ENTITY lvm2-download-ftp  "ftp://sourceware.org/pub/lvm2/LVM2.&lvm2-version;.tgz">
    9   <!ENTITY lvm2-md5sum        "ae295a6ecfeaf67a1dd795723fd227f6">
     9  <!ENTITY lvm2-md5sum        "c4be18fcb94c84c26f71ff4235917c28">
    1010  <!ENTITY lvm2-size          "2.5 MB">
    11   <!ENTITY lvm2-buildsize     "37 MB (add 27 MB for tests; transient files can grow up to around 800 MB in the /tmp directory during tests)">
     11  <!ENTITY lvm2-buildsize     "37 MB (add 18 MB for tests; transient files can grow up to around 800 MB in the /tmp directory during tests)">
    1212  <!-- My build size was 124 MB with tests, but I'll leave this here. -renodr
    1313       The files in /tmp are transient. I monitor /tmp with a loop during
    1414       tests. -pierre, August 2020 -->
    15   <!ENTITY lvm2-time          "0.2 SBU (using parallelism=4; add 16 to 48 SBU for tests, depending on disk speed)">
     15  <!ENTITY lvm2-time          "0.2 SBU (using parallelism=4; add 9 to 48 SBU for tests, depending on disk speed)">
    1616]>
    1717
     
    123123    &lt;*/M&gt;   Snapshot target                               [CONFIG_DM_SNAPSHOT]
    124124    &lt;*/M&gt;   Thin provisioning target                      [CONFIG_DM_THIN_PROVISIONING]
     125    &lt;*/M&gt;   Cache target (EXPERIMENTAL)                   [CONFIG_DM_CACHE]
    125126    &lt;*/M&gt;   Mirror target                                 [CONFIG_DM_MIRROR]
     127    &lt;*/M&gt;   Zero target                                   [CONFIG_DM_ZERO]
     128    &lt;*/M&gt;   I/O delaying target                           [CONFIG_DM_DELAY]
     129  [*] Block devices ---&gt;
     130    &lt;*/M&gt;   RAM block device support                      [CONFIG_BLK_DEV_RAM]
    126131Kernel hacking ---&gt;
    127132  Generic Kernel Debugging Instruments ---&gt;
     
    199204    <para>
    200205      The tests do not implement the <quote>expected fail</quote> possibility,
    201       and a small number of test failures is expected by upstream. More
    202       failures may happen because some kernel options are missing. For example,
    203       the lack of the <emphasis>dm-delay</emphasis> device mapper target may
    204       explain some failures. Some tests are flagged
    205       <quote>warned</quote> if
     206      and a small number of test failures is expected by upstream.
     207      <!-- 1 -->More failures may happen because some kernel options are missing.
     208      For example, the lack of the <emphasis>dm-delay</emphasis> device
     209      mapper target  explains some failures.
     210      <!-- 2 -->Some tests may fail if there is insufficient free space available
     211      in the partition with the /tmp directory.  At least one test fails if 16 TB
     212      is not available.
     213      <!-- 3 -->Some tests are flagged  <quote>warned</quote> if
    206214      <ulink url='https://github.com/jthornber/thin-provisioning-tools'>
    207215      thin-provisioning-tools</ulink> are not installed. A workaround is to
     
    227235
    228236      <note><simpara>The checks create device nodes in the /tmp directory.  The
    229       tests will fail if /tmp is mounted with the nodev
    230       option.</simpara></note>
     237      tests will fail if /tmp is mounted with the nodev option.
     238      </simpara></note>
    231239    </para>
    232240
Note: See TracChangeset for help on using the changeset viewer.