Bug #70792
closedclang-19 can't be installed from run-make-check.sh because clang-13 conflicts
0%
Description
+ apt-get install -y clang-19 lldb-19 lld-19 clangd-19
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
python3-lldb-13 : Conflicts: python3-lldb-x.y
python3-lldb-19 : Conflicts: python3-lldb-x.y
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
Build step 'Execute shell' marked build as failure
Updated by Matan Breizman 11 months ago
- Assignee deleted (
Matan Breizman)
Dan Mick wrote:
+ apt-get install -y clang-19 lldb-19 lld-19 clangd-19
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:The following packages have unmet dependencies:
python3-lldb-13 : Conflicts: python3-lldb-x.y
python3-lldb-19 : Conflicts: python3-lldb-x.y
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
Build step 'Execute shell' marked build as failure
Hey Dan, thanks for creating this tracker.
IIUC, this means that we would have to remove clang-13 (or other) conflicting versions from all of our builders, right?
I think that removing those from the machine itself should be the most convenient (instead of auditing our scripts).
I don't have access to all of the builders, do you happen to know who does?
Thanks!
Updated by Dan Mick 11 months ago
The right solution is to fix the 'update clang' build script snippet to remove any other clang versions. This may happen again as we change the required version; removing 13 (or any other versions) now won't fix the problem, if there is one, when we move from 19 to 20, for example.
Updated by Casey Bodley 10 months ago
The following packages have unmet dependencies: python3-lldb-13 : Conflicts: python3-lldb-x.y python3-lldb-19 : Conflicts: python3-lldb-x.y
Updated by Dan Mick 10 months ago
I had originally assigned this to Matan because he had added the code to install directly from llvm.org in https://github.com/ceph/ceph/pull/61740. Not sure why he removed himself as owner.
Updated by Bill Scales 10 months ago
Seen twice while running make checks on braggi15, worked 3rd attempt building on braggi03
@Dan Mick is this just a problem with the packages installed on braggi15, or are we going to see this on other systems as we switch between building different branches/releases? If its the latter then I think you are suggesting that we update the build scripts to remove the conflicting packages when changing which version of clang we use. Seems to be a common problem on ubuntu 22.4 - see https://github.com/google/re2/commit/a61ae468c7205bc7d38efa11f4d0fb8f51947ee9 and https://github.com/llvm/llvm-project/issues/64182 for other peoples fixes.
Updated by Dan Mick 10 months ago
Bill, that was the point of my earlier comment https://tracker.ceph.com/issues/70792#note-2. The addition of the calls to llvm.sh to manage the build environment has a bug; whether the bug is in llvm.sh itself or in the calling code, the calling code is what we own and it needs to be fixed there.
Updated by Casey Bodley 9 months ago
- Assignee set to Matan Breizman
The following packages have unmet dependencies:
python3-lldb-13 : Conflicts: python3-lldb-x.y
python3-lldb-19 : Conflicts: python3-lldb-x.y
Updated by Casey Bodley 9 months ago
- Pull request ID set to 63409
this is tracked in https://github.com/llvm/llvm-project/issues/64182
several other projects are working around this by running sudo apt-get purge --auto-remove llvm python3-lldb-14 llvm-14 -y before llvm.sh:
https://github.com/leitao/liburing/commit/81dd6ab82a43126835b2263a801c65f616aef0a8
https://github.com/danmar/cppcheck/pull/5285/files
opened https://github.com/ceph/ceph/pull/63409 to do the same, except for v13 packages
Updated by Casey Bodley 9 months ago
- Status changed from New to Fix Under Review
Updated by Casey Bodley 9 months ago
- Status changed from Fix Under Review to Pending Backport
- Assignee changed from Matan Breizman to Casey Bodley
- Backport set to tentacle
Updated by Upkeep Bot 9 months ago
- Copied to Backport #71562: tentacle: clang-19 can't be installed from run-make-check.sh because clang-13 conflicts added
Updated by Upkeep Bot 8 months ago
- Status changed from Pending Backport to Resolved
- Merge Commit set to 03238f02e19dadc4a65ef66ec3fffb6cb21d3403
- Fixed In set to v20.3.0-764-g03238f02e19
- Upkeep Timestamp set to 2025-07-08T14:46:56+00:00
Updated by Upkeep Bot 7 months ago
- Fixed In changed from v20.3.0-764-g03238f02e19 to v20.3.0-764-g03238f02e1
- Upkeep Timestamp changed from 2025-07-08T14:46:56+00:00 to 2025-07-14T16:45:59+00:00