** Changed in: cryptsetup (Ubuntu Noble)
Assignee: (unassigned) => Hector CAO (hectorcao)
** Changed in: cryptsetup (Ubuntu Stonking)
Status: New => Invalid
** Description changed:
[ Impact ]
- * cryptsetup fails to build on Noble due to an failed unit test
+ * cryptsetup fails to build on Noble due to an failed unit test
- * The unit test failure is due to jq security update CVE-2026-33948
+ * The unit test failure is due to jq security update CVE-2026-33948
- * Blocks SRU for cryptsetup on Noble:
+ * Blocks SRU for cryptsetup on Noble:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2160630
[ Test Plan ]
- * Build the package on Noble with all updates installed (apt upgrade)
- * The build should fail with log:
+ * Build the package on Noble with all updates installed (apt upgrade)
+ * The build should fail with log:
Test LUKS2 key refresh...OK
PASS: keyring-compat-test
[0] Generating test headers
generate-luks2-area-in-json-hdr-space-json0.img.sh...jq: parse error: Invalid
numeric literal at EOF at line 1, column 12288
jq: parse error: Invalid numeric literal at EOF at line 1, column 12288
Header generator ./generate-luks2-area-in-json-hdr-space-json0.img.sh failed:
'5'
FAILED backtrace:
135 ./luks2-validation-test
FAIL: luks2-validation-test
-
[ Where problems could occur ]
- * This fix fixes unit tests failure;
- Problems could occur on unit tests and make other tests fail.
+ * This fix fixes unit tests failure;
+ Problems could occur on unit tests and make other tests fail.
[ Other Info ]
- * Since this is FTBFS and usually we do not SRU FTBFS alone.
- We only fix for Noble as of now since we will bundle it with
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2160630
+ * Stonking is not affected by this because jq in stonking does not have
+ yet the jq CVE, it will probably have it once we merge 1.8.2 from
+ Debian
+
+ * Since this is FTBFS and usually we do not SRU FTBFS alone.
+ We only SRU for Noble as of now since we will bundle it with
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2160630
-- Original bug report --
On Ubuntu Noble 24.04 LTS, the build fails with following log:
...
LUKS2 sector size:[512][1024][2048][4096]
[4] Disappeared device test:
LUKS1[OK] LUKS2[OK] BITLK[OK] TCRYPT[OK]
PASS: device-test
[1] Valid keyring keys
[2] message ioctl
[3] bOrked keys
PASS: keyring-test
Testing aes-xts-plain64...OK
Testing aes-cbc-essiv:sha256...OK
Testing serpent-cbc-tcw...OK
Test LUKS2 key refresh...OK
PASS: keyring-compat-test
[0] Generating test headers
generate-luks2-area-in-json-hdr-space-json0.img.sh...jq: parse error: Invalid
numeric literal at EOF at line 1, column 12288
jq: parse error: Invalid numeric literal at EOF at line 1, column 12288
Header generator ./generate-luks2-area-in-json-hdr-space-json0.img.sh failed:
'5'
FAILED backtrace:
135 ./luks2-validation-test
FAIL: luks2-validation-test
...
** Changed in: cryptsetup (Ubuntu Noble)
Status: New => In Progress
** Changed in: cryptsetup (Ubuntu Stonking)
Assignee: Hector CAO (hectorcao) => (unassigned)
** Description changed:
[ Impact ]
* cryptsetup fails to build on Noble due to an failed unit test
* The unit test failure is due to jq security update CVE-2026-33948
* Blocks SRU for cryptsetup on Noble:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2160630
[ Test Plan ]
* Build the package on Noble with all updates installed (apt upgrade)
* The build should fail with log:
Test LUKS2 key refresh...OK
PASS: keyring-compat-test
[0] Generating test headers
generate-luks2-area-in-json-hdr-space-json0.img.sh...jq: parse error: Invalid
numeric literal at EOF at line 1, column 12288
jq: parse error: Invalid numeric literal at EOF at line 1, column 12288
Header generator ./generate-luks2-area-in-json-hdr-space-json0.img.sh failed:
'5'
FAILED backtrace:
135 ./luks2-validation-test
FAIL: luks2-validation-test
[ Where problems could occur ]
* This fix fixes unit tests failure;
Problems could occur on unit tests and make other tests fail.
[ Other Info ]
- * Stonking is not affected by this because jq in stonking does not have
+ * Stonking is not affected by this because jq in stonking does not have
yet the jq CVE, it will probably have it once we merge 1.8.2 from
Debian
* Since this is FTBFS and usually we do not SRU FTBFS alone.
We only SRU for Noble as of now since we will bundle it with
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2160630
+
+ * Since this is bundled with
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2160630 and the
latter does not need to go to -updates
+ This also apply to this one, therefore, I add the tag blocked-in-noble
-- Original bug report --
On Ubuntu Noble 24.04 LTS, the build fails with following log:
...
LUKS2 sector size:[512][1024][2048][4096]
[4] Disappeared device test:
LUKS1[OK] LUKS2[OK] BITLK[OK] TCRYPT[OK]
PASS: device-test
[1] Valid keyring keys
[2] message ioctl
[3] bOrked keys
PASS: keyring-test
Testing aes-xts-plain64...OK
Testing aes-cbc-essiv:sha256...OK
Testing serpent-cbc-tcw...OK
Test LUKS2 key refresh...OK
PASS: keyring-compat-test
[0] Generating test headers
generate-luks2-area-in-json-hdr-space-json0.img.sh...jq: parse error: Invalid
numeric literal at EOF at line 1, column 12288
jq: parse error: Invalid numeric literal at EOF at line 1, column 12288
Header generator ./generate-luks2-area-in-json-hdr-space-json0.img.sh failed:
'5'
FAILED backtrace:
135 ./luks2-validation-test
FAIL: luks2-validation-test
...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2160676
Title:
FTBFS in noble with test failure due to jq security update
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2160676/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
