| 2024-02-03 23:32:06 |
dann frazier |
bug |
|
|
added bug |
| 2024-02-03 23:32:17 |
dann frazier |
nominated for series |
|
Ubuntu Mantic |
|
| 2024-02-03 23:32:17 |
dann frazier |
bug task added |
|
cmake (Ubuntu Mantic) |
|
| 2024-02-03 23:32:17 |
dann frazier |
nominated for series |
|
Ubuntu Jammy |
|
| 2024-02-03 23:32:17 |
dann frazier |
bug task added |
|
cmake (Ubuntu Jammy) |
|
| 2024-02-03 23:32:17 |
dann frazier |
nominated for series |
|
Ubuntu Noble |
|
| 2024-02-03 23:32:17 |
dann frazier |
bug task added |
|
cmake (Ubuntu Noble) |
|
| 2024-02-03 23:32:24 |
dann frazier |
cmake (Ubuntu Jammy): status |
New |
In Progress |
|
| 2024-02-03 23:32:27 |
dann frazier |
cmake (Ubuntu Jammy): assignee |
|
dann frazier (dannf) |
|
| 2024-02-03 23:32:32 |
dann frazier |
cmake (Ubuntu Mantic): status |
New |
Fix Released |
|
| 2024-02-03 23:32:35 |
dann frazier |
cmake (Ubuntu Noble): status |
New |
Fix Released |
|
| 2024-02-04 00:56:28 |
dann frazier |
description |
[Impact]
cmake no longer builds from source in jammy due to a git security update that sets protocol.file.allow=user by default.
[Test Case]
Rebuild cmake in latest jammy.
[Regression Risk]
The fix is to a test case. A risk is that the test may no longer test a valid use case, and future updates could thereby sneak an actual functional regression through. |
[Impact]
cmake no longer builds from source in jammy due to a git security update that sets protocol.file.allow=user by default. This doesn't currently impact our builders because they seem to have an old version of git pinned - but it does impact anyone building w/ latest jammy updates applied.
Start 161: ExternalProjectLocal
663/664 Test #161: ExternalProjectLocal ........................................ Passed 38.40 sec
Start 163: ExternalProjectUpdate
664/664 Test #163: ExternalProjectUpdate ....................................... Passed 34.81 sec
99% tests passed, 2 tests failed out of 664
Label Time Summary:
CMake = 4485.67 sec*proc (263 tests)
CUDA = 488.20 sec*proc (9 tests)
HIP = 97.83 sec*proc (5 tests)
ISPC = 306.75 sec*proc (5 tests)
Label1 = 0.07 sec*proc (1 test)
Label2 = 0.07 sec*proc (1 test)
Qt5 = 1859.09 sec*proc (43 tests)
command = 6.62 sec*proc (27 tests)
policy = 476.79 sec*proc (38 tests)
run = 4479.05 sec*proc (236 tests)
Total Test time (real) = 447.01 sec
The following tests FAILED:
157 - ExternalProject (Failed)
225 - CTest.UpdateGIT (Failed)
Errors while running CTest
make[2]: *** [Makefile:94: test] Error 8
make[2]: Leaving directory '/home/ubuntu/cmake-3.22.1/Build'
dh_auto_test: error: cd Build && make -j64 test ARGS\+=--verbose ARGS\+=-j64 -j1 "ARGS=-E CTestTestUpload\\|curl --timeout 5000 -j64" returned exit code 2
make[1]: *** [debian/rules:81: override_dh_auto_test] Error 25
make[1]: Leaving directory '/home/ubuntu/cmake-3.22.1'
make: *** [debian/rules:108: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
[Test Case]
Rebuild cmake in latest jammy.
[Regression Risk]
The fix is to a test case. A risk is that the test may no longer test a valid use case, and future updates could thereby sneak an actual functional regression through. |
|
| 2024-02-04 00:57:26 |
dann frazier |
attachment added |
|
cmake.buildlog https://bugs.launchpad.net/ubuntu/jammy/+source/cmake/+bug/2052362/+attachment/5744476/+files/cmake.buildlog |
|
| 2024-02-04 00:58:10 |
dann frazier |
description |
[Impact]
cmake no longer builds from source in jammy due to a git security update that sets protocol.file.allow=user by default. This doesn't currently impact our builders because they seem to have an old version of git pinned - but it does impact anyone building w/ latest jammy updates applied.
Start 161: ExternalProjectLocal
663/664 Test #161: ExternalProjectLocal ........................................ Passed 38.40 sec
Start 163: ExternalProjectUpdate
664/664 Test #163: ExternalProjectUpdate ....................................... Passed 34.81 sec
99% tests passed, 2 tests failed out of 664
Label Time Summary:
CMake = 4485.67 sec*proc (263 tests)
CUDA = 488.20 sec*proc (9 tests)
HIP = 97.83 sec*proc (5 tests)
ISPC = 306.75 sec*proc (5 tests)
Label1 = 0.07 sec*proc (1 test)
Label2 = 0.07 sec*proc (1 test)
Qt5 = 1859.09 sec*proc (43 tests)
command = 6.62 sec*proc (27 tests)
policy = 476.79 sec*proc (38 tests)
run = 4479.05 sec*proc (236 tests)
Total Test time (real) = 447.01 sec
The following tests FAILED:
157 - ExternalProject (Failed)
225 - CTest.UpdateGIT (Failed)
Errors while running CTest
make[2]: *** [Makefile:94: test] Error 8
make[2]: Leaving directory '/home/ubuntu/cmake-3.22.1/Build'
dh_auto_test: error: cd Build && make -j64 test ARGS\+=--verbose ARGS\+=-j64 -j1 "ARGS=-E CTestTestUpload\\|curl --timeout 5000 -j64" returned exit code 2
make[1]: *** [debian/rules:81: override_dh_auto_test] Error 25
make[1]: Leaving directory '/home/ubuntu/cmake-3.22.1'
make: *** [debian/rules:108: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
[Test Case]
Rebuild cmake in latest jammy.
[Regression Risk]
The fix is to a test case. A risk is that the test may no longer test a valid use case, and future updates could thereby sneak an actual functional regression through. |
[Impact]
cmake no longer builds from source in jammy due to a git security update that sets protocol.file.allow=user by default. This doesn't currently impact our builders because they seem to have an old version of git pinned - but it does impact anyone building w/ latest jammy updates applied. Here's a tail of the buildlog:
<...>
Start 161: ExternalProjectLocal
663/664 Test #161: ExternalProjectLocal ........................................ Passed 38.40 sec
Start 163: ExternalProjectUpdate
664/664 Test #163: ExternalProjectUpdate ....................................... Passed 34.81 sec
99% tests passed, 2 tests failed out of 664
Label Time Summary:
CMake = 4485.67 sec*proc (263 tests)
CUDA = 488.20 sec*proc (9 tests)
HIP = 97.83 sec*proc (5 tests)
ISPC = 306.75 sec*proc (5 tests)
Label1 = 0.07 sec*proc (1 test)
Label2 = 0.07 sec*proc (1 test)
Qt5 = 1859.09 sec*proc (43 tests)
command = 6.62 sec*proc (27 tests)
policy = 476.79 sec*proc (38 tests)
run = 4479.05 sec*proc (236 tests)
Total Test time (real) = 447.01 sec
The following tests FAILED:
157 - ExternalProject (Failed)
225 - CTest.UpdateGIT (Failed)
Errors while running CTest
make[2]: *** [Makefile:94: test] Error 8
make[2]: Leaving directory '/home/ubuntu/cmake-3.22.1/Build'
dh_auto_test: error: cd Build && make -j64 test ARGS\+=--verbose ARGS\+=-j64 -j1 "ARGS=-E CTestTestUpload\\|curl --timeout 5000 -j64" returned exit code 2
make[1]: *** [debian/rules:81: override_dh_auto_test] Error 25
make[1]: Leaving directory '/home/ubuntu/cmake-3.22.1'
make: *** [debian/rules:108: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
[Test Case]
Rebuild cmake in latest jammy.
[Regression Risk]
The fix is to a test case. A risk is that the test may no longer test a valid use case, and future updates could thereby sneak an actual functional regression through. |
|
| 2024-02-14 14:06:08 |
Robie Basak |
cmake (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
| 2024-02-14 14:06:09 |
Robie Basak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2024-02-14 14:06:11 |
Robie Basak |
bug |
|
|
added subscriber SRU Verification |
| 2024-02-14 14:06:16 |
Robie Basak |
tags |
|
verification-needed verification-needed-jammy |
|
| 2024-02-20 22:35:17 |
dann frazier |
attachment added |
|
cmake_3.22.1-1ubuntu1.22.04.2_armhf.buildlog.gz https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/2052362/+attachment/5747837/+files/cmake_3.22.1-1ubuntu1.22.04.2_armhf.buildlog.gz |
|
| 2024-02-20 22:35:35 |
dann frazier |
tags |
verification-needed verification-needed-jammy |
verification-done verification-done-jammy |
|
| 2024-02-22 21:33:34 |
Launchpad Janitor |
cmake (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2024-02-22 21:33:34 |
Launchpad Janitor |
cve linked |
|
2022-39253 |
|
| 2024-02-22 21:33:41 |
Andreas Hasenack |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
