Activity log for bug #2051571

Date Who What changed Old value New value Message
2024-01-29 16:58:11 Dan Watkins bug added bug
2024-01-29 17:17:22 Brad Figg mstflint (Ubuntu): assignee Brad Figg (brad-figg)
2024-02-09 11:27:12 Dimitri John Ledkov mstflint (Ubuntu): assignee Brad Figg (brad-figg)
2024-02-09 11:30:01 Dimitri John Ledkov tags jammy regression-update
2024-02-09 11:30:06 Dimitri John Ledkov nominated for series Ubuntu Jammy
2024-02-09 11:30:06 Dimitri John Ledkov bug task added mstflint (Ubuntu Jammy)
2024-02-09 11:30:10 Dimitri John Ledkov mstflint (Ubuntu Jammy): importance Undecided Critical
2024-02-09 12:20:57 Robie Basak bug added subscriber Andy Whitcroft
2024-04-02 11:25:36 dann frazier mstflint (Ubuntu Jammy): status New In Progress
2024-04-02 11:25:40 dann frazier mstflint (Ubuntu Jammy): assignee dann frazier (dannf)
2024-04-12 22:09:17 dann frazier description Both jammy's previous 4.17.0+1-1build2 and noble's recent 4.26.0+1-2 include it, and 4.21.0-7 itself continues to ship its manpage. There isn't any indication in the changelog of a reason for dropping it. [Impact] The mstlink and mstreg binaries have regressed in the last jammy update. This is because a new upstream landed in jammy as an SRU, but is based on upstream's debian/ packaging, not Debian's, which enable different build flags. [Test Case] /usr/bin/mstlink and /usr/bin/mstreg have returned. [What Could Go Wrong] While this update does restore files that were dropped in the last "SRU", it does drop some files that the Debian packaging does not ship. This includes some header files, some .a files, and 2 manpages for binaries that neither version of the package ships. It is possible that somebody has started using these files, and by taking them away we break someone. That seems unlikely - these appear to be for internal-use only. Here's a complete diff: --- mstflint.jammy.orig 2024-04-12 21:40:42.700199967 +0000 +++ mstflint.jammy.ppa 2024-04-12 21:58:59.495997299 +0000 @@ -6,37 +6,20 @@ /usr/bin/mstflint /usr/bin/mstfwreset /usr/bin/mstfwtrace +/usr/bin/mstlink /usr/bin/mstmcra /usr/bin/mstmread /usr/bin/mstmtserver /usr/bin/mstmwrite /usr/bin/mstprivhost +/usr/bin/mstreg /usr/bin/mstregdump /usr/bin/mstresourcedump /usr/bin/mstresourceparse /usr/bin/mstvpd -/usr/include -/usr/include/mstflint -/usr/include/mstflint/cmdif -/usr/include/mstflint/cmdif/icmd_cif_common.h -/usr/include/mstflint/cmdif/icmd_cif_open.h -/usr/include/mstflint/common -/usr/include/mstflint/common/compatibility.h -/usr/include/mstflint/mtcr.h -/usr/include/mstflint/mtcr_com_defs.h -/usr/include/mstflint/mtcr_mf.h -/usr/include/mstflint/tools_layouts -/usr/include/mstflint/tools_layouts/adb_to_c_utils.h -/usr/include/mstflint/tools_layouts/icmd_layouts.h -/usr/include/mtcr_ul /usr/lib /usr/lib/x86_64-linux-gnu -/usr/lib/x86_64-linux-gnu/libcmdif.a -/usr/lib/x86_64-linux-gnu/libdev_mgt.a -/usr/lib/x86_64-linux-gnu/libreg_access.a -/usr/lib/x86_64-linux-gnu/libtools_layouts.a /usr/lib/x86_64-linux-gnu/mstflint -/usr/lib/x86_64-linux-gnu/mstflint/libmtcr_ul.a /usr/lib/x86_64-linux-gnu/mstflint/python_tools /usr/lib/x86_64-linux-gnu/mstflint/python_tools/c_dev_mgt.so /usr/lib/x86_64-linux-gnu/mstflint/python_tools/ccmdif.so @@ -150,13 +133,14 @@ /usr/share/doc/mstflint/README.gz /usr/share/doc/mstflint/changelog.Debian.gz /usr/share/doc/mstflint/copyright +/usr/share/lintian +/usr/share/lintian/overrides +/usr/share/lintian/overrides/mstflint /usr/share/man /usr/share/man/man1 -/usr/share/man/man1/mstarchive.1.gz /usr/share/man/man1/mstconfig.1.gz /usr/share/man/man1/mstcongestion.1.gz /usr/share/man/man1/mstflint.1.gz -/usr/share/man/man1/mstfwmanager.1.gz /usr/share/man/man1/mstfwreset.1.gz /usr/share/man/man1/mstfwtrace.1.gz /usr/share/man/man1/mstlink.1.gz @@ -196,6 +180,10 @@ /usr/share/mstflint/mlxconfig_dbs /usr/share/mstflint/mlxconfig_dbs/mlxconfig_host.db /usr/share/mstflint/mlxconfig_dbs/mlxconfig_switch.db -/usr/include/mtcr_ul/mtcr.h -/usr/include/mtcr_ul/mtcr_com_defs.h -/usr/lib/libmtcr_ul.a +/usr/share/mstflint/prm_dbs +/usr/share/mstflint/prm_dbs/hca +/usr/share/mstflint/prm_dbs/hca/ext +/usr/share/mstflint/prm_dbs/hca/ext/register_access_table.adb +/usr/share/mstflint/prm_dbs/switch +/usr/share/mstflint/prm_dbs/switch/ext +/usr/share/mstflint/prm_dbs/switch/ext/register_access_table.adb
2024-04-12 22:11:25 dann frazier description [Impact] The mstlink and mstreg binaries have regressed in the last jammy update. This is because a new upstream landed in jammy as an SRU, but is based on upstream's debian/ packaging, not Debian's, which enable different build flags. [Test Case] /usr/bin/mstlink and /usr/bin/mstreg have returned. [What Could Go Wrong] While this update does restore files that were dropped in the last "SRU", it does drop some files that the Debian packaging does not ship. This includes some header files, some .a files, and 2 manpages for binaries that neither version of the package ships. It is possible that somebody has started using these files, and by taking them away we break someone. That seems unlikely - these appear to be for internal-use only. Here's a complete diff: --- mstflint.jammy.orig 2024-04-12 21:40:42.700199967 +0000 +++ mstflint.jammy.ppa 2024-04-12 21:58:59.495997299 +0000 @@ -6,37 +6,20 @@ /usr/bin/mstflint /usr/bin/mstfwreset /usr/bin/mstfwtrace +/usr/bin/mstlink /usr/bin/mstmcra /usr/bin/mstmread /usr/bin/mstmtserver /usr/bin/mstmwrite /usr/bin/mstprivhost +/usr/bin/mstreg /usr/bin/mstregdump /usr/bin/mstresourcedump /usr/bin/mstresourceparse /usr/bin/mstvpd -/usr/include -/usr/include/mstflint -/usr/include/mstflint/cmdif -/usr/include/mstflint/cmdif/icmd_cif_common.h -/usr/include/mstflint/cmdif/icmd_cif_open.h -/usr/include/mstflint/common -/usr/include/mstflint/common/compatibility.h -/usr/include/mstflint/mtcr.h -/usr/include/mstflint/mtcr_com_defs.h -/usr/include/mstflint/mtcr_mf.h -/usr/include/mstflint/tools_layouts -/usr/include/mstflint/tools_layouts/adb_to_c_utils.h -/usr/include/mstflint/tools_layouts/icmd_layouts.h -/usr/include/mtcr_ul /usr/lib /usr/lib/x86_64-linux-gnu -/usr/lib/x86_64-linux-gnu/libcmdif.a -/usr/lib/x86_64-linux-gnu/libdev_mgt.a -/usr/lib/x86_64-linux-gnu/libreg_access.a -/usr/lib/x86_64-linux-gnu/libtools_layouts.a /usr/lib/x86_64-linux-gnu/mstflint -/usr/lib/x86_64-linux-gnu/mstflint/libmtcr_ul.a /usr/lib/x86_64-linux-gnu/mstflint/python_tools /usr/lib/x86_64-linux-gnu/mstflint/python_tools/c_dev_mgt.so /usr/lib/x86_64-linux-gnu/mstflint/python_tools/ccmdif.so @@ -150,13 +133,14 @@ /usr/share/doc/mstflint/README.gz /usr/share/doc/mstflint/changelog.Debian.gz /usr/share/doc/mstflint/copyright +/usr/share/lintian +/usr/share/lintian/overrides +/usr/share/lintian/overrides/mstflint /usr/share/man /usr/share/man/man1 -/usr/share/man/man1/mstarchive.1.gz /usr/share/man/man1/mstconfig.1.gz /usr/share/man/man1/mstcongestion.1.gz /usr/share/man/man1/mstflint.1.gz -/usr/share/man/man1/mstfwmanager.1.gz /usr/share/man/man1/mstfwreset.1.gz /usr/share/man/man1/mstfwtrace.1.gz /usr/share/man/man1/mstlink.1.gz @@ -196,6 +180,10 @@ /usr/share/mstflint/mlxconfig_dbs /usr/share/mstflint/mlxconfig_dbs/mlxconfig_host.db /usr/share/mstflint/mlxconfig_dbs/mlxconfig_switch.db -/usr/include/mtcr_ul/mtcr.h -/usr/include/mtcr_ul/mtcr_com_defs.h -/usr/lib/libmtcr_ul.a +/usr/share/mstflint/prm_dbs +/usr/share/mstflint/prm_dbs/hca +/usr/share/mstflint/prm_dbs/hca/ext +/usr/share/mstflint/prm_dbs/hca/ext/register_access_table.adb +/usr/share/mstflint/prm_dbs/switch +/usr/share/mstflint/prm_dbs/switch/ext +/usr/share/mstflint/prm_dbs/switch/ext/register_access_table.adb [Impact] The mstlink and mstreg binaries have regressed in the last jammy update. This is because a new upstream landed in jammy as an SRU outside of the SRU process, and is based on upstream's debian/ packaging, not Debian's, which enable different build flags. [Test Case] /usr/bin/mstlink and /usr/bin/mstreg have returned. [What Could Go Wrong] While this update does restore files that were dropped in the last "SRU", it does drop some files that the Debian packaging does not ship. This includes some header files, some .a files, and 2 manpages for binaries that neither version of the package ships. It is possible that somebody has started using these files, and by taking them away we break someone. That seems unlikely - these appear to be for internal-use only. Here's a complete diff: --- mstflint.jammy.orig 2024-04-12 21:40:42.700199967 +0000 +++ mstflint.jammy.ppa 2024-04-12 21:58:59.495997299 +0000 @@ -6,37 +6,20 @@  /usr/bin/mstflint  /usr/bin/mstfwreset  /usr/bin/mstfwtrace +/usr/bin/mstlink  /usr/bin/mstmcra  /usr/bin/mstmread  /usr/bin/mstmtserver  /usr/bin/mstmwrite  /usr/bin/mstprivhost +/usr/bin/mstreg  /usr/bin/mstregdump  /usr/bin/mstresourcedump  /usr/bin/mstresourceparse  /usr/bin/mstvpd -/usr/include -/usr/include/mstflint -/usr/include/mstflint/cmdif -/usr/include/mstflint/cmdif/icmd_cif_common.h -/usr/include/mstflint/cmdif/icmd_cif_open.h -/usr/include/mstflint/common -/usr/include/mstflint/common/compatibility.h -/usr/include/mstflint/mtcr.h -/usr/include/mstflint/mtcr_com_defs.h -/usr/include/mstflint/mtcr_mf.h -/usr/include/mstflint/tools_layouts -/usr/include/mstflint/tools_layouts/adb_to_c_utils.h -/usr/include/mstflint/tools_layouts/icmd_layouts.h -/usr/include/mtcr_ul  /usr/lib  /usr/lib/x86_64-linux-gnu -/usr/lib/x86_64-linux-gnu/libcmdif.a -/usr/lib/x86_64-linux-gnu/libdev_mgt.a -/usr/lib/x86_64-linux-gnu/libreg_access.a -/usr/lib/x86_64-linux-gnu/libtools_layouts.a  /usr/lib/x86_64-linux-gnu/mstflint -/usr/lib/x86_64-linux-gnu/mstflint/libmtcr_ul.a  /usr/lib/x86_64-linux-gnu/mstflint/python_tools  /usr/lib/x86_64-linux-gnu/mstflint/python_tools/c_dev_mgt.so  /usr/lib/x86_64-linux-gnu/mstflint/python_tools/ccmdif.so @@ -150,13 +133,14 @@  /usr/share/doc/mstflint/README.gz  /usr/share/doc/mstflint/changelog.Debian.gz  /usr/share/doc/mstflint/copyright +/usr/share/lintian +/usr/share/lintian/overrides +/usr/share/lintian/overrides/mstflint  /usr/share/man  /usr/share/man/man1 -/usr/share/man/man1/mstarchive.1.gz  /usr/share/man/man1/mstconfig.1.gz  /usr/share/man/man1/mstcongestion.1.gz  /usr/share/man/man1/mstflint.1.gz -/usr/share/man/man1/mstfwmanager.1.gz  /usr/share/man/man1/mstfwreset.1.gz  /usr/share/man/man1/mstfwtrace.1.gz  /usr/share/man/man1/mstlink.1.gz @@ -196,6 +180,10 @@  /usr/share/mstflint/mlxconfig_dbs  /usr/share/mstflint/mlxconfig_dbs/mlxconfig_host.db  /usr/share/mstflint/mlxconfig_dbs/mlxconfig_switch.db -/usr/include/mtcr_ul/mtcr.h -/usr/include/mtcr_ul/mtcr_com_defs.h -/usr/lib/libmtcr_ul.a +/usr/share/mstflint/prm_dbs +/usr/share/mstflint/prm_dbs/hca +/usr/share/mstflint/prm_dbs/hca/ext +/usr/share/mstflint/prm_dbs/hca/ext/register_access_table.adb +/usr/share/mstflint/prm_dbs/switch +/usr/share/mstflint/prm_dbs/switch/ext +/usr/share/mstflint/prm_dbs/switch/ext/register_access_table.adb
2024-04-12 22:15:16 dann frazier description [Impact] The mstlink and mstreg binaries have regressed in the last jammy update. This is because a new upstream landed in jammy as an SRU outside of the SRU process, and is based on upstream's debian/ packaging, not Debian's, which enable different build flags. [Test Case] /usr/bin/mstlink and /usr/bin/mstreg have returned. [What Could Go Wrong] While this update does restore files that were dropped in the last "SRU", it does drop some files that the Debian packaging does not ship. This includes some header files, some .a files, and 2 manpages for binaries that neither version of the package ships. It is possible that somebody has started using these files, and by taking them away we break someone. That seems unlikely - these appear to be for internal-use only. Here's a complete diff: --- mstflint.jammy.orig 2024-04-12 21:40:42.700199967 +0000 +++ mstflint.jammy.ppa 2024-04-12 21:58:59.495997299 +0000 @@ -6,37 +6,20 @@  /usr/bin/mstflint  /usr/bin/mstfwreset  /usr/bin/mstfwtrace +/usr/bin/mstlink  /usr/bin/mstmcra  /usr/bin/mstmread  /usr/bin/mstmtserver  /usr/bin/mstmwrite  /usr/bin/mstprivhost +/usr/bin/mstreg  /usr/bin/mstregdump  /usr/bin/mstresourcedump  /usr/bin/mstresourceparse  /usr/bin/mstvpd -/usr/include -/usr/include/mstflint -/usr/include/mstflint/cmdif -/usr/include/mstflint/cmdif/icmd_cif_common.h -/usr/include/mstflint/cmdif/icmd_cif_open.h -/usr/include/mstflint/common -/usr/include/mstflint/common/compatibility.h -/usr/include/mstflint/mtcr.h -/usr/include/mstflint/mtcr_com_defs.h -/usr/include/mstflint/mtcr_mf.h -/usr/include/mstflint/tools_layouts -/usr/include/mstflint/tools_layouts/adb_to_c_utils.h -/usr/include/mstflint/tools_layouts/icmd_layouts.h -/usr/include/mtcr_ul  /usr/lib  /usr/lib/x86_64-linux-gnu -/usr/lib/x86_64-linux-gnu/libcmdif.a -/usr/lib/x86_64-linux-gnu/libdev_mgt.a -/usr/lib/x86_64-linux-gnu/libreg_access.a -/usr/lib/x86_64-linux-gnu/libtools_layouts.a  /usr/lib/x86_64-linux-gnu/mstflint -/usr/lib/x86_64-linux-gnu/mstflint/libmtcr_ul.a  /usr/lib/x86_64-linux-gnu/mstflint/python_tools  /usr/lib/x86_64-linux-gnu/mstflint/python_tools/c_dev_mgt.so  /usr/lib/x86_64-linux-gnu/mstflint/python_tools/ccmdif.so @@ -150,13 +133,14 @@  /usr/share/doc/mstflint/README.gz  /usr/share/doc/mstflint/changelog.Debian.gz  /usr/share/doc/mstflint/copyright +/usr/share/lintian +/usr/share/lintian/overrides +/usr/share/lintian/overrides/mstflint  /usr/share/man  /usr/share/man/man1 -/usr/share/man/man1/mstarchive.1.gz  /usr/share/man/man1/mstconfig.1.gz  /usr/share/man/man1/mstcongestion.1.gz  /usr/share/man/man1/mstflint.1.gz -/usr/share/man/man1/mstfwmanager.1.gz  /usr/share/man/man1/mstfwreset.1.gz  /usr/share/man/man1/mstfwtrace.1.gz  /usr/share/man/man1/mstlink.1.gz @@ -196,6 +180,10 @@  /usr/share/mstflint/mlxconfig_dbs  /usr/share/mstflint/mlxconfig_dbs/mlxconfig_host.db  /usr/share/mstflint/mlxconfig_dbs/mlxconfig_switch.db -/usr/include/mtcr_ul/mtcr.h -/usr/include/mtcr_ul/mtcr_com_defs.h -/usr/lib/libmtcr_ul.a +/usr/share/mstflint/prm_dbs +/usr/share/mstflint/prm_dbs/hca +/usr/share/mstflint/prm_dbs/hca/ext +/usr/share/mstflint/prm_dbs/hca/ext/register_access_table.adb +/usr/share/mstflint/prm_dbs/switch +/usr/share/mstflint/prm_dbs/switch/ext +/usr/share/mstflint/prm_dbs/switch/ext/register_access_table.adb [Impact] The mstlink and mstreg binaries have regressed in the last jammy update. This is because a new upstream landed in jammy as an SRU outside of the SRU process, and is based on upstream's debian/ packaging, not Debian's. One of the differences between these version is the use of different configure flags. [Test Case] /usr/bin/mstlink and /usr/bin/mstreg have returned. [What Could Go Wrong] While this update does restore files that were dropped in the last "SRU", it does drop some files that the Debian packaging does not ship. This includes some header files, some .a files, and 2 manpages for binaries that neither version of the package ships. It is possible that somebody has started using these files, and by taking them away we break someone. That seems unlikely - these appear to be for internal-use only. Here's a complete diff: --- mstflint.jammy.orig 2024-04-12 21:40:42.700199967 +0000 +++ mstflint.jammy.ppa 2024-04-12 21:58:59.495997299 +0000 @@ -6,37 +6,20 @@  /usr/bin/mstflint  /usr/bin/mstfwreset  /usr/bin/mstfwtrace +/usr/bin/mstlink  /usr/bin/mstmcra  /usr/bin/mstmread  /usr/bin/mstmtserver  /usr/bin/mstmwrite  /usr/bin/mstprivhost +/usr/bin/mstreg  /usr/bin/mstregdump  /usr/bin/mstresourcedump  /usr/bin/mstresourceparse  /usr/bin/mstvpd -/usr/include -/usr/include/mstflint -/usr/include/mstflint/cmdif -/usr/include/mstflint/cmdif/icmd_cif_common.h -/usr/include/mstflint/cmdif/icmd_cif_open.h -/usr/include/mstflint/common -/usr/include/mstflint/common/compatibility.h -/usr/include/mstflint/mtcr.h -/usr/include/mstflint/mtcr_com_defs.h -/usr/include/mstflint/mtcr_mf.h -/usr/include/mstflint/tools_layouts -/usr/include/mstflint/tools_layouts/adb_to_c_utils.h -/usr/include/mstflint/tools_layouts/icmd_layouts.h -/usr/include/mtcr_ul  /usr/lib  /usr/lib/x86_64-linux-gnu -/usr/lib/x86_64-linux-gnu/libcmdif.a -/usr/lib/x86_64-linux-gnu/libdev_mgt.a -/usr/lib/x86_64-linux-gnu/libreg_access.a -/usr/lib/x86_64-linux-gnu/libtools_layouts.a  /usr/lib/x86_64-linux-gnu/mstflint -/usr/lib/x86_64-linux-gnu/mstflint/libmtcr_ul.a  /usr/lib/x86_64-linux-gnu/mstflint/python_tools  /usr/lib/x86_64-linux-gnu/mstflint/python_tools/c_dev_mgt.so  /usr/lib/x86_64-linux-gnu/mstflint/python_tools/ccmdif.so @@ -150,13 +133,14 @@  /usr/share/doc/mstflint/README.gz  /usr/share/doc/mstflint/changelog.Debian.gz  /usr/share/doc/mstflint/copyright +/usr/share/lintian +/usr/share/lintian/overrides +/usr/share/lintian/overrides/mstflint  /usr/share/man  /usr/share/man/man1 -/usr/share/man/man1/mstarchive.1.gz  /usr/share/man/man1/mstconfig.1.gz  /usr/share/man/man1/mstcongestion.1.gz  /usr/share/man/man1/mstflint.1.gz -/usr/share/man/man1/mstfwmanager.1.gz  /usr/share/man/man1/mstfwreset.1.gz  /usr/share/man/man1/mstfwtrace.1.gz  /usr/share/man/man1/mstlink.1.gz @@ -196,6 +180,10 @@  /usr/share/mstflint/mlxconfig_dbs  /usr/share/mstflint/mlxconfig_dbs/mlxconfig_host.db  /usr/share/mstflint/mlxconfig_dbs/mlxconfig_switch.db -/usr/include/mtcr_ul/mtcr.h -/usr/include/mtcr_ul/mtcr_com_defs.h -/usr/lib/libmtcr_ul.a +/usr/share/mstflint/prm_dbs +/usr/share/mstflint/prm_dbs/hca +/usr/share/mstflint/prm_dbs/hca/ext +/usr/share/mstflint/prm_dbs/hca/ext/register_access_table.adb +/usr/share/mstflint/prm_dbs/switch +/usr/share/mstflint/prm_dbs/switch/ext +/usr/share/mstflint/prm_dbs/switch/ext/register_access_table.adb
2024-04-26 08:16:37 Timo Aaltonen mstflint (Ubuntu Jammy): status In Progress Fix Committed
2024-04-26 08:16:38 Timo Aaltonen bug added subscriber Ubuntu Stable Release Updates Team
2024-04-26 08:16:47 Timo Aaltonen bug added subscriber SRU Verification
2024-04-26 08:16:49 Timo Aaltonen tags jammy regression-update jammy regression-update verification-needed verification-needed-jammy
2024-05-03 19:54:05 dann frazier tags jammy regression-update verification-needed verification-needed-jammy jammy regression-update verification-done verification-done-jammy
2024-07-09 18:25:48 Launchpad Janitor mstflint (Ubuntu Jammy): status Fix Committed Fix Released
2024-07-09 18:26:00 Brian Murray removed subscriber Ubuntu Stable Release Updates Team