Bug#1005622: [Pkg-utopia-maintainers] Bug#1005622: libblockdev: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below
Hi, Sorry for the symlink breakage. On Mon, Feb 14, 2022 at 6:54 PM Michael Biebl wrote: > While speaking of getting rid off unnecessary complexity: Is the > separate udeb build still needed? This is what I sometimes decide to evaluate, but then time goes on something else. :( Now I'm going to upload Helmut's fix, thanks for that! Regards, Laszlo/GCS
Bug#1005622: [Pkg-utopia-maintainers] Bug#1005622: libblockdev: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below
Am 14.02.22 um 18:51 schrieb Michael Biebl: I agree. Apparently this isn't the first time that dmraid has been bitten by this split-usr issue (and having to manually fiddle with the creation of the .so symlink) [1] Getting rid of this unnecessary complexity would solve this once and for all. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856946 While speaking of getting rid off unnecessary complexity: Is the separate udeb build still needed? Apparently dmraid doesn't link against libselinux anymore (and even if it did, we do have a libselinux udeb nowadays) Michael OpenPGP_signature Description: OpenPGP digital signature
Bug#1005622: [Pkg-utopia-maintainers] Bug#1005622: libblockdev: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below
Am 14.02.22 um 17:55 schrieb Helmut Grohne: We have this moratorium in place that says you should not move files from / to /usr, because it could go bad when moving files. ttbomk, those "bad" things only happen if you move files from /lib to /usr (under the same name) but *also* move it between different binary packages, which isn't the case here. However, in this case, we are moving files from non-triplet to triplet and thus we can safely move from / to /usr without the aforementioned risk. So we may want to go the extra mile here and use the multiarch-conversion to move all files to /usr in a safe way for stable upgrades and get rid of a pile of complexity that way. I agree. Apparently this isn't the first time that dmraid has been bitten by this split-usr issue (and having to manually fiddle with the creation of the .so symlink) [1] Getting rid of this unnecessary complexity would solve this once and for all. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856946 OpenPGP_signature Description: OpenPGP digital signature
Bug#1005622: [Pkg-utopia-maintainers] Bug#1005622: libblockdev: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below
Control: tags -1 + patch
Hi Michael,
On Sun, Feb 13, 2022 at 02:20:26PM +0100, Michael Biebl wrote:
> I suspect the following:
>
> in 1.0.0.rc16-10 /usr/lib/libdmraid.so is a dangling symlink to
> /lib/libdmraid.so.1.0.0.rc16 (yay for those pointless split-usr shenanigans,
> can we please have merged-usr like yesterday) and as a result the
> compiler/linker falls back to link
> /usr/lib/x86_64-linux-gnu/libdmraid.a
> statically into libblockdev-dm2
Thank you for the detailed analysis and for contacting me directly. I am
sorry for the inconvenience this bug has caused to you. I usually
double-check these links in a multiarch conversion, but it turns out
that both me and Laszlo missed this instance.
Before blindly applying this patch, let me propose something else:
We have this moratorium in place that says you should not move files
from / to /usr, because it could go bad when moving files. However, in
this case, we are moving files from non-triplet to triplet and thus we
can safely move from / to /usr without the aforementioned risk. So we
may want to go the extra mile here and use the multiarch-conversion to
move all files to /usr in a safe way for stable upgrades and get rid of
a pile of complexity that way.
That's up to Laszlo to decide. In the mean time, here is the patch that
fixes the issue reported by Lucas and diagnosed by Michael. Thank you
two.
Helmut
diff --minimal -Nru dmraid-1.0.0.rc16/debian/changelog
dmraid-1.0.0.rc16/debian/changelog
--- dmraid-1.0.0.rc16/debian/changelog 2022-02-03 17:28:13.0 +0100
+++ dmraid-1.0.0.rc16/debian/changelog 2022-02-14 17:43:28.0 +0100
@@ -1,3 +1,11 @@
+dmraid (1.0.0.rc16-10.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix bad library symlink (closes: #1005622). Thanks to Michael Biebl and
+Lucas Nussbaum.
+
+ -- Helmut Grohne Mon, 14 Feb 2022 17:43:28 +0100
+
dmraid (1.0.0.rc16-10) unstable; urgency=medium
[ Johannes Schauer Marin Rodrigues ]
diff --minimal -Nru dmraid-1.0.0.rc16/debian/libdmraid-dev.links
dmraid-1.0.0.rc16/debian/libdmraid-dev.links
--- dmraid-1.0.0.rc16/debian/libdmraid-dev.links2017-08-30
23:28:37.0 +0200
+++ dmraid-1.0.0.rc16/debian/libdmraid-dev.links2022-02-14
17:41:24.0 +0100
@@ -1 +1,2 @@
-lib/libdmraid.so.1.0.0.rc16 usr/lib/libdmraid.so
+#!/usr/bin/dh-exec
+lib/${DEB_HOST_MULTIARCH}/libdmraid.so.1.0.0.rc16
usr/lib/${DEB_HOST_MULTIARCH}/libdmraid.so
diff --minimal -Nru dmraid-1.0.0.rc16/debian/rules
dmraid-1.0.0.rc16/debian/rules
--- dmraid-1.0.0.rc16/debian/rules 2022-02-03 17:28:13.0 +0100
+++ dmraid-1.0.0.rc16/debian/rules 2022-02-14 17:41:52.0 +0100
@@ -71,7 +71,6 @@
binary-arch: install
dh_testdir
dh_testroot
- chmod +x debian/libdmraid*.install
dh_install
dh_installdirs
dh_installudev --priority=97
Bug#1005622: [Pkg-utopia-maintainers] Bug#1005622: libblockdev: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below
I suspect the following: in 1.0.0.rc16-10 /usr/lib/libdmraid.so is a dangling symlink to /lib/libdmraid.so.1.0.0.rc16 (yay for those pointless split-usr shenanigans, can we please have merged-usr like yesterday) and as a result the compiler/linker falls back to link /usr/lib/x86_64-linux-gnu/libdmraid.a statically into libblockdev-dm2 Am 13.02.22 um 14:13 schrieb Michael Biebl: Control: reassign -1 libdmraid-dev Control: found -1 1.0.0.rc16-10 Control: affects src:libblockdev Reassigning accordingly. Am 13.02.22 um 14:11 schrieb Michael Biebl: Looking at those symbols, they all appear to come from libdmraid and this appears to be an issue caused by dmraid (1.0.0.rc16-10) Building in a sid chroot with libdmraid-dev_1.0.0.rc16-9_amd64.deb and libdmraid1.0.0.rc16_1.0.0.rc16-9_amd64.deb makes the build succeed. So I suspect this breakage was caused by [ Helmut Grohne ] * Fix FTCBFS: Use a multiarch --libdir (closes: #951469). And indeed, reverting that patch from #951469 fixes this issue. Helmut, can you please take care of that? Somehow this change makes those symbols from libdmraid leak into libblockdev-dm2 Thanks, Michael Am 13.02.22 um 08:50 schrieb Lucas Nussbaum: Source: libblockdev Version: 2.26-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220212 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory '/<>' dh_makeshlibs -- -c4 dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libblockdev-dm2/DEBIAN/symbols doesn't match completely debian/libblockdev-dm2.symbols --- debian/libblockdev-dm2.symbols (libblockdev-dm2_2.26-1_amd64) +++ dpkg-gensymbolsnjXTfu 2022-02-12 22:44:06.350039704 + @@ -1,5 +1,23 @@ libbd_dm.so.2 libblockdev-dm2 #MINVER# * Build-Depends-Package: libblockdev-dm-dev + _dbg_free@Base 2.26-1 + _dbg_malloc@Base 2.26-1 + _dbg_realloc@Base 2.26-1 + _dbg_strdup@Base 2.26-1 + _dbg_strndup@Base 2.26-1 + _rebuild_raidset@Base 2.26-1 + add_delimiter@Base 2.26-1 + add_dev_to_array@Base 2.26-1 + add_dev_to_set@Base 2.26-1 + add_spare_dev_to_array@Base 2.26-1 + alloc_dev_info@Base 2.26-1 + alloc_lib_context@Base 2.26-1 + alloc_meta_areas@Base 2.26-1 + alloc_private@Base 2.26-1 + alloc_private_and_read@Base 2.26-1 + alloc_raid_dev@Base 2.26-1 + alloc_raid_set@Base 2.26-1 + base_partitioned_set@Base 2.26-1 bd_dm_activate_raid_set@Base 2.14 bd_dm_check_deps@Base 2.14 bd_dm_close@Base 2.14 @@ -15,3 +33,150 @@ bd_dm_name_from_node@Base 2.14 bd_dm_node_from_name@Base 2.14 bd_dm_remove@Base 2.14 + change_set@Base 2.26-1 + check_busy_disk@Base 2.26-1 + check_raid_set@Base 2.26-1 + check_valid_format@Base 2.26-1 + count_devices@Base 2.26-1 + count_devs@Base 2.26-1 + count_sets@Base 2.26-1 + create_raidset@Base 2.26-1 + ddf1_beginning@Base 2.26-1 + ddf1_check_all_crcs@Base 2.26-1 + ddf1_cr_off_maxpds_helper@Base 2.26-1 + ddf1_cvt_adapter@Base 2.26-1 + ddf1_cvt_all@Base 2.26-1 + ddf1_cvt_config_record@Base 2.26-1 + ddf1_cvt_disk_data@Base 2.26-1 + ddf1_cvt_header@Base 2.26-1 + ddf1_cvt_phys_drive@Base 2.26-1 + ddf1_cvt_phys_drive_header@Base 2.26-1 + ddf1_cvt_records@Base 2.26-1 + ddf1_cvt_spare_record@Base 2.26-1 + ddf1_cvt_virt_drive@Base 2.26-1 + ddf1_cvt_virt_drive_header@Base 2.26-1 + ddf1_dump_all@Base 2.26-1 + ddf1_endianness@Base 2.26-1 + ddf1_process_records@Base 2.26-1 + ddf1_update_all_crcs@Base 2.26-1 + del_dev_in_set@Base 2.26-1 + delete_error_target@Base 2.26-1 + delete_raidsets@Base 2.26-1 + discover_devices@Base 2.26-1 + discover_partitions@Base 2.26-1 + discover_raid_devices@Base 2.26-1 + discover_raid_devices_spares@Base 2.26-1 + display_devices@Base 2.26-1 + display_set@Base 2.26-1 + display_table@Base 2.26-1 + dm_create@Base 2.26-1 + dm_reload@Base 2.26-1 + dm_remove@Base 2.26-1 + dm_resume@Base 2.26-1 + dm_status@Base 2.26-1 + dm_suspend@Base 2.26-1 + dm_version@Base 2.26-1 + dso@Base 2.26-1 + dso_end_rebuild@Base 2.26-1 + dso_get_members@Base 2.26-1 + end_log@Base 2.26-1 + erase_metadata@Base 2.26-1 + file_dev_size@Base 2.26-1 + file_metadata@Base 2.26-1 + find_disk@Base 2.26-1 + find_group@Base 2.26-1 + find_or_alloc_raid_set@Base 2.26-1 + find_raiddev@Base 2.26-1 + find_set@Base 2.26-1 + find_set_inconsistent@Base 2.26-1 + find_spare@Base 2.26-1 + format_error@Base 2.26-1 + free_dev_info@Base 2.26-1 + free_format_caps@Base 2.26-1 + free_lib_context@Base 2.26-1 + free_raid_dev@Base 2.26-1 + free_raid_set@Base 2.26-1 + free_string@Base 2.26-1 + get_ata_serial@Base 2.26-1 + get_basename@Base 2.26-1 + get_dirname@Base 2.26-1 + get_dm_type@Base 2.26-1 + get_format@Base 2.26-1 + get_format_caps@Base 2.26-1 + get_raid_set@Base 2.26-1 + get_scsi_id@Base 2.26-1 + get_scsi_serial@Base 2.26-1 + get_set_name@Base 2.26-1 + get_set_type@Base 2.26-1 + get_status@Base 2.26-1 + get_type@Base 2.26-1 +
Bug#1005622: [Pkg-utopia-maintainers] Bug#1005622: libblockdev: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below
Control: reassign -1 libdmraid-dev Control: found -1 1.0.0.rc16-10 Control: affects src:libblockdev Reassigning accordingly. Am 13.02.22 um 14:11 schrieb Michael Biebl: Looking at those symbols, they all appear to come from libdmraid and this appears to be an issue caused by dmraid (1.0.0.rc16-10) Building in a sid chroot with libdmraid-dev_1.0.0.rc16-9_amd64.deb and libdmraid1.0.0.rc16_1.0.0.rc16-9_amd64.deb makes the build succeed. So I suspect this breakage was caused by [ Helmut Grohne ] * Fix FTCBFS: Use a multiarch --libdir (closes: #951469). And indeed, reverting that patch from #951469 fixes this issue. Helmut, can you please take care of that? Somehow this change makes those symbols from libdmraid leak into libblockdev-dm2 Thanks, Michael Am 13.02.22 um 08:50 schrieb Lucas Nussbaum: Source: libblockdev Version: 2.26-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220212 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory '/<>' dh_makeshlibs -- -c4 dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libblockdev-dm2/DEBIAN/symbols doesn't match completely debian/libblockdev-dm2.symbols --- debian/libblockdev-dm2.symbols (libblockdev-dm2_2.26-1_amd64) +++ dpkg-gensymbolsnjXTfu 2022-02-12 22:44:06.350039704 + @@ -1,5 +1,23 @@ libbd_dm.so.2 libblockdev-dm2 #MINVER# * Build-Depends-Package: libblockdev-dm-dev + _dbg_free@Base 2.26-1 + _dbg_malloc@Base 2.26-1 + _dbg_realloc@Base 2.26-1 + _dbg_strdup@Base 2.26-1 + _dbg_strndup@Base 2.26-1 + _rebuild_raidset@Base 2.26-1 + add_delimiter@Base 2.26-1 + add_dev_to_array@Base 2.26-1 + add_dev_to_set@Base 2.26-1 + add_spare_dev_to_array@Base 2.26-1 + alloc_dev_info@Base 2.26-1 + alloc_lib_context@Base 2.26-1 + alloc_meta_areas@Base 2.26-1 + alloc_private@Base 2.26-1 + alloc_private_and_read@Base 2.26-1 + alloc_raid_dev@Base 2.26-1 + alloc_raid_set@Base 2.26-1 + base_partitioned_set@Base 2.26-1 bd_dm_activate_raid_set@Base 2.14 bd_dm_check_deps@Base 2.14 bd_dm_close@Base 2.14 @@ -15,3 +33,150 @@ bd_dm_name_from_node@Base 2.14 bd_dm_node_from_name@Base 2.14 bd_dm_remove@Base 2.14 + change_set@Base 2.26-1 + check_busy_disk@Base 2.26-1 + check_raid_set@Base 2.26-1 + check_valid_format@Base 2.26-1 + count_devices@Base 2.26-1 + count_devs@Base 2.26-1 + count_sets@Base 2.26-1 + create_raidset@Base 2.26-1 + ddf1_beginning@Base 2.26-1 + ddf1_check_all_crcs@Base 2.26-1 + ddf1_cr_off_maxpds_helper@Base 2.26-1 + ddf1_cvt_adapter@Base 2.26-1 + ddf1_cvt_all@Base 2.26-1 + ddf1_cvt_config_record@Base 2.26-1 + ddf1_cvt_disk_data@Base 2.26-1 + ddf1_cvt_header@Base 2.26-1 + ddf1_cvt_phys_drive@Base 2.26-1 + ddf1_cvt_phys_drive_header@Base 2.26-1 + ddf1_cvt_records@Base 2.26-1 + ddf1_cvt_spare_record@Base 2.26-1 + ddf1_cvt_virt_drive@Base 2.26-1 + ddf1_cvt_virt_drive_header@Base 2.26-1 + ddf1_dump_all@Base 2.26-1 + ddf1_endianness@Base 2.26-1 + ddf1_process_records@Base 2.26-1 + ddf1_update_all_crcs@Base 2.26-1 + del_dev_in_set@Base 2.26-1 + delete_error_target@Base 2.26-1 + delete_raidsets@Base 2.26-1 + discover_devices@Base 2.26-1 + discover_partitions@Base 2.26-1 + discover_raid_devices@Base 2.26-1 + discover_raid_devices_spares@Base 2.26-1 + display_devices@Base 2.26-1 + display_set@Base 2.26-1 + display_table@Base 2.26-1 + dm_create@Base 2.26-1 + dm_reload@Base 2.26-1 + dm_remove@Base 2.26-1 + dm_resume@Base 2.26-1 + dm_status@Base 2.26-1 + dm_suspend@Base 2.26-1 + dm_version@Base 2.26-1 + dso@Base 2.26-1 + dso_end_rebuild@Base 2.26-1 + dso_get_members@Base 2.26-1 + end_log@Base 2.26-1 + erase_metadata@Base 2.26-1 + file_dev_size@Base 2.26-1 + file_metadata@Base 2.26-1 + find_disk@Base 2.26-1 + find_group@Base 2.26-1 + find_or_alloc_raid_set@Base 2.26-1 + find_raiddev@Base 2.26-1 + find_set@Base 2.26-1 + find_set_inconsistent@Base 2.26-1 + find_spare@Base 2.26-1 + format_error@Base 2.26-1 + free_dev_info@Base 2.26-1 + free_format_caps@Base 2.26-1 + free_lib_context@Base 2.26-1 + free_raid_dev@Base 2.26-1 + free_raid_set@Base 2.26-1 + free_string@Base 2.26-1 + get_ata_serial@Base 2.26-1 + get_basename@Base 2.26-1 + get_dirname@Base 2.26-1 + get_dm_type@Base 2.26-1 + get_format@Base 2.26-1 + get_format_caps@Base 2.26-1 + get_raid_set@Base 2.26-1 + get_scsi_id@Base 2.26-1 + get_scsi_serial@Base 2.26-1 + get_set_name@Base 2.26-1 + get_set_type@Base 2.26-1 + get_status@Base 2.26-1 + get_type@Base 2.26-1 + group_set@Base 2.26-1 + hot_spare_add@Base 2.26-1 + init_fn@Base 2.26-1 + init_locking@Base 2.26-1 + init_raid_set@Base 2.26-1 + join_superset@Base 2.26-1 + lc_inc_opt@Base 2.26-1 + lc_list@Base 2.26-1 + lc_opt@Base 2.26-1 + lc_opt_arg@Base 2.26-1 + lc_stralloc_opt@Base 2.26-1 + lc_strcat_opt@Base 2.26-1 + led@Base 2.26-1 + lib_perform@Base 2.26-1 + libdmraid_date@Base 2.26-1 +
Bug#1005622: [Pkg-utopia-maintainers] Bug#1005622: libblockdev: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below
Looking at those symbols, they all appear to come from libdmraid and this appears to be an issue caused by dmraid (1.0.0.rc16-10) Building in a sid chroot with libdmraid-dev_1.0.0.rc16-9_amd64.deb and libdmraid1.0.0.rc16_1.0.0.rc16-9_amd64.deb makes the build succeed. So I suspect this breakage was caused by [ Helmut Grohne ] * Fix FTCBFS: Use a multiarch --libdir (closes: #951469). And indeed, reverting that patch from #951469 fixes this issue. Helmut, can you please take care of that? Somehow this change makes those symbols from libdmraid leak into libblockdev-dm2 Thanks, Michael Am 13.02.22 um 08:50 schrieb Lucas Nussbaum: Source: libblockdev Version: 2.26-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220212 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory '/<>' dh_makeshlibs -- -c4 dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libblockdev-dm2/DEBIAN/symbols doesn't match completely debian/libblockdev-dm2.symbols --- debian/libblockdev-dm2.symbols (libblockdev-dm2_2.26-1_amd64) +++ dpkg-gensymbolsnjXTfu 2022-02-12 22:44:06.350039704 + @@ -1,5 +1,23 @@ libbd_dm.so.2 libblockdev-dm2 #MINVER# * Build-Depends-Package: libblockdev-dm-dev + _dbg_free@Base 2.26-1 + _dbg_malloc@Base 2.26-1 + _dbg_realloc@Base 2.26-1 + _dbg_strdup@Base 2.26-1 + _dbg_strndup@Base 2.26-1 + _rebuild_raidset@Base 2.26-1 + add_delimiter@Base 2.26-1 + add_dev_to_array@Base 2.26-1 + add_dev_to_set@Base 2.26-1 + add_spare_dev_to_array@Base 2.26-1 + alloc_dev_info@Base 2.26-1 + alloc_lib_context@Base 2.26-1 + alloc_meta_areas@Base 2.26-1 + alloc_private@Base 2.26-1 + alloc_private_and_read@Base 2.26-1 + alloc_raid_dev@Base 2.26-1 + alloc_raid_set@Base 2.26-1 + base_partitioned_set@Base 2.26-1 bd_dm_activate_raid_set@Base 2.14 bd_dm_check_deps@Base 2.14 bd_dm_close@Base 2.14 @@ -15,3 +33,150 @@ bd_dm_name_from_node@Base 2.14 bd_dm_node_from_name@Base 2.14 bd_dm_remove@Base 2.14 + change_set@Base 2.26-1 + check_busy_disk@Base 2.26-1 + check_raid_set@Base 2.26-1 + check_valid_format@Base 2.26-1 + count_devices@Base 2.26-1 + count_devs@Base 2.26-1 + count_sets@Base 2.26-1 + create_raidset@Base 2.26-1 + ddf1_beginning@Base 2.26-1 + ddf1_check_all_crcs@Base 2.26-1 + ddf1_cr_off_maxpds_helper@Base 2.26-1 + ddf1_cvt_adapter@Base 2.26-1 + ddf1_cvt_all@Base 2.26-1 + ddf1_cvt_config_record@Base 2.26-1 + ddf1_cvt_disk_data@Base 2.26-1 + ddf1_cvt_header@Base 2.26-1 + ddf1_cvt_phys_drive@Base 2.26-1 + ddf1_cvt_phys_drive_header@Base 2.26-1 + ddf1_cvt_records@Base 2.26-1 + ddf1_cvt_spare_record@Base 2.26-1 + ddf1_cvt_virt_drive@Base 2.26-1 + ddf1_cvt_virt_drive_header@Base 2.26-1 + ddf1_dump_all@Base 2.26-1 + ddf1_endianness@Base 2.26-1 + ddf1_process_records@Base 2.26-1 + ddf1_update_all_crcs@Base 2.26-1 + del_dev_in_set@Base 2.26-1 + delete_error_target@Base 2.26-1 + delete_raidsets@Base 2.26-1 + discover_devices@Base 2.26-1 + discover_partitions@Base 2.26-1 + discover_raid_devices@Base 2.26-1 + discover_raid_devices_spares@Base 2.26-1 + display_devices@Base 2.26-1 + display_set@Base 2.26-1 + display_table@Base 2.26-1 + dm_create@Base 2.26-1 + dm_reload@Base 2.26-1 + dm_remove@Base 2.26-1 + dm_resume@Base 2.26-1 + dm_status@Base 2.26-1 + dm_suspend@Base 2.26-1 + dm_version@Base 2.26-1 + dso@Base 2.26-1 + dso_end_rebuild@Base 2.26-1 + dso_get_members@Base 2.26-1 + end_log@Base 2.26-1 + erase_metadata@Base 2.26-1 + file_dev_size@Base 2.26-1 + file_metadata@Base 2.26-1 + find_disk@Base 2.26-1 + find_group@Base 2.26-1 + find_or_alloc_raid_set@Base 2.26-1 + find_raiddev@Base 2.26-1 + find_set@Base 2.26-1 + find_set_inconsistent@Base 2.26-1 + find_spare@Base 2.26-1 + format_error@Base 2.26-1 + free_dev_info@Base 2.26-1 + free_format_caps@Base 2.26-1 + free_lib_context@Base 2.26-1 + free_raid_dev@Base 2.26-1 + free_raid_set@Base 2.26-1 + free_string@Base 2.26-1 + get_ata_serial@Base 2.26-1 + get_basename@Base 2.26-1 + get_dirname@Base 2.26-1 + get_dm_type@Base 2.26-1 + get_format@Base 2.26-1 + get_format_caps@Base 2.26-1 + get_raid_set@Base 2.26-1 + get_scsi_id@Base 2.26-1 + get_scsi_serial@Base 2.26-1 + get_set_name@Base 2.26-1 + get_set_type@Base 2.26-1 + get_status@Base 2.26-1 + get_type@Base 2.26-1 + group_set@Base 2.26-1 + hot_spare_add@Base 2.26-1 + init_fn@Base 2.26-1 + init_locking@Base 2.26-1 + init_raid_set@Base 2.26-1 + join_superset@Base 2.26-1 + lc_inc_opt@Base 2.26-1 + lc_list@Base 2.26-1 + lc_opt@Base 2.26-1 + lc_opt_arg@Base 2.26-1 + lc_stralloc_opt@Base 2.26-1 + lc_strcat_opt@Base 2.26-1 + led@Base 2.26-1 + lib_perform@Base 2.26-1 + libdmraid_date@Base 2.26-1 + libdmraid_exit@Base 2.26-1 + libdmraid_init@Base 2.26-1 + libdmraid_make_table@Base 2.26-1 + libdmraid_version@Base 2.26-1 + list_add_sorted@Base 2.26-1 + list_formats@Base 2.26-1 +
