In addition to the changelog versions it seems to me that the debdiff is potentially a bit missleading:
1) the shell testcases are not executed neither during build, nor during autopkgtest. As they seem to need root, it would be nice to add autopkgtest that would do:
cd iptables/tests/shell; ./run-tests.sh --host
as root.
2) the patched in new test case is patched as a regular text file, and thus is not picked up by ./run-tests.sh harness, because executable bit is lost. Hence debian/rules should probably `chmod +x` in the clean target. And then autopkgtest either needs to have restriction requires build; or also chmod that new test case before running ./run-tests.sh --host.
Given this new test case is supposed to catch this regression, enabling this test suite in autopkgtest would be worth while for jammy.
In addition to the changelog versions it seems to me that the debdiff is potentially a bit missleading:
1) the shell testcases are not executed neither during build, nor during autopkgtest. As they seem to need root, it would be nice to add autopkgtest that would do:
cd iptables/ tests/shell; ./run-tests.sh --host
as root.
2) the patched in new test case is patched as a regular text file, and thus is not picked up by ./run-tests.sh harness, because executable bit is lost. Hence debian/rules should probably `chmod +x` in the clean target. And then autopkgtest either needs to have restriction requires build; or also chmod that new test case before running ./run-tests.sh --host.
Given this new test case is supposed to catch this regression, enabling this test suite in autopkgtest would be worth while for jammy.
Can you attempt to fix above things?